Incident database

How real software and AI systems failed

65 documented incidents from postmortems, regulatory filings and court records, plus 1,500 security advisories ingested every two hours. Each links to its public source and to the safeguard that addresses it.

15 records · Documented incident: A real incident summarised from a public source (postmortem, regulatory filing, court record or advisory).

Explore these 15 records in charts

Most represented patterns

Top six in the filtered results. A record can have several patterns.

  • Privileged action without an enforceable approval gate11
  • AI action exceeds its intended scope8
  • Indirect prompt injection changes agent behavior5
  • Weak or phishable authentication on a privileged path3
  • Cross-tenant access through a caller-controlled identifier2
  • Destructive operation without verified recovery1

Records by year

Up to eight recent years, plus undated records. Dates may refer to an incident, disclosure or publication.

  • 202510
  • 20241
  • 20211
  • 20201
  • 20121
  • 20101
Documented incidentIncident 2025-08-26AI agent

GitHub Actions injection leaks Nx's npm token; malicious packages use local AI coding tools to hunt for secrets (2025)

A pull-request title validation workflow used pullrequesttarget, which runs with repository secrets, and echoed the unsanitized PR title, creating an injection point; the workflow's token also had read/write permissions.

Safeguard: Never run untrusted pull-request input with secrets

Privileged action without an enforceable approval gatenx.dev