Organisational risksCenter for AI Safety§4

Powerful AI gets leaked or stolen

Seen in real incidents11 matching case files

The warning

AI models could be leaked by accident or stolen by state, industry or criminal actors, which is why AI developers need state-of-the-art information security.

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

What the registry shows

Model weights have not been publicly reported stolen, but leaked keys exposed private models, outsiders reached a restricted model, source code shipped by accident, and AI companies accuse rivals of copying model capabilities through mass querying.

Verified case files show this risk happening in the real world. First real-world case on file: Jan 29, 2025.

Matching case files per quarter

Status history

Date	Status	Matching case files	Change
Oct 18, 2026	Seen in real incidents	11	Tracking 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

Seen in real incidents Accidents with AI are hard to avoid
Seen in real incidents AI developers' own safety measures fail

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)