Now Hacked
EN
Data breach

Musinsa's 29CM customer data leak of 159,852 records, with more later confirmed

First reported · Last reported · 36 related reports

Abnormal access to the order lookup API at 29CM, operated by Musinsa, leaked 159,852 customer records. Most included only names, while about 20,000 included contact details, shipping information, email addresses and more. The company apologized, and in October 2026 a further leak of 30,000 personal records became known.

Key facts

Affected organization
Musinsa
Incident type
Data breach
Occurred / detected
Not confirmed
Scale of damage
159,852 customer records plus 30,000 additional records
Cause / method
Abnormal access to the order lookup API
Location
South Korea

If your data was exposed

Check if my data was leaked ↗View Musinsa notice ↗

Exposed dataNamePhone numberEmailAddress

  1. Don’t tap links in texts, calls or emails that mention this incident and offer compensation, refunds or breach checks. Check directly on the organization’s official website or app.
  2. If you’ve suffered harm, report it. Call 118 (no area code) for privacy violations, contact the police for financial losses, and apply for dispute mediation to seek compensation.Personal Information Infringement Report Center ↗Korean National Police Agency cybercrime report ↗Personal Information Dispute Mediation Committee ↗

Lookup and notice links are official pages found by AI. Make sure the address is on the organization’s official domain before using it.

Timeline

  1. The leak of about 159,000 customer personal records at 29CM became known.
  2. The scale of the leak through the order lookup API became known as 159,852 records, and the company apologized.
  3. It was pointed out that the leak occurred just two months after the company obtained information security certification, along with the need to strengthen the certification.
  4. A further leak of 30,000 personal records at 29CM became known.

36 related reports

The summary and key facts are written by AI from related reports and may contain errors. Check the original articles and the organization’s official statements for accurate details.