Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Iberia » MCDIBENISDEC1768955534

Incident Score: Analysis & Impact (MCDIBENISDEC1768955534)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-93
Company Score Before Incident781 / 1000
Company Score After Incident688 / 1000
INCIDENT NUMBERMCDIBENISDEC1768955534
Type of Cyber IncidentRansomware
ATTACK VECTORNA
DATA EXPOSED861 GB
INCIDENT DATE15/06/2023
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of Iberia's Ransomware 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 Iberia 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 Iberia breach identified under incident ID MCDIBENISDEC1768955534.

The analysis begins with a detailed overview of Iberia's information like the linkedin page: https://www.linkedin.com/company/iberia, the number of followers: 418965, the industry type: Airlines and Aviation and the number of employees: 10823 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 781 and after the incident was 688 with a difference of -93 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 Iberia and their customers.

On 20 January 2026, McDonald’s India disclosed Ransomware issues under the banner "Everest Ransomware Group Claims Breach of McDonald’s India".

The Everest ransomware group has claimed responsibility for a breach of McDonald’s India, the fast-food giant’s Indian subsidiary, allegedly exfiltrating 861 GB of customer data and internal documents.

The disruption is felt across the environment, and exposing 861 GB.

Formal response steps have not been shared publicly yet.

The case underscores how Ongoing.

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 confidence (50%), supported by evidence indicating allegedly exfiltrating 861 GB of customer data and internal documents and Valid Accounts (T1078) with moderate confidence (60%), supported by evidence indicating store-level data, such as manager names, company email addresses. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (70%), supported by evidence indicating eRP migration files, pricing data, and confidential internal communications and OS Credential Dumping (T1003) with moderate confidence (50%), supported by evidence indicating store-level data, such as manager names, company email addresses. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating 861 GB of customer data and internal documents allegedly stolen, Data from Network Shared Drive (T1039) with moderate to high confidence (80%), supported by evidence indicating structured directories with month-by-month accounting records, and Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating folder labeled Investor Info containing board-level documents. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating 861 GB of data allegedly exfiltrated by Everest ransomware group and Exfiltration Over Web Service (T1567) with moderate confidence (60%), supported by evidence indicating claims posted on the group’s dark web leak site. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with moderate to high confidence (70%), supported by evidence indicating everest ransomware group, known for ransomware operations and Defacement (T1491) with moderate confidence (50%), supported by evidence indicating claims posted on the group’s dark web leak site. Under the Command and Control tactic, the analysis identified Application Layer Protocol (T1071) with moderate to high confidence (70%), supported by evidence indicating data exfiltration and ransomware operations by Everest group. 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 (50%)
Valid Accounts (60%)
Credential Access
Unsecured Credentials: Credentials In Files (70%)
OS Credential Dumping (50%)
Collection
Data from Local System (90%)
Data from Network Shared Drive (80%)
Data from Information Repositories (80%)
Exfiltration
Exfiltration Over C2 Channel (90%)
Exfiltration Over Web Service (60%)
Impact
Data Encrypted for Impact (70%)
Defacement (50%)
Command and Control
Application Layer Protocol (70%)