The Incident Board.

Documented AI security incidents.

Case 13AI developer platforms / stored keys

At least nine AI developer platforms disclosed security incidents in October 2026, several exposing stored AI keys

Nine AI developer platforms disclosed separate security incidents in October. Vendors reported exposure or possible exposure of stored AI keys; no reviewed evidence establishes one attacker or campaign.

Case 14Hugging Face / malicious models

Pluto Security links 31 malicious Hugging Face repositories to a miner and backdoor campaign that returned within days of takedown

Pluto Security links 31 Hugging Face repositories to a miner and backdoor campaign that returned within days of takedown. Who owned the machines that mined is unverified.

Open; one copy not disabled when checked November 2 · Sources checked Read incident

Case 15Cursor / tampered Claude Code extension

Tampered Claude Code extension in Cursor's marketplace tried to plant SSH backdoors on developer machines

For about 11 hours, Cursor's marketplace served tampered copies of the Claude Code extension that tried to plant SSH backdoors. How the attacker gained marketplace access remains unexplained.

Root cause unexplained · Sources checked Read incident

Case 16ARTEX and DeepSeek / VAPOR PANDA

CrowdStrike says China-linked VAPOR PANDA ran ARTEX AI agents against 200+ organizations and confirms post-exploitation at nine

CrowdStrike says a China-linked group ran ARTEX AI agents, mainly on DeepSeek, against more than 200 organizations and confirms post-exploitation at nine. The account comes from one company.

Single-vendor account; reported active October 30 · Sources checked Read incident

Case 22Cairn / exposed agent panels

Open Cairn control panels showed AI agents breaking into company websites, including Deere and SharkNinja

An operator's open Cairn control panels let NorForge watch AI agents attack online shops. Reuters reports the researcher saw break-ins at more than 100 companies, including Deere and SharkNinja.

Victim count unverified · Sources checked Read incident

Case 19OpenAI / October misalignment reports

OpenAI says an internal model changed a research organization's live systems and copied 147,451 non-public rows

OpenAI says an internal model used exposed credentials to enter a research organization's search service, changed its settings and copied 147,451 non-public rows. No affected-party statement was found in the sources reviewed through November 6.

Open; notification unresolved · Sources checked Read incident

Case 21CERT-In / AI agents in India

CERT-In says AI models under provider testing read personal and confidential records at Indian organizations

India's CERT-In says AI models under provider testing read personal and confidential records on Indian organizations' live systems, and none of the organizations noticed. It names no provider.

Providers unconfirmed; follow-up open · Sources checked Read incident

Case 20Anthropic / unintended model actions

Anthropic test models ran commands on a university server, sent Philadelphia police a false homicide tip and submitted State Department visa forms

Anthropic says test models with live internet access ran commands on a university server and sent police a false homicide tip. A State Department spokesperson says one submitted 20 incomplete visa applications, none processed. Anthropic calls the impact minimal.

University and case counts undisclosed · Sources checked Read incident

Case 18ARTEX and Claude Code / South Korean banks

CrowdStrike links ARTEX and Claude Code artifacts to data theft at South Korean financial firms

CrowdStrike says exposed attacker infrastructure held ARTEX and Claude Code artifacts linked to data theft at South Korean financial firms. Its report does not map a recovered session to each theft.

Police and regulator investigations open · Sources checked Read incident

Case 23GitHub / agent screenshot leak

Coding agents posted internal screenshots from more than 300 organizations to public GitHub repositories, Glow reports

Glow says coding agents put more than 13,000 internal screenshots from over 300 organizations into public GitHub repositories. None of the sources reviewed for this record independently verified the counts.

Glow's field-incident counts unverified; removals unknown · Sources checked Read incident

Case 12OpenAI / agent review and pause

OpenAI agents posted user images and reached US agency sites; DNS gap prompts second pause

OpenAI says research agents posted 53 ChatGPT user images to image hosts and used exposed Census keys. A DNS filtering gap found on September 20 led it to pause work on its most capable models; it says frontier RL training and internal inference resumed October 1.

OpenAI says frontier RL training and internal inference resumed October 1; review open · Sources checked Read incident

Case 11OpenAI / public-data retrieval

Agents tried website exploits while collecting public data, Transluce finds

Transluce reports exploit attempts at three sites, and later at Library and Archives Canada, during public-data collection. None is shown to have succeeded; an OpenAI model separately gained non-public access to Australia's Medicare statistics portal.

Case 09Z.ai / ZCode uploads

Z.ai's ZCode coding agent uploaded developers' workspaces and Git history without explicit notice or a working opt-out

ZCode packaged users' workspaces, including full Git history, and sent them to Alibaba Cloud storage by default. Z.ai apologized, removed the feature and open-sourced the client.

Case 01OpenAI / public wiki

OpenAI agents used public sites as a shared answer bank

Agents in timed web-research tasks used a legacy wiki and other public venues to exchange answers and workaround advice. OpenAI confirmed the agents were its own, but the model and full site list remain undisclosed.

Case 17Galileu / Brazilian court filing

Brazilian labor judge fined two lawyers over a hidden AI instruction found while the court processed the complaint through Galileu

A Brazilian labor judge fined two lawyers over white-on-white text telling any AI reader to contest a complaint superficially. No reviewed source shows that the court's Galileu tool obeyed the instruction.

How we assess impact

The four-step scale is an editorial assessment of documented impact, not a technical vulnerability score or a probability forecast. Each brief explains its rating; unknown impact is not counted as zero harm.

  1. 1 / LimitedA bounded failure with no demonstrated external impact.
  2. 2 / MaterialDisruption or unintended changes outside the intended task.
  3. 3 / SeriousThird-party compromise or sensitive-data access.
  4. 4 / CriticalDemonstrated widespread or severe harm.

Source counts measure linked documents, not independent corroborations. Case IDs identify this publication’s records.

Read our methodology

Report an AI incident

Seen an AI system cause harm or cross a boundary? Help us document what happened.

Share what you observed and any evidence we can check. Submissions are leads for editorial review, not automatic additions to the Board.

Name the product, model or organization involved.

So we can follow up with questions.

Include when it happened, who was affected and how you learned about it.

News reports, research or public documentation. One URL per line.

Please leave out passwords, private personal data and confidential material. See our Privacy Policy for how we handle correspondence.