Coupang breach exposes personal data of 33.7 million South Korean customer accounts

Coupang, South Korea’s largest online retailer, has disclosed a data breach affecting about 33.7 million customer accounts, roughly two-thirds of the country’s population. The company first reported suspicious activity involving around 4,500 accounts. A deeper investigation then showed the exposure was several thousand times larger.

What happened

Coupang detected abnormal access on 18 November 2025. On 29 November it said the unauthorised activity had started as early as 24 June 2025 and went unnoticed for about five months. According to Korean media and investigators’ statements, the suspect is a former employee who had worked on authentication systems and kept a valid access key after leaving the company. Reports also describe an earlier test run in January 2025 against 95 accounts, as well as extortion emails sent to the company and to customers.

Coupang said it found no evidence that customers of Coupang Taiwan or its Japanese food delivery service Rocket Now were affected.

Impact

The exposed data includes:

  • customer names and email addresses
  • phone numbers
  • shipping addresses
  • certain order history

Coupang says payment card data, financial information and login passwords were not affected. Even so, the combination of verified contact details, home addresses and purchase history is very useful for delivery-themed phishing, smishing and voice fraud. The scale of the incident has drawn immediate scrutiny from South Korean regulators and lawmakers.

Recommendations

  • Coupang customers should treat unsolicited messages about orders, refunds or compensation with suspicion and only use the official app or website.
  • Retailers and platforms should revoke access keys, signing keys and service credentials immediately when staff leave, and inventory long-lived keys on a regular schedule.
  • Monitor authentication services for token issuance from unusual hosts or volumes. Bulk profile reads across millions of accounts should trigger alerts.
  • Apply short lifetimes and automated rotation to keys that can sign or mint authentication tokens.

Sources