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

Incident Score: Analysis & Impact (INF1765483620)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-33
Company Score Before Incident750 / 1000
Company Score After Incident717 / 1000
Company LinkView Information Design Profile
INCIDENT NUMBERINF1765483620
Type of Cyber IncidentCyber Attack
ATTACK VECTORThird-party software developer (Bakka Soft)
DATA EXPOSEDNA
INCIDENT DATE30/06/2025
STATUSOngoing (unverified report)

Key Highlights From The Incident Analysis

  • Timeline of Information Design'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 Information Design 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 Information Design breach identified under incident ID INF1765483620.

The analysis begins with a detailed overview of Information Design's information like the linkedin page: https://www.linkedin.com/company/information-design-one-ag, the number of followers: 1244, the industry type: IT Services and IT Consulting and the number of employees: 33 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 750 and after the incident was 717 with a difference of -33 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 Information Design and their customers.

Aeroflot recently reported "Aeroflot July Outage - Supply-Chain Attack via Bakka Soft", a noteworthy cybersecurity incident.

Attackers exploited months-old access, lacking 2FA, to deploy extensive malware and disrupt Aeroflot's flights.

The disruption is felt across the environment, affecting Aeroflot’s IT network, iOS apps, quality management systems, plus an estimated financial loss of Tens of millions of dollars.

Formal response steps have not been shared publicly yet.

The case underscores how Ongoing (unverified report), teams are taking away lessons such as Lack of 2FA and persistent third-party access can lead to supply-chain attacks. Early detection of suspicious activity is critical to prevent escalation, and recommending next steps like Implement multi-factor authentication (MFA/2FA) for all third-party access, Monitor and audit third-party vendor access to critical infrastructure and Enhance detection capabilities for suspicious activity.

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 Supply Chain Compromise (T1195) with high confidence (95%), with evidence including supply-chain breach via Bakka Soft, and bakka Soft had access to Aeroflot’s IT network and Supply Chain Compromise: Compromise Software Supply Chain (T1195.002) with high confidence (90%), supported by evidence indicating bakka Soft worked on Aeroflot’s iOS apps and quality management systems. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating persistent access to Aeroflot’s infrastructure via Bakka Soft and Create Account (T1136) with moderate to high confidence (70%), supported by evidence indicating attackers established persistence (implied by malware deployment). Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (80%), supported by evidence indicating lack of 2FA allowed attackers to bypass authentication controls and Valid Accounts: Local Accounts (T1078.003) with moderate to high confidence (85%), supported by evidence indicating bakka Soft’s access exploited without 2FA or revocation. Under the Impact tactic, the analysis identified Service Stop (T1489) with high confidence (95%), supported by evidence indicating over 100 grounded flights, tens of thousands of passengers stranded and Defacement (T1491) with moderate to high confidence (70%), supported by evidence indicating operational disruption of flagship airline (implied brand impact). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Sources & References