Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Lenta » MIRЯНДLENFED1768365445

Incident Score: Analysis & Impact (MIRЯНДLENFED1768365445)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-32
Company Score Before Incident772 / 1000
Company Score After Incident740 / 1000
Company LinkView Lenta Profile
INCIDENT NUMBERMIRЯНДLENFED1768365445
Type of Cyber IncidentCyber Attack
ATTACK VECTORNA
DATA EXPOSEDNA
INCIDENT DATE22/06/2025
STATUSpublished

Key Highlights From The Incident Analysis

  • Timeline of Lenta's Cyber Attack and lateral movement inside company's environment.
  • Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
  • How Rankiteo’s incident engine converts technical details into a normalized incident score.
  • How this cyber incident impacts Lenta Rankiteo cyber scoring and cyber rating.
  • Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.

Full Incident Analysis Transcript

In this Rankiteo incident briefing, we review the Lenta breach identified under incident ID MIRЯНДLENFED1768365445.

The analysis begins with a detailed overview of Lenta's information like the linkedin page: https://www.linkedin.com/company/lenta, the number of followers: 11506, the industry type: Retail and the number of employees: 763 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 772 and after the incident was 740 with a difference of -32 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Lenta and their customers.

Lenta recently reported "Cyberattack on Russia's Mercury Platform Disrupts Dairy Supply Chain", a noteworthy cybersecurity incident.

Major Russian retailers Lenta, Miratorg, and Yandex Lavka have disclosed significant dairy supply chain disruptions after the country's Mercury platform used for animal-based product certification was downed by a cyberattack.

The disruption is felt across the environment, affecting Mercury platform, product labeling system, and other platforms.

In response, and began remediation that includes Efforts to restore the system are underway.

Overall, the incident is a reminder of why proactive monitoring and strong governance matter.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

MITRE ATT&CK® Correlation Analysis

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with moderate to high confidence (70%), supported by evidence indicating cyberattack on the Mercury platform, a critical certification system and Trusted Relationship (T1199) with moderate confidence (60%), supported by evidence indicating mercury platform facilitates data exchanges with mandatory labeling system. Under the Impact tactic, the analysis identified Service Stop (T1489) with high confidence (90%), supported by evidence indicating outages impacted data exchanges, halting operations for large-volume producers and Defacement (T1491) with lower confidence (30%), supported by evidence indicating no details on system defacement, but platform was downed. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate confidence (50%), supported by evidence indicating no threat group claimed responsibility, but prior attacks involved ransomware. Under the Defense Evasion tactic, the analysis identified Disabling Security Tools (T1089) with lower confidence (40%), supported by evidence indicating mercury platform outage suggests possible disruption of monitoring tools. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Exploit Public-Facing Application (70%)
Trusted Relationship (60%)
Impact
Service Stop (90%)
Defacement (30%)
Exfiltration
Exfiltration Over C2 Channel (50%)
Defense Evasion
Disabling Security Tools (40%)