AI Threat Watch

MIT AI Risk InitiativeSeven risk domainsDomain 7

AI system safety, failures and limitations

Seen in real incidents15 matching case files

The risk domain

AI pursuing goals that conflict with ours, having dangerous capabilities, failing under real conditions, being hard to understand, and risks that arise when many AI agents interact.

Paraphrased from the source. Source: The AI Risk Repository: A Meta-Review, Database, and Taxonomy of Risks From Artificial Intelligence, MIT AI Risk Initiative, Aug 14, 2024, domain 7, Table 2, page 10. Summary by MIT AI Risk Initiative: airisk.mit.edu.

What the registry shows

Agents that wiped data, escaped test environments, reached outside systems and filed a false report. These are failures and unintended behaviour; none shows an AI pursuing goals of its own.

Verified case files show this risk happening in the real world.

Matching case files per quarter

0246'25 Q1'25 Q2Seen in real incidents: 11'25 Q3Seen in real incidents: 11'25 Q4Seen in real incidents: 22'26 Q1'26 Q2Seen in real incidents: 55'26 Q3Seen in real incidents: 66'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

The same case files in other research

Warnings from other sources that link to some of the same case files.

Other warnings in this group

Research vs reality · MIT AI Risk Repository →

How we match: a case file is linked to a warning when what happened is a real-world instance of the risk the source 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 source'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العربية中文Русский