AI Agent Incidents
Every public case of an AI agent wrecking production data, on its own or aimed by someone. Every row links to the receipts. Nobody here is judging. Much.
The 23 so far, at a glance
How the 18 accidents ended
The 5 agent-assisted attacks are left out: recovery doesn't apply.
Only 6 of the 18 accidents got everything back, and 5 started with a routine schema migration or reset. Before an agent runs migrations, check that its credentials can't also delete your backups.
AI agent incidents in production, newest first
Showing all 23. Number 24 is coming: get the alert. Know one we missed? Email us
How we count
What counts
An AI agent's actions damaged production data, backups or cloud resources, or caused an outage. Attacks run through an agent count, tagged agent-assisted.
What doesn't
Damage on someone's own laptop. Ransomware (see the ransomware tracker). Demos with no real victim. Vendor marketing.
How we source
Company statements, the affected person's own report or credible press, linked on every row. A person approves each row.
Are you a peak datamaxxer?
Take the quiz