15-Year-Old Saitama Student Uses ChatGPT to Mass-Cancel 46,812 Bandai Channel Subscriptions, Triggering Service Outage and Data Breach Concerns
A 15-year-old student from Saitama Prefecture has been arrested for orchestrating a sophisticated cyber attack that resulted in the mass cancellation of 46,812 user subscriptions on the popular anime streaming service Bandai Channel, operated by Bandai Namco Filmworks.
According to Japanese police, the teenager developed a custom program capable of simulating legitimate user requests to delete accounts. The original code, written while he was still in middle school, processed requests too slowly, prompting the student to consult ChatGPT and rewrite the script in a more efficient programming language.
On November 4, 2025, the optimized program was used to flood the service’s servers with fraudulent deletion commands, causing the platform to automatically terminate tens of thousands of accounts and forcing the company to suspend operations temporarily.
When Bandai Namco Filmworks attempted to block the attacker’s access, the student evaded detection by rotating his IP address more than 30 times, demonstrating that the assault was deliberate and sustained rather than accidental.
Investigators later discovered that the same individual had already come to police attention in June, when he was detained in connection with other computer crimes. During questioning, the teenager stated that he held no grudge against the company and had acted simply to gain access to a large number of user accounts.
Company Response and Data Protection Concerns
Bandai Namco Filmworks filed a formal complaint with the Tokyo Metropolitan Police Department in November 2025. In December, the company publicly acknowledged a possible compromise of personal information belonging to up to 1.36 million accounts, including email addresses, account balances, and payment details.
Despite the scale of the potential exposure, the firm confirmed that no evidence of data publication or secondary misuse has been detected. The company stated it takes the incident seriously and will implement regular security audits to prevent recurrence.
Police officials warned that the perceived anonymity of the internet can create a false sense of impunity, noting that such actions carry serious legal consequences regardless of the perpetrator’s age.
Related articles
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.
South Korean Medical Beauty Platform Gangnam Unni Suffers API Breach Exposing 220,000 Users' Sensitive Photos and Medical Records
Healing Paper, operator of South Korea's largest medical beauty information platform Gangnam Unni, confirmed a data breach affecting nearly 220,000 customers after an API endpoint used to query consultation records was abnormally accessed. The incident exposed highly sensitive personal information including names, contact details, medical consultation reasons, treatment progress, uploaded pre-procedure photos, appointment times, actual procedures performed, and payment information. Approximately 160,000 South Korean users and 60,000 overseas users were impacted, including 481 from mainland China, 4,218 from Taiwan, and others from Japan and Thailand. Attackers exploited weak authentication and rate limiting on the API, first detected on September 4, with a second attempt on a different path the following day. The breach raises risks of targeted phishing and extortion using victims' private medical images and records. Healing Paper has reported the incident to authorities, implemented enhanced authentication and monitoring, and allowed users to check their exposure status within 30 days.
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.