ENKR

Yes24 ransomware, possible personal-data leak

Add to my breach check

Made public

What leaked4

Hard to replace

  • Mobile number
  • Home or delivery address
  • Username

Permanent

  • Full name

To-dos4 · about 45 min in all

  1. Know the scam pattern: calls and texts that cite these leaked detailsabout 5 minfreeLimits harm from: phishing messages, scam calls
  2. Register as an exposed person with the FSSabout 10 minLimits harm from: scam calls (opens in a new tab)
  3. Block new loans and cards in your nameabout 10 minLimits harm from: scam calls (opens in a new tab)
  4. Remove your address and phone from public profiles and tighten SNS privacyabout 20 minfreeLimits harm from: visits or contact at home

What happened next22 events

  1. Undetected 3 events0 days · show events
  2. Response 11 eventsNo individual notice on record · show events
  3. Remedy 3 eventsEnded · show events
  4. Penalty 5 eventsOngoing · Back to latest
  5. DisputesNone on record

Penalty: 5 events

Back to latest
  1. KISA H1 2025 threat report: services down about five days; no off-site backup, so restored through negotiation with the attacker
  2. Yes24 agreed to KISA technical support
  3. Police cybercrime unit opened a preliminary inquiry
  4. PIPC opened a personal-data leak investigation
  5. MSIT and KISA required Yes24 to preserve and submit incident data
Company
Yes24
When it happened
Company detected it
Made public
Notice
Possible leak
Affected
unknown; abnormal member-information lookups reported

How the facts developed

  1. Notice that, if a leak is confirmed, affected customers will be told individually which items leaked, naming name, ID, contact and address (press)
  2. Statement naming ransomware as the cause and saying no member data had leaked (press)

Sources