Coupang customer data breach
Add to my breach checkMade public · about 37.55 million people
What leaked6
Replaceable
- Building entrance code
Hard to replace
- Mobile number
- Home or delivery address
- Email address
Permanent
- Purchase or order history
- Full name
- Building entrance codeThe PIPC found 4,226 codes leaked unmasked. The address-list page masked the others, so for any one account it is possible, not confirmed.
- Mobile numberdelivery address-book phone
- Purchase or order historyorder history of 58,349 members · 272,470 orders: date, product, quantity, price; PIPC
To-dos5 · about 55 min in all
- Know the scam pattern: calls and texts that cite these leaked detailsLimits harm from: scam calls, phishing messages
- Register as an exposed person with the FSSLimits harm from: scam calls (opens in a new tab)
- Block new loans and cards in your nameLimits harm from: scam calls (opens in a new tab)
- Change the building entrance codeStops: building entry
- Remove your address and phone from public profiles and tighten SNS privacyLimits harm from: visits or contact at home
What happened next50 events
Penalty: 16 events
Back to latest- Suit to cancel the PIPC penalty surcharges (breach and advertising cases) filed at Seoul Administrative Court with a stay application
- Criminal complaint among the sanctions in the breach case, whose listed violations include destroying evidence such as logs
- Corrective orders: key management and access control, breach notice to non-member data subjects, destruction policy and governance; publication orders
- Separate penalty surcharge of KRW 201.1 billion in the same decision for collecting off-site activity records without consent · not the breach itself
- Administrative fine of KRW 16.8 million for breach-notice and destruction violations
11 more
- Penalty surcharge of KRW 423.6 billion for the breach · security-measure failures
- PIPC found 33,222,472 members and at least 4,338,368 non-members affected; basic security failures, not advanced hacking
- Joint investigation results: 33.67M name/email records leaked, delivery-list page viewed ~148M times; forged tokens, signing key not rotated after departure; late KISA report · fine planned
- Referred deletion of application logs (23 May to 2 June 2025) to investigators
- Fourth PIPC call to notify non-member data subjects · after 3, 10 and 26 December 2025; not carried out
- Referred deletion of web logs after the data-preservation order to investigators
- PIPC found partial compliance; called for a notice plan for non-members, 30+ day posting, and fixes to the liability-waiver terms and withdrawal process
- Police raided Coupang headquarters · first compulsory investigation
- Emergency resolution urging Coupang to re-notify the incident as a 'leak' rather than an 'exposure' with every leaked item, notify people on delivery lists, expand its response team and report back within 7 days
- Government joint public-private investigation team activated
- PIPC opened its investigation
- Company
- Coupang
- When it happened
- –
- Company detected it
- Made public
- Notice
- Leak confirmed
- Affected
- about 37.55 million people · PIPC decision June 11, 2026; 33.7M accounts in the first notice, +165,455 in February 2026
How the facts developed
- PIPC decision: about 37.55 million people. Penalty surcharge for the breach KRW 423.6 billion and an administrative fine of KRW 16.8 million. In the same decision, separate penalty surcharges: KRW 201.1 billion on Coupang for collecting online activity records without a legal basis, and KRW 248 million on CFS for unlawful collection and use of personal data and unlawful processing of sensitive data
- 165,455 further accounts (delivery lists: name, phone, address)
- Corrected notice after the PIPC's emergency resolution of December 3, 2025: '유출' instead of '노출', building entrance codes added. People on delivery lists who are not Coupang members were not notified (PIPC June 2026)
- First notice used '노출', listed name, email, delivery address book and some order info, and was posted for one to two days
Sources
- 개인정보보호위원회 regulator, (opens in a new tab)checked October 22, 2026
- 개인정보보호위원회 regulator, (opens in a new tab)checked October 22, 2026
- 개인정보보호위원회 regulator, (opens in a new tab)checked October 22, 2026
- 개인정보보호위원회 regulator, (opens in a new tab)checked October 22, 2026
- 개인정보보호위원회 regulator, (opens in a new tab)checked October 15, 2026
- 뉴시스 press (opens in a new tab)checked October 22, 2026
- 디지털타임스 press (opens in a new tab)checked October 16, 2026
- 과학기술정보통신부 regulator (opens in a new tab)checked October 22, 2026