AI Threat Watch

Organisational risksCenter for AI Safety§4.1

Accidents with AI are hard to avoid

Seen in real incidents15 matching case files

The warning

AI systems are complex and unreliable, so accidents are normal; the goal must be to stop accidents from cascading into disasters.

Paraphrased from the paper. Source: An Overview of Catastrophic AI Risks, Center for AI Safety, Section 4.1, page 27.

What the registry shows

Coding agents have wiped databases and drives, assistants have published private chats, and staff acting on an AI agent's advice exposed sensitive data.

Verified case files show this risk happening in the real world. First real-world case on file: Sep 18, 2023.

Matching case files per quarter

0246Seen in real incidents: 11'25 Q1Seen in real incidents: 44'25 Q2Seen in real incidents: 55'25 Q3Seen in real incidents: 11'25 Q4Seen in real incidents: 22'26 Q1'26 Q2Seen in real incidents: 11'26 Q3'26 Q4

Status history

DateStatusMatching case filesChange
Oct 18, 2026Seen in real incidents15Tracking starts

Tracked since Oct 18, 2026. A line is added when the status changes, when the first real-world case is linked, and once a month, so the record shows when a warning moved from research to reality. research_history.json

All matching case files

Other warnings in this group

Research vs reality →

How we match: a case file is linked to a warning when what happened is a real-world instance of the risk the paper describes, judged by the editors from the facts in the case file. A match means the case fits the warning, not that it proves the paper's wider argument. Allegations in lawsuits are labelled as allegations. Statuses are editorial and reviewed as new cases arrive. The matching is recomputed on every update. Data: Systematic coverage in the registry starts in 2025, so a first-case date shows when the registry first recorded the risk, not when it first happened. research.json (CC BY 4.0)

Language: EnglishFrançaisEspañolالعربية中文Русский