Try the new OrcaCyber Zero 1.5 — connect to any cyber harness for offensive security, zero-days & AI defense 🐳Get API
Open database · CC BY 4.0

Every AI agent incident,with its receipt.

An open, month-by-month database of real-world AI agent security events. Every record carries at least one source and a verdict on whether anyone was actually harmed.

396 records · 2024-12 → 2026-10-09 · 729 unique sources

Share

Every record, placed in the month it happened

one block = one record · click a month to filter · shift-click for a range
396
records
141
confirmed real harm
729
sources
48
critical
23
months covered
86%
grade A sourcing

The method

Three questions every record answers before anything else

Most incident lists collapse the one distinction that matters: an agent that actually caused damage is not the same thing as a researcher showing that it could. Every bar below is a live filter.

Was anyone actually harmed?

A confirmed victim, not a proof of concept. This is the field that separates a breach from a conference demo.

Was the AI involvement confirmed?

By a primary source — the vendor, the victim, law enforcement or an official report. Disputed attributions stay in, and stay labelled.

What kind of record is this?

An incident, a vulnerability disclosure, a research demo, a threat report or a policy move. Counting them together is how the headline numbers go wrong.

Attack surface

Twelve ways an agent gets turned into a liability

Each record is tagged with one or more of these. The sparkline is that type’s own record count month by month — click a tile to filter the database below.

Landmarks

The records that moved the line

Critical severity, a confirmed victim, and a primary source you can click. The strip on each card is that record’s own month, drawn in the same units as the timeline above.

396records
396 records

October 2026

12

September 2026

48

Methodology

How severity and confidence are decided

Confidence is about source quality, not severity. A grade of D does not mean false — it means the parties disagree and you should not cite one side alone.

Severity

CriticalConfirmed damage at scale, or a first-of-its-kind with real victims.
HighConfirmed but limited damage, a CVSS 9+ flaw, or a significant capability demonstration.
MediumA controlled demo, a moderate flaw, or a single-user incident.
LowA background entry kept for timeline continuity.
InfoPolicy, regulation and threat reports — not counted as incidents.

Confidence

A·340Primary source — the vendor, the victim, law enforcement or an official report.
B·51A research lab or a major outlet, with checkable detail.
C·2Second-hand only, with no primary source.
D·3The facts or the attribution are disputed.

Found something missing, or something wrong?

Corrections are written into the record’s revision history, never silently overwritten. Every entry needs at least one source — no source, no entry.

Filters

© 2026 OrcaRouter