Cases › security breach › LR-2026-0611
Teen arrested for cyberattack on Bandai Channel using ChatGPT
Preliminary Why: Publisher not yet named · subject to change
Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.
Status: fix reported
No source states: loss or records, agent tool, could do, deployer.
Severity major: Test: many third parties, a stated count of two or more affected parties. 46,812 subscriptions were automatically terminated.
A 15-year-old schoolboy in Japan, who had taught himself programming, is reported by police to have used ChatGPT to create a homemade malicious programme aimed at Bandai Channel, the anime streaming service run by Bandai Namco Filmworks. The programme cancelled the subscriptions of over 46,000 users. The teenager found a vulnerability by analysing network traffic. After the company tried to block his access, he continued by changing his IP address approximately 30 times. The company temporarily suspended the service and contacted the police. The teenager admitted the allegations. The police have not identified any misuse of the email addresses and usernames he obtained. The company contacted affected subscribers directly and said it had strengthened its security measures.
What happened
What was done
“Security measures strengthened”
Risks
Primary96 incidents
Rising: 24 vs 4.0 a week
Sorted by rule from the case's fields; not yet read from the sources.
Controls
HarnessEffective Stop control
Control failure chain
L1 · ModelChatGPTModel provider
No source mentions a control at this layer.
Model version not linked to a model card.
Other controls for this risk at this layer, not mentioned in the sources: Safety training and refusal, Cyber and weapons safeguards, Abuse monitoring and account enforcement, Staged or restricted release, Dangerous-capability testing before release, Outside red-teaming, Content safety classifiers, Safeguards kept on in testing, Reasoning monitoring.
L2 · HarnessHarness not namedAgent framework vendor
L3 · ApplicationThe attackerDeployer
The attacker ran the agent; this layer was the attacker's own.
L4 · Infrastructure / targetOrganisation hit
No source mentions a control at this layer.
Other controls for this risk at this layer, not mentioned in the sources: Known flaws patched, Multi-factor sign-in and password policy, Network segmentation, Intrusion and endpoint detection, Backups and recovery, Phishing and fraud filters.
EffectiveNot effectiveNot effective (bypassed)Did not existNot stated in sourcesNot yet checkedAttacker's ownOrder: model · harness · application · target
Controls for this risk: result in this incident
| Control | Part of the system | Result |
|---|---|---|
| Content safety classifiers | L1 Model | Not stated in sources |
| Safety training and refusal | L1 Model | Not stated in sources |
| Cyber and weapons safeguards | L1 Model | Not stated in sources |
| Dangerous-capability testing before release | L1 Model | Not stated in sources |
| Outside red-teaming | L1 Model | Not stated in sources |
| Staged or restricted release | L1 Model | Not stated in sources |
| Abuse monitoring and account enforcement | L1 Model | Not stated in sources |
| Reasoning monitoring | L1 Model | Not stated in sources |
| Safeguards kept on in testing | L1 Model | Not stated in sources |
| Stop control | L2 Harness | Effective |
| Known flaws patched | L4 Infrastructure / target | Not stated in sources |
| Multi-factor sign-in and password policy | L4 Infrastructure / target | Not stated in sources |
| Network segmentation | L4 Infrastructure / target | Not stated in sources |
| Intrusion and endpoint detection | L4 Infrastructure / target | Not stated in sources |
| Backups and recovery | L4 Infrastructure / target | Not stated in sources |
| Phishing and fraud filters | L4 Infrastructure / target | Not stated in sources |
Similar incidents
Evidence
- Other parties affected 46,812
- What was done Security measures strengthened
No source states: what it reached or did, when it was found, how many records were exposed, the direct loss, any court case, the cause, what set it off, what was done.
Show the full account: 6 items from the primary sources
What happened, in order
- 2025-11-04 Rogue commands sent to Bandai Channel servers; police say this triggered mass deletion of user profiles.
Not dated in the sources:
- Company tried to block the suspect after discovery; he kept attacking by changing IP address about 30 times.
- Japanese police arrested the 15-year-old on suspicion of the cyberattack on Bandai Channel.
- The teenager admitted the allegations.
- Company contacted affected subscribers directly and warned them about possible follow-up scams.
- Company said there was no evidence so far of leaked or weaponised user data.
Show every field, with its source and grade
The AI system
What happened
Impact
Context
Notes on gaps
Sources differ on details: Mezha says the subscriptions of over 46,000 users were cancelled, IBTimes says 46,812 subscriptions were terminated and says the subscriber count was over 46,000; IBTimes gives the attack date as 4 November 2025 while Mezha says November 2025. The 4 November date is used as the best-sourced date. The vulnerability is linked to J1 (known flaws patched) as failed by inference, since a flaw existed and was exploited. The IP-address ban being bypassed has no matching control id and is not coded. The company's strengthened security measures are not named as specific controls, so no remediation controls are listed.
LR-2026-0611 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON