Rogue AI incident statistics
Publicly reported incidents where AI acted outside or against its operator's intent, affecting organizations or services and their users. These are RogueWatch catalogue counts, not a worldwide total. Active counts include confirmed, reported and claimed records; retracted and sample records are excluded.
Dataset last updated: 2026-10-30T04:28:22Z. Counts cover the complete active catalogue, including claimed cases; retractions are listed separately.
How many rogue AI incidents has RogueWatch tracked?
RogueWatch tracks 20 active publicly reported rogue AI incidents: 20 confirmed, 0 reported and 0 claimed. 0 retracted records are excluded from that total. These are catalogue counts under RogueWatch's inclusion rules, not a worldwide total. The latest record update in this snapshot is 2026-10-30T04:28:22Z.
- confirmed
- 20 — Confirmed by the victim, the AI provider, a government, or 2+ independent sources.
- reported
- 0 — Reported by at least one credible outlet or researcher; not yet independently confirmed.
- claimed
- 0 — Claimed by the attacker or a single unverified party.
- Disputed
- 0 active records; included in the confidence totals above.
- Retracted
- 0; excluded from all active totals and tables.
Which organizations are named in rogue AI incidents?
RogueWatch lists 9 distinct named organizations or services in its active records, including OpenAI (internal research infrastructure); DSEwiki (Deutsches Software-Entwickler-Wiki); Hugging Face; PocketOS; SaaStr. 10 active incidents do not identify a named affected organization. Organization counts use published names, group case-insensitively and split semicolon-separated names; they are not a total of all affected organizations or people.
| Organization / service | Incidents | Supporting records |
|---|---|---|
| OpenAI (internal research infrastructure) | 3 | RW-0036, RW-0037, RW-0038 |
| DSEwiki (Deutsches Software-Entwickler-Wiki) | 1 | RW-0021 |
| Hugging Face | 1 | RW-0019 |
| PocketOS | 1 | RW-0035 |
| SaaStr | 1 | RW-0034 |
| Services Australia (Medicare Statistics Reporting Service) | 1 | RW-0020 |
| US Department of Commerce | 1 | RW-0023 |
| US Securities and Exchange Commission | 1 | RW-0023 |
| Wikimedia Foundation (Wikidata, Etherpad) | 1 | RW-0033 |
Which AI providers and systems appear in rogue AI incident reports?
Active RogueWatch records name 5 AI providers: OpenAI (12 incidents); Anthropic (6 incidents); Google (1 incident); Meta (1 incident); Replit (1 incident). Multiple providers can appear in one incident, so provider counts must not be added to calculate an incident total. A provider being named does not establish fault or measure overall model safety. Provider attribution is separate from incident confidence and can be confirmed, reported or unknown.
| Provider | Incidents | Supporting records |
|---|---|---|
| OpenAI | 12 | RW-0019, RW-0020, RW-0021, RW-0022, RW-0023, RW-0027, RW-0031, RW-0032, RW-0033, RW-0036, RW-0037, RW-0038 |
| Anthropic | 6 | RW-0024, RW-0025, RW-0026, RW-0027, RW-0030, RW-0035 |
| 1 | RW-0029 | |
| Meta | 1 | RW-0028 |
| Replit | 1 | RW-0034 |
0 active incidents contain an unknown system attribution or identify no AI system. Named-provider counts exclude unknown attributions. Inspect models, roles, confidence and sources for each incident.
How many tracked incidents occurred each year?
Years below describe reported occurrence, rather than when RogueWatch added the record. Month-only and year-only dates contribute only to their known year. These figures describe this catalogue; a missing year is not proof that no incidents occurred.
How to cite these statistics
Attribute these figures to RogueWatch, link to this statistics page, and state the dataset update timestamp and your access date. Include the confidence breakdown and coverage limits when quoting the total. For a specific event, cite its permanent incident page and the original sources listed there.
Download source-linked incident data (JSON) · Download these counts (JSON) · RSS updates
These pages and downloads are generated from the same records on every site build. Counts can change after additions, corrections or retractions. Read the inclusion rules and correction policy.