People search Coupang data breach timeline because millions of customers entrust payment and identity data to everyday transactions. BreachHistory indexes 3 Coupang-linked incidents, with headline counts up to 37.5M+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Coupang breach history matters
Coupang operates in Retail (South Korea). Across indexed rows, recurring themes include mixed intrusion and disclosure events. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — 200K accounts
Cataloged incident. Coupang confirmed a data breach affecting approximately 200,000 Taiwan-based customer accounts. Company offered vouchers to affected users. Taiwan demanded answers from Coupang; regulatory oversight concerns followed. Exposed categories include Customer account data. BreachHistory cites approximately 200K+ affected records in this row. See the coupang-taiwan 2026 record and canonical BreachHistory entry.
2026 — 37.55M accounts; record ₩624.6B PIPC fine (Feb breach)
Cataloged incident. South Korea's Ministry of Science and ICT confirmed in February 2026 that a breach at Coupang exposed 33.7 million customer accounts after a former developer stole a signing key post-departure and forged access passes from April through November 2025. In June 2026, the Personal Information Protection Commission (PIPC) imposed a record 624.6 billion won (~$409 million) fine—the largest in South Korean history—finding personal information of approximately 37.55 million people leaked due to negligent authentication-ke Exposed categories include Names, emails, phones, delivery addresses, order histories. BreachHistory cites approximately 37.5M+ affected records in this row. See the coupang 2026 record and canonical BreachHistory entry.
2025 — Internal portal compromise
Cataloged incident. Compromised internal portal; leak included home door codes and purchase history. Exposed categories include Names, addresses, phone numbers, home door codes, purchase history. BreachHistory cites approximately 33.7M+ affected records in this row. See the coupang2025 and canonical BreachHistory entry.
Patterns and analysis
- Mixed intrusion and disclosure events — appears across multiple Coupang catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Use virtual card numbers for online checkout where your bank supports it.
- Step 5: Bookmark the Coupang company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/coupang · Latest: coupang-taiwan2026.
Sources: BreachHistory catalog (3 rows for Coupang), company and regulator disclosures cited in individual breach records.