South Korean Medical Beauty Platform Gangnam Unni Suffers API Breach Exposing 220,000 Users' Sensitive Photos and Medical Records
Healing Paper, the operator of South Korea's largest medical beauty platform Gangnam Unni, issued a public apology on September 7 confirming that personal data of nearly 220,000 customers had been exposed through abnormal access to an API interface.
What Data Was Leaked
The breach involved far more than basic identifiers. Exposed information included names, phone numbers, email addresses, birth dates, gender, residential locations, social media IDs, and IP addresses. More critically, it also revealed medical beauty consultation details such as requested procedures, hospital and doctor names, reasons for consultation, treatment progress, user-uploaded consultation photos, appointment times, completed procedures, visit records, and payment information. These records create a comprehensive profile of an individual's health status, appearance insecurities, spending patterns, and movement history, including highly private pre-procedure images that users would never want shared.
Of the affected users, roughly 160,000 were in South Korea and 60,000 overseas. The overseas group included 48,000 from Japan, 4,218 from Taiwan, 1,591 from Thailand, and 481 from mainland China.
How the API Became the Leak Point
The attack path was straightforward and did not require sophisticated techniques. On September 4, attackers abnormally accessed an API endpoint designed for querying consultation records. After Healing Paper blocked that path, the same actor attempted access via a different route the next day. The root cause was insufficient authentication checks and missing rate-limiting controls on backend APIs. Many platforms focus security efforts on the main website and user interface while leaving API endpoints with loose access controls, incomplete logging, and no real-time anomaly detection.
Secondary Risks After the Breach
Security experts in South Korea have warned of immediate follow-on threats. Attackers could use the detailed medical and appointment data to craft convincing phishing messages impersonating the platform or clinics, offering fake promotions or appointment reminders. Even more concerning is the potential for extortion, where victims are threatened with the release of their pre-procedure photos and treatment records unless they pay.
Remediation and Recommendations
Healing Paper has reported the incident to the Korea Internet & Security Agency, involved law enforcement, conducted a full system review, strengthened identity verification, and added abnormal access monitoring. Users can check their exposure status on the official site within 30 days of the announcement.
Security teams are advised to treat APIs with the same rigor as primary web applications: enforce strict authentication and least-privilege access, implement rate limiting and behavioral analytics on sensitive endpoints, integrate API logs into SIEM systems, and include API attack surfaces in regular penetration testing. Users who registered with Gangnam Unni or similar platforms should verify any unexpected messages claiming to be from the service or clinics through official channels before clicking links or providing information.
Related articles
Beget Loses Accreditation as .RU and .РФ Domain Registrar After Cyberattack
Following a cyberattack on November 2, Russian domain registrar and hosting provider Beget has had its accreditation temporarily suspended by the Coordination Center for .RU and .РФ domains. The company can no longer register new domains in the .RU, .РФ, and .SU zones or accept transfers from other registrars. Beget must continue supporting all domains registered before the suspension, and expiration dates have been postponed by agreement with the Coordination Center and RosNIIROS to prevent any loss of domains. The incident stems from attackers gaining access to the management infrastructure and deploying wiping scripts. Partial functionality has been restored in the control panel, but full domain management features for the affected zones will return only after accreditation is reinstated. No specific recovery timeline has been announced.
Beget Rebuilds Cloud Infrastructure After Destructive Cyberattack Wipes VPS Backups
Beget suffered a severe cyberattack that allowed threat actors to access the management layer of its entire cloud architecture and execute wiping scripts. The incident destroyed cloud infrastructure and left backup copies of VPS files available to only half of the affected users. Internal systems were also hit, breaking links between customer accounts and services, forcing the provider to reconstruct ownership records. Hosting services have recovered more than 60 percent, while full cloud restoration timelines remain unknown. The attack disrupted BelkaCar’s car-sharing application, which relied on Beget for backend connectivity and has since migrated to another provider.
Fukuoka Prefecture Exposes Personal Data of 183 Corporate Officers Due to Website File Misconfiguration
Fukuoka Prefecture has confirmed that personal information belonging to 183 corporate officers from 24 organizations was left publicly accessible on its official website. The exposure occurred within files related to the Fukuoka Prefecture Easy-to-Work Care Workplace Certification System. The files were uploaded by a contracted vendor between August 21 and September 17, 2026, with incorrect permissions that allowed online editing and saving instead of read-only access. The issue remained undetected until an applicant inquired about download procedures. Upon discovery, the prefecture instructed the vendor to remove the files and contacted all 24 affected corporations by telephone to provide explanations and apologies. The incident highlights risks associated with improper configuration of application files containing sensitive personal data on government websites.
New Container, Old Code: Web Shell Persists Three Months in 1C-Bitrix Environment
Two 1C-Bitrix sites shared a web shell named WebShellOrb after an attacker exploited multiple vulnerabilities in a custom appeal application. The initial compromise went undetected because Nginx logs were retained for only one month, leading responders to conclude that no scanning activity remained visible. After agents showed no malicious code, administrators restarted the container without addressing the underlying issues in the shared filesystem and source code. The attacker regained access weeks later by reusing JWT tokens generated with a hardcoded secret and by exploiting SQL injection flaws that allowed password hash extraction. Shared system user accounts and a common filesystem volume enabled the shell to propagate between sites and survive container recreation. The incident highlighted that redeploying containers and rotating passwords failed to eliminate persistence rooted in unpatched code and misconfigured authentication logic.