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

Incident Score: Analysis & Impact (COU1768977298)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact0
Company Score Before Incident100 / 1000
Company Score After Incident100 / 1000
Company LinkView Coupang Profile
INCIDENT NUMBERCOU1768977298
Type of Cyber IncidentBreach
ATTACK VECTORInsider Threat (Former Employee)
DATA EXPOSEDSensitive customer information
INCIDENT DATE15/12/2025
STATUSPending (Class Period: May 7, 2025 - December 16, 2025)

Key Highlights From The 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 COU1768977298.

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: 242085, the industry type: Software Development and the number of employees: 8652 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 100 and after the incident was 100 with a difference of 0 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 16 December 2025, Coupang, Inc. disclosed Data Breach issues under the banner "Coupang Securities Class Action Over Undisclosed Data Breach and Cybersecurity Failures".

A securities class action lawsuit against Coupang, Inc.

The disruption is felt across the environment, and exposing Sensitive customer information.

In response, and stakeholders are being briefed through Omissions in SEC filings, misleading public statements.

The case underscores how Pending (Class Period: May 7, 2025 - December 16, 2025), with advisories going out to stakeholders covering Investors who purchased Coupang securities during the Class Period have until February 17, 2026, to file as lead plaintiffs.

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 Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), supported by evidence indicating former employee exploited system vulnerabilities from May 7 to December 16, 2025. Under the Persistence tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (80%), supported by evidence indicating unauthorized access for six months by former employee. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Cloud Instance Metadata API (T1552.005) with moderate to high confidence (70%), supported by evidence indicating inadequate cybersecurity protocols, weak security controls. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating sensitive customer information was compromised. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating unauthorized access to sensitive customer information for six months. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (60%), supported by evidence indicating inadequate cybersecurity protocols, weak security controls and Indicator Removal: Clear Windows Event Logs (T1070.001) with moderate confidence (50%), supported by evidence indicating breach went undetected for six months. Under the Impact tactic, the analysis identified Service Stop (T1489) with lower confidence (40%), supported by evidence indicating heightened risk of regulatory and legal repercussions. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Valid Accounts: Cloud Accounts (90%)
Persistence
Valid Accounts: Cloud Accounts (80%)
Credential Access
Unsecured Credentials: Cloud Instance Metadata API (70%)
Collection
Data from Local System (80%)
Exfiltration
Exfiltration Over C2 Channel (70%)
Defense Evasion
Impair Defenses: Disable or Modify Tools (60%)
Indicator Removal: Clear Windows Event Logs (50%)
Impact
Service Stop (40%)

Sources & References