Coupang Breach Incident Score: Analysis & Impact (COU4132641112125)
The Rankiteo video explains how the company Coupang has been impacted by a Breach on the date November 06, 2025.
Incident Summary
If the player does not load, you can open the video directly.
Key Highlights From This Incident Analysis
- Timeline of Coupang's Breach 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 Coupang 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 Coupang breach identified under incident ID COU4132641112125.
The analysis begins with a detailed overview of Coupang's information like the linkedin page: https://www.linkedin.com/company/coupang, the number of followers: 226701, the industry type: Software Development and the number of employees: 7994 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 812 and after the incident was 767 with a difference of -45 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 Coupang and their customers.
On 18 November 2023, Coupang disclosed data breach and unauthorized access issues under the banner "Coupang Data Breach Exposing Personal Information of Over 4,500 Customers".
Coupang failed to detect a data breach that exposed the personal information of more than 4,500 customers for over 10 days.
The disruption is felt across the environment, affecting user account profiles, and exposing names, phone numbers and shipping addresses, with nearly 4,536 records at risk.
In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like revoked signature key information for tokens, and began remediation that includes enhanced detection rules and expanded monitoring, and stakeholders are being briefed through text message to affected customers on November 18, 2023.
The case underscores how ongoing (by Ministry of Science and ICT, KISA, and Personal Information Protection Commission), with advisories going out to stakeholders covering text message notification to affected customers.
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 Valid Accounts: Cloud Accounts (T1078.004) with high confidence (95%), with evidence including exploitation of signed access token (Initial Access Broker), and unauthorized access to 4,536 customer accounts. Under the Persistence tactic, the analysis identified Account Manipulation: Additional Cloud Credentials (T1098.003) with moderate to high confidence (85%), supported by evidence indicating exploitation of signed access token (undetected for 12 days). Under the Credential Access tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with high confidence (95%), with evidence including compromised signed access token (Vulnerability Exploited), and revoked signature key information for tokens (Containment). Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating five most recent orders and delivery address book entries (Data Compromised). Under the Exfiltration tactic, the analysis identified Exfiltration Over Command and Control Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating unauthorized access to view sensitive customer data (12-day window). Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (75%), supported by evidence indicating failed to detect the intrusion promptly (Root Cause) and Indicator Removal: Timestomp (T1070.006) with moderate to high confidence (70%), supported by evidence indicating breach went undetected for 12 days (Prolonged Access). Under the Impact tactic, the analysis identified Active Scanning: Vulnerability Scanning (T1595.002) with moderate to high confidence (70%), supported by evidence indicating exploitation of signed access token (Initial Vector). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources
- Coupang Rankiteo Cyber Incident Details: http://www.rankiteo.com/company/coupang/incident/COU4132641112125
- Coupang CyberSecurity Rating page: https://www.rankiteo.com/company/coupang
- Coupang Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/cou4132641112125-coupang-breach-november-2025/
- Coupang CyberSecurity Score History: https://www.rankiteo.com/company/coupang/history
- Coupang CyberSecurity Incident Source: https://koreajoongangdaily.joins.com/news/2025-11-21/business/industry/Coupang-fails-to-detect-data-breach-affecting-over-4500-customers-for-12-days/2460376
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/static/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://www.rankiteo.com/static/Rankiteo%20Cybersecurity%20Rating%20Model.pdf





