Ingram Micro Breach Incident Score: Analysis & Impact (THEINGDEPCIRTIM1769124673)

In this Rankiteo incident briefing, we review the Ingram Micro breach identified under incident ID THEINGDEPCIRTIM1769124673.

The analysis begins with a detailed overview of Ingram Micro's information like the linkedin page: https://www.linkedin.com/company/ingram-micro, the number of followers: 583296, the industry type: IT Services and IT Consulting and the number of employees: 28560 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 483 and after the incident was 473 with a difference of -10 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 Ingram Micro and their customers.

On 01 August 2025, U.S. Department of Government Efficiency (DOGE) disclosed Data Breach, Phishing and Ransomware issues under the banner "Weekly Cybersecurity Breach Roundup: DOGE Data Exposure, CIRO Phishing Attack, and Rising Threats".

This week’s cybersecurity landscape saw multiple high-profile incidents, including unauthorized data sharing by the U.S.

The disruption is felt across the environment, affecting Cloudflare server, CIRO systems and Ingram Micro systems, and exposing Social Security data, Personal Identifiable Information (PII) and Investment account details, with nearly ['750,000 (CIRO)', '42,521 (Ingram Micro)', '23 million (SK Telecom)'] records at risk, plus an estimated financial loss of $91 million (proposed fine for SK Telecom).

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Ingram Micro took systems offline and SK Telecom offered free USIM replacements, and began remediation that includes Chainlit released patches for CVE-2026-22218 and CVE-2026-22219, while recovery efforts such as Ingram Micro restored operations by July 9, 2025 continue, and stakeholders are being briefed through CIRO disclosed breach in August 2025 and SK Telecom contested fine.

The case underscores how Ongoing (DOGE, SK Telecom, CIRO), and recommending next steps like Strengthen DDoS defenses (traffic filtering, WAFs, rate-limiting), Patch critical vulnerabilities promptly (e.g., Chainlit) and Avoid unauthorized cloud storage for sensitive data, with advisories going out to stakeholders covering UK NCSC advised organizations to strengthen DDoS defenses.

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.

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 Phishing (T1566) with high confidence (90%), supported by evidence indicating cIRO disclosed a phishing attack in August 2025, Exploit Public-Facing Application (T1190) with moderate to high confidence (80%), supported by evidence indicating cVE-2026-22218 and CVE-2026-22219 in Chainlit AI framework, Supply Chain Compromise: Compromise Software Dependencies and Development Tools (T1195.002) with moderate to high confidence (70%), supported by evidence indicating north Korean hackers abused Microsoft VS Code for malware delivery, and Valid Accounts (T1078) with moderate to high confidence (80%), supported by evidence indicating compromised Bitbucket account (SK Telecom). Under the Execution tactic, the analysis identified User Execution: Malicious File (T1204.002) with moderate to high confidence (70%), supported by evidence indicating victims tricked into opening malicious Git repositories (VS Code) and Command and Scripting Interpreter (T1059) with moderate to high confidence (80%), supported by evidence indicating malicious Git repositories executed attacker-controlled commands. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating dOGE employee accessed Numident database despite revoked access. Under the Privilege Escalation tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating dOGE employee accessed sensitive SSA databases. Under the Defense Evasion tactic, the analysis identified Hide Artifacts: Hidden Files and Directories (T1564.001) with moderate confidence (60%), supported by evidence indicating dOGE employee sent encrypted file (undecryptable by SSA) and Masquerading (T1036) with moderate to high confidence (70%), supported by evidence indicating malicious Git repositories disguised as legitimate projects. Under the Credential Access tactic, the analysis identified Brute Force (T1110) with moderate confidence (50%), supported by evidence indicating phishing attack (CIRO) may have led to credential harvesting and Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (70%), supported by evidence indicating aWS keys stolen via compromised Bitbucket account (SK Telecom). Under the Discovery tactic, the analysis identified Account Discovery (T1087) with moderate confidence (60%), supported by evidence indicating dOGE accessed Numident database (SSA records) and Network Service Discovery (T1046) with moderate to high confidence (70%), supported by evidence indicating sSRF vulnerability in Chainlit (CVE-2026-22219). Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating 3.5 TB of data stolen (Ingram Micro); SSA data uploaded to Cloudflare and Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating numident database accessed (DOGE); investment account details (CIRO). Under the Command and Control tactic, the analysis identified Application Layer Protocol (T1071) with moderate to high confidence (70%), supported by evidence indicating north Korean hackers used Vercel for C2 infrastructure. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating 3.5 TB exfiltrated (Ingram Micro); SSA data uploaded to Cloudflare and Exfiltration Over Web Service (T1567) with moderate to high confidence (80%), supported by evidence indicating data published by SafePay gang after ransom refusal. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with moderate to high confidence (80%), supported by evidence indicating ransomware attack by SafePay gang (Ingram Micro), Endpoint Denial of Service (T1499) with moderate to high confidence (70%), supported by evidence indicating dDoS attacks by NoName057(16) (UK NCSC alert), and Data Destruction (T1485) with moderate confidence (50%), supported by evidence indicating potential data destruction if ransom unpaid (Ingram Micro). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.