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
Metascan Confirms Limited Data Breach After Two-Minute Telegram Bot Compromise
Metascan has publicly acknowledged a data breach involving internal materials obtained through a compromised Telegram bot token. The attacker gained access to a corporate Telegram chat for approximately two minutes on September 5 and exported a small set of documents before being removed. The incident stemmed from an overlooked bot token on test virtual machines after an employee departure. Among the leaked items were two pilot project reports from July 2026 that mentioned major Russian organizations including Transneft, Selectel, Lenta, Sberbank, and Rostelecom. Metascan attributed the leak to a former employee now working with a competitor and rejected claims of deliberately hidden vulnerabilities. The company has accepted full responsibility, outlined corrective measures, and launched a bug bounty program.
Unauthorized Access to Japan's Government Solution Service (GSS) Exposes 246,000 Personal Records via VPN Flaw
Japan's Digital Agency confirmed that its Government Solution Service (GSS) suffered unauthorized access after attackers exploited a vulnerability in VPN equipment used for external maintenance operations. The intrusion, believed to have begun in late May 2026, allowed threat actors to compromise maintenance accounts and access large volumes of files on internal servers. On June 25, 2026, security teams detected suspicious access to numerous files using a compromised account, prompting an investigation that concluded on July 9 with confirmation of the breach. Some files containing personal information may have been exfiltrated, affecting approximately 246,000 records of government officials, civil servants, contractors, and related individuals. The agency immediately disabled the affected accounts and severed external communications on July 9 but has not disclosed technical details of the exploited VPN vulnerability. The incident was reported by Security NEXT on September 11, 2026.
Dropbox Accounts Compromised Through Lenovo ID Authentication Flaw
Several thousand Dropbox accounts were breached between August 4 and 21 due to an authorization flaw involving Lenovo ID. The root cause was an error on Lenovo's side that permitted registration of accounts using arbitrary email addresses, which could then be used to access matching Dropbox accounts. Dropbox responded by forcing logouts for all users who had relied on Lenovo ID and by requiring direct password entry for Dropbox credentials. Approximately 5,000 accounts were affected, though only about one-third saw stored files accessed by attackers. Accounts protected by two-factor authentication remained unaffected. Additional reports from the same period covered Kaspersky analysis of ValleyRAT spyware using DLL sideloading, a critical SQL injection vulnerability in the All-in-One WP Migration WordPress plugin, and a Google Chrome update addressing CVE-2026-85046 in the V8 engine.
Detecting and Removing Secrets from Git History with Betterleaks and git-filter-repo
Developers often accidentally commit sensitive data such as API keys, passwords, database dumps, or private uploads to Git repositories. Even after removal in a later commit, these secrets remain accessible in the commit history and can be recovered by anyone with repository access. The recommended approach begins with scanning the entire history using specialized tools to identify leaked credentials across all branches and past commits. Once identified, the secrets must first be rotated or revoked before any history rewriting occurs. Tools like Betterleaks provide detection with keyword filtering, entropy analysis, and Base64 decoding, while git-filter-repo enables precise removal of files and replacement of secret strings throughout the repository timeline. The process requires careful backups, coordination with teams, and force-pushing rewritten history, followed by fresh clones for all contributors and CI/CD systems. Even after cleanup, organizations must assume that old secrets may persist in forks, backups, or caches and therefore treat rotation as mandatory.