Cases › security breach › LR-2026-0364
Kuaishou livestream platform hit by AI-assisted bot attack
Preliminary Why: Publisher not yet named · subject to change
Status: action reported, no fix
No source states: loss or records, developer and model, agent tool, could do, deployer.
Severity moderate: Test: data or systems of others touched with a bounded scope stated. The sources state user data was compromised and that the scope was the livestreaming section, with all other services unaffected.
Kuaishou, a Chinese short-video platform, reported an attack on its livestreaming section in which bot accounts flooded the service with illicit streams. According to reports, about 17,000 bot accounts broadcast pornographic and violent material during a 90-minute siege that bypassed security systems and compromised user data. Experts said the attackers likely used automated tools to solve CAPTCHAs and generated the streams with AI-made faces or looped recordings. Kuaishou shut down all livestreaming channels, which also cleared legitimate content, and later restored the function after system repairs. The company said it reported the incident to regulators and public security authorities.
What happened
What was done
Risks
Primary96 incidents
Rising: 24 vs 4.0 a week
Read from the sources; not yet reviewed by a person.
Controls
ModelNot effective Content safety classifiers
HarnessEffective Stop control
Infrastructure / targetNot effective (bypassed) Bot and scraping defences
Control failure chain
L1 · ModelProvider not namedModel provider
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, 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
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 effective |
| 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 |
| Bot and scraping defences | L4 Infrastructure / target | Not effective (bypassed) |
| 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 |
Evidence
- Cause a safeguard that was in place did not hold
No source states: what the AI was doing, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, what set it off.
Show the full account: 8 items from the primary sources
What happened, in order
Not dated in the sources:
- The coordinated assault began.
- Attackers deployed about 17,000 bot accounts to broadcast pornography and violent material.
- Kuaishou initiated a blanket shutdown of all livestreaming channels.
- The livestreaming section appeared cleared out, including legitimate content.
- Kuaishou stated the attack overwhelmed its moderation defences.
- Kuaishou confirmed it had been maliciously targeted by cybercriminal groups and that emergency measures were taken.
- Kuaishou restored its livestreaming function after extensive system repairs.
- Kuaishou reported the incident to relevant regulators and public security authorities.
Show every field, with its source and grade
What happened
Impact
Context
Notes on gaps
The sources describe an attack by cybercriminals using automated bots, CAPTCHA-solving services and AI-generated faces. Reversibility is not stated.
LR-2026-0364 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON