Incident record
강남언니 (힐링페이퍼)
Gangnam Unni (Healing Paper) · Healthcare
This record separates what has been publicly claimed, investigated, and confirmed. It does not imply that every affected account belongs to a unique person.
Reported impact
219,665 users
Disclosure recorded
2026-09-08
Sector
Healthcare
Practical risk
Critical
What this means
A practical reading of this record
The public record supports a critical practical risk level based on the currently reported scope and data categories. This can change if the organisation or regulator updates the record.
- Change the password for this service through its official app or website. Change it anywhere you reused it.
- Review card or bank activity and contact the issuer through its official channel if anything looks unfamiliar.
- Expect targeted phishing and account-recovery scams. Do not share verification codes with an unsolicited caller.
Classification
Categories are assigned only where the currently stored public record supports them. A privacy decision is not automatically treated as a hacking incident.
Evidence status
Why it appears in the index
Confirmed by the organisation, a regulator, or a documented official decision.
Healing Paper reported that 219,665 domestic and international users were affected, including about 160,000 in South Korea. The reported data can include contact details, consultation and treatment information, consultation photos, and, for some users, payment details. The company said it reported the incident to KISA and requested a police investigation.
Recorded source · Healing Paper disclosure and Korean media reporting ↗
Editorial record
Review and status trail
Last reviewed
2026-09-21
The latest editorial review of the stored public record.
Latest source event
2026-09-08
The most recent dated event currently documented on this page.
Confirmed
Current status recorded from the first documented public event in this entry.
Documented events
Public timeline
- 01
Unauthorised API access detected
Healing Paper detected abnormal access to an API used to retrieve consultation records and blocked the route.
- 02
Second access attempt blocked
The company reported blocking a further attempt through another route while applying emergency security measures.
- 03
Public reporting
The incident and an affected-user count of 219,665 were publicly reported following the company notice.
Data reported exposed
Protect your account
Change your password if you use this service
Use a new, unique password through the official app or website. Change any other account where you reused it, and enable a passkey or two-factor authentication when available.
Correction
Is something inaccurate or outdated?
Send a public source or official correction. Material updates are logged rather than silently replacing the record.