extract 0 0 0

emmanuelgjr/genai-incidents

published by @emmanuelgjr

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
871
Last 30 days
200
Likes
8
Size
36.6 MB
Created on HF
2026-06-03
Age
4 months ago

Description

GenAI & Agentic AI Security Incidents

15,637 real-world and research incidents involving generative-AI and agentic-AI

systems — prompt injection, jailbreaks, data exfiltration, deepfakes, model and

supply-chain compromise, agent hijacking, and AI-enabled harms — cross-mapped to six

taxonomies. Dataset version 2.13.0.

Every applicable incident is tagged with four core taxonomies:

OWASP Top 10 for LLM Applications (2026) — LLM01–LLM10

OWASP Top 10 for Agentic Applications (ASI) —… See the full description on the dataset page: https://huggingface.co/datasets/emmanuelgjr/genai-incidents.

Tags

task_categories:text-classificationtask_categories:text-retrievallanguage:enlicense:cc-by-4.0size_categories:10K<n<100Kformat:jsonmodality:tabularmodality:textlibrary:datasetslibrary:pandaslibrary:polarslibrary:mlcroissantregion:ussecuritycybersecurityai-safetyai-securityllmagentic-aiincidentsthreat-intelligenceprompt-injectionowaspmitre-atlasnist-ai-rmf

README current version from Hugging Face


license: cc-by-4.0
language:

  • en
    pretty_name: GenAI & Agentic AI Security Incidents
    tags:
  • security
  • cybersecurity
  • ai-safety
  • ai-security
  • llm
  • agentic-ai
  • incidents
  • threat-intelligence
  • prompt-injection
  • owasp
  • mitre-atlas
  • nist-ai-rmf
    task_categories:
  • text-classification
  • text-retrieval
    size_categories:
  • 10K<n<100K
    configs:
  • config_name: default
    data_files: incidents.jsonl

GenAI & Agentic AI Security Incidents

15,637 real-world and research incidents involving generative-AI and agentic-AI
systems — prompt injection, jailbreaks, data exfiltration, deepfakes, model and
supply-chain compromise, agent hijacking, and AI-enabled harms — cross-mapped to six
taxonomies. Dataset version 2.13.0.

Every applicable incident is tagged with four core taxonomies:

  • OWASP Top 10 for LLM Applications (2026) — LLM01–LLM10
  • OWASP Top 10 for Agentic Applications (ASI) — ASI01–ASI10
  • NIST AI RMF (AI 100-1) — GOVERN / MAP / MEASURE / MANAGE
  • MITRE ATLAS — techniques (AML.T00xx) and tactics (AML.TA00xx)

Plus, where available:

  • MAESTRO architectural layers (L1–L7) — companion, carried where the upstream source provides it
  • VERIS 1.4.1 crosswalk (veris:* tags) — experimental, computed at export time from attack_vector, not a stored per-incident field

Quickstart

from datasets import load_dataset
ds = load_dataset("emmanuelgjr/genai-incidents", split="train")

# prompt-injection incidents
ds.filter(lambda r: "LLM01" in (r["owasp_llm"] or []))

# only maintainer-reviewed entries
ds.filter(lambda r: r["quality_tier"] in ("reviewed", "curated"))

# the landmark tier -- the headline-citation set this project asks
# you to cite, rather than the full corpus (which is mostly CVE/advisory bulk)
ds.filter(lambda r: r["tier"] == "landmark")

What's inside

Key fields per record (full reference in the data dictionary):

  • id, title, description, date, year, severity
  • attack_vector — normalised exploit/harm class (e.g. prompt-injection, deepfake, rce)
  • owasp_llm, owasp_asi, nist_ai_rmf, mitre_atlas, mitre_atlas_tactics — framework mappings.
    Pinned taxonomy versions for this release: atlas 2026.09, owasp_llm 2026, owasp_asi 2026, capec unversioned, veris 1.4.1
  • cve_ids, cwe_ids, cvss_score — where applicable
  • references — source URLs · source_ids — upstream provenance
  • quality_tier — curated / reviewed / auto (filter by vetting level)
  • tier — landmark (the headline-citation set: rows that are hand-curated, catalogued
    in the AI Incident Database, or AI-harm cases) or feed (everything else: mostly
    CVE/GHSA/OSV advisories, plus OECD AI Incidents and Hazards Monitor incident reports). A different axis from quality_tier, not a rename of it:
    most landmark rows qualify by being catalogued in the AI Incident Database, which
    says nothing about vetting level. Cite the landmark count, not the corpus total,
    when you mean "headline incidents"
  • corpus — security or ai-harm
  • source_freshness — present only on rows whose upstream source has stopped refreshing (see below)
  • status — present only on a row that is not standing as published (absence means it stands).
    22 of the rows above carry status: disputed: every CVE record they rest on is
    listed by the CVE Program as published but disputed. They are counted in the 15,637
    and carry a lowered confidence; retracted rows are omitted from this export.

Source freshness

Some rows carry a source_freshness object ({status, as_of, sources, review_by}). It says that
the upstream source that supplied the row has stopped refreshing — not that the row
was withdrawn, superseded, or is wrong. The two are independent facts, and the field
exists because conflating them is how a dataset comes to mislead without any single
value being false: this corpus is rebuilt from committed ingest snapshots, so a row keeps
being emitted long after its upstream download disappears. In particular
source_status: "active" means emitted on the latest build, never re-checked
against a live source
.
sources names the stale sources by their key in the
repository's published freshness registry (data/source_freshness.json), and as_of is
the earliest last_success date recorded there for those sources — a date taken from the
registry, not the build date. Everything that source contributed to the row,
including any taxonomy or risk-tier tags it supplied, is current through as_of and no
further. review_by is the date a human is due to re-decide whether that source is
refreshed or retired (the until of the registry hold); it is a declared date that
nothing evaluates, not a claim that anything happens then. Absence of the field means no tracked source feeding the row is known to be
stale — not that the row has been verified current. Full definition, the registry's own
fields, and what the registry does and does not cover:
docs/DATA_DICTIONARY.md → Source freshness,
which is authoritative; this is a summary of it.

Sources & provenance

Aggregated and de-duplicated from AIID, OECD AI Incidents and Hazards Monitor, AIAAIC, MITRE ATLAS,
AVID, MIT FutureTech AI Risk Repository, NVD / GitHub Security Advisories / OSV, garak,
promptfoo, red-team benchmark catalogues, and researcher blogs / vendor threat reports.

Intended uses & limitations

Built for security research, red-team scenario design, taxonomy / benchmark work, and
trend analysis. It is not an exhaustive census: coverage skews toward
English-language, publicly-reported events, and auto-tier rows are bulk-ingested
without individual review — filter on quality_tier for higher-confidence subsets. See
the datasheet for full scope, collection method, and limitations.

Licensing

Data is released under CC BY 4.0 overall (license: cc-by-4.0 above; see
LICENSE-DATA and NOTICE-DATA in the source repository). A subset of entries that
cite the AIAAIC Repository — those whose description derives from
AIAAIC's sheet (description_source == "aiaaic") plus a smaller set of hand-curated
rows whose title and categorical facts derive from AIAAIC directly (current count
audited in docs/SOURCE_LICENSES.md §1.1, not restated here to avoid drift) —
carries an additional, row-level CC BY-SA 4.0 attribution/share-alike obligation — this
does not apply project-wide, only to those specific rows. Each such row carries a
machine-readable content_license field (source, license, attribution,
obligations) naming AIAAIC as the attribution target; redistributing or adapting
one of those rows' content should honor that row's attribution and share-alike
obligation. A separate, open question about an EU/UK sui generis database right
over the AIAAIC extraction is tracked in the source repository's NOTICE-DATA and
docs/SOURCE_LICENSES.md (§1.1) and is not resolved by this row-level marker.

Rows sourced from the OECD AI Incidents and Hazards Monitor (AIM) carry a
narrower, separate obligation: description on those rows is reduced to
structural facts and a source link only (never AIM's LLM-generated
summary/evidences, machine output derived from copyrighted third-party
news of unresolved ownership). A small number of rows instead ship another
source's description, where that source won the merge; every OECD AIM-sourced
row carries a per-entry citation (OECD (year), AI Incidents and Hazards Monitor, url (accessed on date)) regardless of which description it ships.
The title field is not covered by the reduction and remains an open
question, tracked at the same posture as the AIAAIC headline question above.
Exact per-row counts and the merge-precedence exceptions: title's in
NOTICE-DATA; description's in docs/SOURCE_LICENSES.md's OECD AIM
summary-of-outcomes row (§1.5 covers the full licensing analysis), in the
source repository.

Links

Licence: data CC-BY-4.0 (see Licensing above for row-level AIAAIC obligations), code MIT.

README history 17 revisions

Every night we snapshot the README of every dataset in the catalog. When the SHA changes we archive the new version and diff it against the last. This is the evolving thought record of the alignment-data field: what the author decided to say about the corpus, and how that framing shifted over time.

  1. 2026-10-13Upload folder using huggingface_hub06045778.8 KB
    Loading...
  2. 2026-10-04Upload folder using huggingface_hub987c2b37.8 KB
    Loading...
  3. 2026-10-01Upload folder using huggingface_hubb07ae677.8 KB
    Loading...
  4. 2026-09-18Upload folder using huggingface_hub56ad8097.3 KB
    Loading...
  5. 2026-08-01Upload folder using huggingface_hub94192597.3 KB
    Loading...
  6. 2026-07-13Upload folder using huggingface_hub73bae823.2 KB
    Loading...
  7. 2026-07-03Upload folder using huggingface_huba708dca3.2 KB
    Loading...
  8. 2026-07-02Upload folder using huggingface_hub04ab4913.2 KB
    Loading...
  9. 2026-06-11Upload folder using huggingface_hubaeb81d13.2 KB
    Loading...
  10. 2026-06-11Upload folder using huggingface_hub9a5fdb93.2 KB
    Loading...
  11. 2026-06-11Upload folder using huggingface_hub1d86c253.2 KB
    Loading...
  12. 2026-06-10Upload folder using huggingface_hub0fbf76f3.2 KB
    Loading...
  13. 2026-06-10Upload folder using huggingface_hubf1724963.2 KB
    Loading...
  14. 2026-06-03Upload folder using huggingface_hub19471d63.2 KB
    Loading...
  15. 2026-06-03Upload folder using huggingface_hub2e313a11.4 KB
    Loading...
  16. 2026-06-03Upload folder using huggingface_hub4e18fcd1.4 KB
    Loading...
  17. 2026-06-03initial commitcdbdefa0 B
    Loading...

Used by abliterated models none yet

No abliterated models in our catalog have declared this dataset in their YAML metadata yet. This can mean the dataset is used but not declared, is used outside abliteration workflows, or is new. The link will populate automatically as models are indexed.

Community discussions 1 thread · 1 open · 1 comments

Threads posted by the community on Hugging Face: bug reports, questions about usage, pull requests on the README, license clarifications. Click any thread to expand and read the full conversation inline. Newest first.

  1. 2026-06-04[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · extract

Read further

Metadata

License
cc-by-4.0

Repository

Download the dataset

0

Copy any of these snippets into your notebook or terminal. All three fetch directly from Hugging Face using your own credentials.

Recommended: datasets library (Python)
from datasets import load_dataset
ds = load_dataset("emmanuelgjr/genai-incidents")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="emmanuelgjr/genai-incidents", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/emmanuelgjr/genai-incidents
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration