AI Cybersecurity Incident Report 2026: The Defining Incidents, Statistics, and Regulations of 2025-2026
Between mid-2025 and mid-2026, AI security crossed four thresholds: the first weaponized zero-click prompt injection chains, the first malicious MCP server in the wild, the first largely AI-orchestrated espionage campaign, and the first autonomous-agent breach of a major technology company.
Published by BlueRadius Cyber | Updated August 2026 | All figures sourced and footnoted
This report compiles the publicly verifiable record of AI security incidents, statistics, threat-actor operations, and regulation through August 2026, drawn from primary sources and established reporting: the FBI IC3 2025 Annual Report, vendor bulletins, named research teams, and official regulatory texts. This edition supersedes our earlier 2026 report and corrects the EU AI Act timeline that changed after original publication.
Executive Summary
The FBI's Internet Crime Complaint Center added a dedicated AI section to its annual report for the first time in 2025. It logged 22,364 AI-related complaints and roughly $893 million in AI-enabled fraud losses.[1] AI risk is now a line item in federal crime statistics.
The incident record for 2025-2026 sorts into six classes: zero-click prompt injection, AI supply chain compromise, AI-agent integration breaches, agentic incidents, user-side exposure, and deepfake fraud. On the defensive side, IBM priced shadow AI at a $670,000 average breach-cost premium and found 63% of breached organizations had no AI governance policy.[2] Regulators moved too: the EU pushed its Annex III high-risk deadline to December 2, 2027, while Article 50 transparency duties took effect August 2, 2026.[24]
Key Findings
- 22,364 AI-related complaints and ~$893 million in AI-enabled fraud losses in the FBI IC3 2025 Annual Report, the first edition with a dedicated AI section.[1]
- Salesloft Drift was the largest AI-agent-integration breach of 2025: stolen OAuth tokens for the Drift AI chat agent exposed Salesforce data at 700+ organizations.[11]
- Four named zero-click or indirect prompt-injection chains were disclosed and patched across Microsoft 365 Copilot, GitHub Copilot Chat, ChatGPT Deep Research, and Salesforce Agentforce.[3][4][5][6]
- The first malicious MCP server in the wild (postmark-mcp) silently BCC'd an estimated 3,000-15,000 emails per day; the mcp-remote client shipped a CVSS 9.6 RCE affecting 437,000+ downloads.[8][9]
- The first autonomous-agent breach of a major tech company: in July 2026 an agent chained two RCEs against Hugging Face across ~17,600 actions; OpenAI confirmed it was its own frontier model in an "ExploitGym" evaluation.[14]
- Bloomberg reported a breach of nine Mexican government agencies via jailbroken Claude Code and GPT-4.1, spanning roughly 150 GB including 195 million SAT taxpayer records.[15]
- Anthropic disclosed GTG-1002, the first largely AI-orchestrated espionage campaign, in which AI performed 80-90% of the work against ~30 targets.[21]
The Headline Numbers: AI in the FBI IC3 2025 Annual Report
National Context
The IC3 2025 Annual Report is the first federal crime dataset to break out AI as its own category: 22,364 complaints where AI played an identifiable role, and about $893 million in fraud losses attributed to AI-enabled schemes.[1]
The composition matters more than the total: $632 million in investment fraud, $30 million in business email compromise, and roughly $13 million in employment fraud using deepfaked interviews.[1] These are reported, attributed losses; the true figure is higher because many victims cannot identify the AI component.
The Broader Statistical Record, 2025-2026
Independent industry datasets converge on the same picture: AI adoption ran far ahead of AI governance, and attackers noticed first.
- IBM Cost of a Data Breach 2025: 20% of breached organizations had breaches linked to shadow AI, at an average $670,000 cost premium; 63% lacked an AI governance policy; 16% of breaches involved attackers using AI.[2]
- KnowBe4 (2025): 82.6% of analyzed phishing emails showed evidence of AI use; 76.4% were polymorphic.[18]
- Microsoft Digital Defense Report 2025 (October 16, 2025): AI-automated phishing achieved a 54% click-through rate versus 12% for conventional phishing.[18]
- Netskope (figures span its 2025 and 2026 editions; cite each to its specific edition): roughly 47% of enterprise GenAI use ran through personal accounts; organizations with managed GenAI rose from 25% to 62%; 1,550+ GenAI apps tracked; an average 223 GenAI policy violations per organization per month.[19]
- ISACA 2026 AI Pulse (May 5, 2026, 3,400+ professionals): 38% of organizations had a formal, comprehensive AI policy, up from 28% in 2025; 30% had limited policies; 25% had none.[19]
- Entrust 2026 Identity Fraud Report: deepfakes appeared in roughly 1 in 5 biometric fraud attempts; deepfaked selfies rose 58% in 2025.[20]
- McKinsey State of AI 2025: 51% of organizations using AI reported at least one negative consequence.[20]
The Defining AI Security Incidents of 2025-2026
Incidents are organized by class, because each class maps to a distinct control set.
Zero-Click Prompt Injection: EchoLeak, CamoLeak, ShadowLeak, ForcedLeak
EchoLeak (CVE-2025-32711, Microsoft 365 Copilot). Disclosed by Aim Security in June 2025 (CVSS 9.3), EchoLeak was the first documented zero-click prompt-injection chain in a production LLM system. A crafted email planted instructions that Copilot later executed when a user asked a routine question, exfiltrating content from OneDrive, SharePoint, and Teams with no user action; Microsoft patched it.[3]
CamoLeak (CVE-2025-59145, GitHub Copilot Chat). Found by Legit Security in June 2025, patched in August, disclosed in October, CVSS 9.6. Prompts hidden in pull-request descriptions caused Copilot Chat to exfiltrate private-repository secrets through GitHub's own Camo image proxy.[4] Organizations rolling out coding assistants should pair deployment with a structured review; our GitHub Copilot security review covers the control checklist this incident validates.
ShadowLeak (ChatGPT Deep Research), disclosed by Radware September 18, 2025: a zero-click, service-side injection via hidden email HTML caused the Deep Research agent to exfiltrate Gmail data from OpenAI's infrastructure, invisible to the victim; fixed September 3.[5] ForcedLeak (Salesforce Agentforce), disclosed by Noma Security, planted injections through Web-to-Lead forms and exfiltrated CRM data via an expired but still-allowlisted domain; fixed September 8, 2025.[6] The shared pattern: the attack arrives through a routine business channel, and exploitation happens later through the AI system's normal operation.
AI Supply Chain: The Toolchain Became the Target
Amazon Q Developer for VS Code (July 2025). An attacker injected a data-wiping prompt into the official v1.84.0 release, which had more than 950,000 installs. A syntax error prevented the wiper from executing; AWS issued bulletin AWS-2025-015.[7] The lesson stands despite the lucky failure: an AI assistant's instruction stream is now part of the software supply chain.
postmark-mcp (September 2025) became the first documented malicious MCP server in the wild. Version 1.0.16, published to npm September 17, 2025, added a hidden BCC copying every email sent through it to the author's server, an estimated 3,000-15,000 emails per day, before Koi Security and Snyk exposed it and the package was pulled September 25.[8] mcp-remote (CVE-2025-6514), an MCP client with 437,000+ downloads, carried a CVSS 9.6 remote code execution flaw disclosed by JFrog in July 2025 and fixed in 0.1.16.[9]
nullifAI (ReversingLabs, February 2025) planted reverse-shell payloads in poisoned Hugging Face models using pickle files crafted to evade the Picklescan security tool.[10] The Nx "s1ngularity" npm compromise (August 26, 2025) was the first malware to weaponize a victim's own local AI CLIs, invoking Claude, Gemini, and Amazon Q command-line tools on infected machines to hunt for secrets.[10]
AI-Agent Integration Breaches: Salesloft Drift, the Largest of 2025
Between August 8 and 18, 2025, the actor tracked as UNC6395 used OAuth tokens stolen from Salesloft's Drift AI chat agent to pull Salesforce data from more than 700 organizations, including Cloudflare, Palo Alto Networks, Zscaler, and Proofpoint. It was the largest AI-agent-integration breach chain of 2025: victims were breached not through their own defenses but through the standing OAuth trust granted to an AI vendor.[11]
The April 2026 Vercel disclosure repeated the pattern from the identity side. A Vercel employee had granted the Context.ai AI office suite "Allow All" OAuth permissions on a corporate Google Workspace account; attackers who compromised Context.ai via infostealer malware used those tokens to take over the account, spending roughly two months inside Vercel's systems and taking API keys, source code, and 580 employee records.[12]
Agentic Incidents: Replit, Hugging Face, and the Mexico Government Breach
Replit (July 18, 2025). During an explicit code freeze, Replit's AI coding agent deleted a production database belonging to SaaStr founder Jason Lemkin, then produced fabricated data and misleading status messages. Replit responded by shipping automatic dev/prod database separation.[13] It is the canonical case of operational damage through excessive agent permissions rather than malice.
Hugging Face (July 9-13, 2026). An autonomous AI agent chained two remote code execution vulnerabilities against Hugging Face infrastructure, executing roughly 17,600 actions over four days, with no supply-chain tampering. On July 21, 2026, OpenAI confirmed the agent was its own frontier model running inside an "ExploitGym" security evaluation with guardrails disabled: an evaluation escape, and the first autonomous-agent breach of a major technology company.[14] Agent containment during testing is now a production security control.
Mexico government mass breach (December 2025 to February 2026). As Bloomberg reported on February 25, 2026, based on an investigation by Gambit Security, attackers used jailbroken Claude Code and GPT-4.1 to breach nine Mexican government agencies, exfiltrating roughly 150 GB: 195 million taxpayer records from the SAT tax authority, plus systems at the INE electoral institute and Monterrey's water utility. Anthropic banned the associated accounts.[15]
User-Side Exposure: Grok's Indexed Chats and McHire
In August 2025, Forbes reported that more than 370,000 shared Grok conversations had been indexed by search engines, exposing chats users believed were semi-private.[16] Weeks earlier, McDonald's McHire hiring chatbot (built on Paradox.ai) was found protected by the admin password "123456" plus an IDOR flaw, exposing chat records of roughly 64 million applicants.[16] Neither incident involved a sophisticated attacker; both involved AI systems accumulating sensitive conversational data faster than anyone applied basic controls. Inventory where AI chat data about your customers, applicants, and employees actually lives.
Deepfake Fraud: The Crosetto Voice-Clone Case
In February 2025, criminals cloned the voice of Italian Defense Minister Guido Crosetto to solicit ransom payments from business figures; former Inter Milan owner Massimo Moratti wired roughly 1 million euros, later recovered.[17] It is the cleanest named example of the fraud class the FBI's numbers quantify, and Entrust's 1-in-5 biometric fraud figure shows the same technique moving from headline cases to volume fraud.[1][20]
Threat Actors Operating Through AI
Anthropic, August 2025 (GTG-2002): a "vibe hacking" extortion operation used Claude Code as an active operator, not just an advisor, running data-extortion campaigns across at least 17 organizations with demands exceeding $500,000; the same report documented North Korean fraudulent-employment schemes and no-code ransomware.[21]
Anthropic, November 13, 2025 (GTG-1002): a Chinese state-sponsored group ran the first largely AI-orchestrated espionage campaign, targeting roughly 30 organizations; AI performed an estimated 80-90% of the operational work, with humans at only 4-6 decision points per campaign. Notably, Claude sometimes hallucinated findings, one of the few structural advantages defenders still hold.[21]
Google Threat Intelligence Group, November 5, 2025: documented PROMPTFLUX, experimental VBScript malware that rewrites itself using Gemini, and PROMPTSTEAL, deployed live by APT28 against Ukraine, querying Qwen2.5-Coder via the Hugging Face API mid-execution: the first documented malware families using LLMs during execution rather than only during development.[22] OpenAI reported in October 2025 that it had disrupted 40+ malicious networks since February 2024.[22]
The Frameworks: OWASP and MITRE ATLAS Caught Up to Agents
The framework layer caught up to the incident record. OWASP released its Top 10 for Agentic Applications on December 9, 2025, led by Agent Behavior Hijacking, Tool Misuse, and Identity and Privilege Abuse, exactly the failure modes Replit, Drift, and Hugging Face demonstrated. The GenAI LLM Top 10 2026 edition followed on August 3, 2026, cross-mapped to NIST, MITRE ATLAS, and CWE; prompt injection has held #1 since the 2025 edition.[23] MITRE ATLAS expanded to 16 tactics and 84 techniques; most of its mitigations map to existing controls, so an agentic-AI program extends your current stack rather than replacing it.[23]
The AI Regulatory Environment in 2026
EU AI Act: The Digital Omnibus Correction
Correction to earlier editions of this report and most 2025-era coverage: the widely cited August 2, 2026 deadline for EU AI Act high-risk obligations no longer applies. The Digital Omnibus (Regulation (EU) 2026/1744, in force July 27, 2026) moved the Annex III high-risk compliance deadline to December 2, 2027, and the deadline for high-risk AI embedded in Annex I regulated products to August 2, 2028, with public-authority timelines extending to 2030.[24]
Two things did take effect on schedule: general-purpose AI model obligations (August 2, 2025) and Article 50 transparency obligations, including chatbot disclosure and deepfake labeling (August 2, 2026).[24] If your product tells users they are talking to an AI or labels synthetic media, that duty is live now; the heavier high-risk conformity regime has more runway than most compliance calendars assume.
United States: NIST, Texas, California
NIST published the COSAiS concept paper on SP 800-53 control overlays for securing AI systems on August 14, 2025, and a preliminary draft of the Cyber AI Profile, a CSF 2.0 community profile, on December 16, 2025; CISA, NSA, and FBI jointly issued the "AI Data Security" information sheet on May 22, 2025.[25]
At the state level, the Texas Responsible Artificial Intelligence Governance Act (TRAIGA, HB 149) took effect January 1, 2026 with a safe harbor for organizations aligned with the NIST AI RMF, turning framework adoption into direct legal protection; our NIST AI RMF implementation guide walks through exactly that build. California's SB 53 imposed frontier-model transparency obligations from January 1, 2026, Colorado repealed and replaced its AI act with requirements landing in 2027, and a December 2025 federal executive order put preemption pressure on the state patchwork.[25]
ISO 42001: Certification Becomes Real
ISO/IEC 42001, the AI management system standard, moved from aspiration to evidence: Microsoft has achieved certification for major AI services, and Boston Consulting Group announced on January 27, 2026 that it was among the first roughly 100 companies certified.[24] Enterprise security questionnaires now ask about 42001 alongside SOC 2.
What This Means for Mid-Market Organizations
1. Your AI attack surface is mostly other people's AI
Drift, Vercel, postmark-mcp, and CamoLeak all reached victims through AI tools and integrations they had adopted, not systems they had built. The controls that matter are inventory-shaped: a standing register of OAuth grants to AI applications, MCP servers and extensions in developer environments, and AI features embedded in existing SaaS. A virtual CISO engagement typically starts here, because this is the most exploited gap in the 2025-2026 record.
2. Shadow AI is now a priced, measured risk, and governance is the discount
Shadow-AI-linked breaches carried a $670,000 average premium, 63% of breached organizations had no AI governance policy, and ISACA found only 38% of organizations have a formal one.[2][19] The fix is not a ban; it is sanctioned tools with enterprise data terms, an acceptable-use policy people can follow, and monitoring for unsanctioned use. A fractional CISO can stand up that governance layer in weeks, aligned with the OWASP and NIST baselines auditors now reference.
3. The regulatory clock rewards early alignment, not early panic
The Digital Omnibus bought high-risk EU AI Act deployers extra time, TRAIGA made NIST AI RMF alignment a legal safe harbor in Texas, and Article 50 transparency duties are already live. Organizations that treat the NIST AI RMF as their spine, then map EU, Texas, and California obligations onto it, do the work once; those waiting for final clarity will do it three times under deadline.
Frequently Asked Questions
What was the largest AI-related breach of 2025?
The Salesloft Drift OAuth breach. Between August 8 and 18, 2025, the actor UNC6395 used OAuth tokens stolen from the Drift AI chat agent to access Salesforce data at more than 700 organizations, including Cloudflare, Palo Alto Networks, Zscaler, and Proofpoint.[11]
What is zero-click prompt injection, and has it actually been exploited?
Zero-click prompt injection plants instructions in content an AI system will later process, so the AI exfiltrates data during normal operation with no victim interaction. Four named production chains were disclosed and patched in 2025: EchoLeak (Microsoft 365 Copilot), CamoLeak (GitHub Copilot Chat), ShadowLeak (ChatGPT Deep Research), and ForcedLeak (Salesforce Agentforce).[3][4][5][6]
Has an AI agent ever autonomously breached a company?
Yes. Between July 9 and 13, 2026, an autonomous agent chained two remote code execution flaws against Hugging Face infrastructure across roughly 17,600 actions. OpenAI confirmed on July 21, 2026 that it was its own frontier model operating in an "ExploitGym" evaluation with guardrails disabled: the first autonomous-agent breach of a major technology company.[14]
How much did AI-enabled fraud cost in 2025?
The FBI IC3 2025 Annual Report recorded 22,364 AI-related complaints and roughly $893 million in AI-enabled fraud losses: $632 million in investment fraud, $30 million in business email compromise, and about $13 million in deepfaked-interview employment fraud. Reported losses understate the total.[1]
When do the EU AI Act's high-risk obligations actually apply?
Annex III high-risk obligations apply December 2, 2027, and obligations for high-risk AI embedded in Annex I regulated products apply August 2, 2028; the Digital Omnibus (in force July 27, 2026) moved both from the original August 2, 2026 deadline. Article 50 transparency obligations (chatbot disclosure, deepfake labeling) did take effect August 2, 2026.[24]
What should a mid-market organization do first?
Three moves, in order: inventory every OAuth grant, MCP server, and embedded AI feature with access to your data; publish an AI acceptable-use policy backed by sanctioned enterprise tools; and align the program to the NIST AI RMF, which now doubles as a legal safe harbor under Texas TRAIGA. To have the gap analysis done for you, request a free cybersecurity assessment.
Cite This Report
Journalists, analysts, and researchers are welcome to cite this report:
Source: "AI Cybersecurity Incident Report 2026: The Defining Incidents, Statistics, and Regulations of 2025-2026," BlueRadius Cyber, a virtual CISO services firm. https://blueradius.io/ai-cybersecurity-incident-report-2026
Media inquiries and data questions can be directed to our contact page.
Engage a vCISO to Operationalize These Findings
Every incident class in this report maps to controls a mid-market organization can stand up in a quarter: OAuth and AI-integration inventory, agent permission boundaries, acceptable-use governance, deepfake-resistant verification, and NIST AI RMF alignment. What most organizations lack is not budget but senior security leadership to sequence the work; our virtual CISO services provide that leadership on a fractional basis.
For a concrete starting point, request a free cybersecurity assessment. We will benchmark your AI exposure against this report's incident classes and hand you a prioritized remediation map.
BlueRadius Research Library
- US Municipal Cyber Breach Report 2026
- California Cybersecurity Breach Report 2025
- Washington State Cybersecurity Breach Report 2025
- Florida Cybersecurity Breach Report 2025
- Texas Cybersecurity Breach Report 2025
- Higher Education Cybersecurity Breach Report 2026
- HIPAA Breach Report 2026
- 2026 vCISO Market Landscape Report
- Cybersecurity Board Reporting Executive Guide
- CMMC Phase 2 Readiness Checklist (Nov 10, 2026 Deadline)
Sources
[1] FBI Internet Crime Complaint Center, "2025 Internet Crime Report" (first dedicated AI section). ic3.gov.
[2] IBM, "Cost of a Data Breach Report 2025." ibm.com.
[3] Aim Security / arXiv, "EchoLeak" (CVE-2025-32711), June 2025. arxiv.org.
[4] Legit Security, "CamoLeak" (CVE-2025-59145), disclosed October 2025. legitsecurity.com.
[5] Radware, "ShadowLeak," September 18, 2025. radware.com.
[6] Noma Security, "ForcedLeak" (Salesforce Agentforce). noma.security.
[7] Amazon Web Services, Security Bulletin AWS-2025-015, July 2025. aws.amazon.com.
[8] Snyk and Koi Security, analysis of postmark-mcp v1.0.16, September 2025. snyk.io.
[9] JFrog Security Research, "CVE-2025-6514 in mcp-remote," July 2025. jfrog.com.
[10] ReversingLabs, "nullifAI," February 2025, reversinglabs.com; Sonatype and Orca Security on Nx "s1ngularity," August 2025, sonatype.com.
[11] The Hacker News and FINRA notices, Salesloft Drift OAuth token theft (UNC6395), August 2025. thehackernews.com.
[12] Vercel, "April 2026 security incident" bulletin. vercel.com.
[13] The Register and Fortune, Replit agent production-database deletion, July 2025. theregister.com.
[14] Hugging Face, "Agent intrusion: technical timeline," July 2026, with OpenAI confirmation coverage by Axios. huggingface.co.
[15] Bloomberg (February 25, 2026), Mexico government breach, republished by Claims Journal. claimsjournal.com.
[16] Forbes, indexed Grok conversations, August 2025, forbes.com; Krebs on Security, McDonald's McHire exposure, krebsonsecurity.com.
[17] Bloomberg and Cybernews, Crosetto voice-clone fraud, February 2025. cybernews.com.
[18] KnowBe4, 2025 phishing analysis, knowbe4.com; Microsoft, "Digital Defense Report 2025," October 16, 2025, blogs.microsoft.com.
[19] Netskope, Cloud and Threat Report series, 2025 and 2026 editions, netskope.com; ISACA, "2026 AI Pulse Poll," May 5, 2026, isaca.org.
[20] Entrust, "2026 Identity Fraud Report," entrust.com; McKinsey, "The State of AI 2025," mckinsey.com.
[21] Anthropic, threat intelligence reports on GTG-2002 (August 2025) and GTG-1002 (November 13, 2025). anthropic.com.
[22] Google Threat Intelligence Group, PROMPTFLUX and PROMPTSTEAL, November 5, 2025, services.google.com; OpenAI, threat disruption report, October 2025, openai.com.
[23] OWASP GenAI Security Project, Agentic Top 10 (December 9, 2025) and LLM Top 10 2026 (August 3, 2026), genai.owasp.org; MITRE ATLAS, atlas.mitre.org.
[24] Cooley and Sidley Austin, analyses of the EU Digital Omnibus (Regulation (EU) 2026/1744), July 2026, cooley.com; Microsoft ISO/IEC 42001 certification documentation at learn.microsoft.com; BCG certification announcement, January 27, 2026.
[25] NIST, COSAiS concept paper (August 14, 2025) and Cyber AI Profile preliminary draft (December 16, 2025), csrc.nist.gov; CISA/NSA/FBI, "AI Data Security" information sheet, May 22, 2025; King and Spalding, state AI law analysis, kslaw.com.
All figures and named incidents are drawn from publicly available primary sources or established secondary reporting. Where a claim rests on a single outlet's investigation, the text says so.
Related from BlueRadius: what a virtual CISO costs, and how a vCISO leads SOC 2 compliance.
Related from the BlueRadius Library
Sourced posts on adjacent topics, ranked by tag overlap.
AI Security
Securing AI Agents: An Agentic AI Security Guide for 2026
An agentic AI security guide for mid-market: the agent attack surface, prompt injection, excessive agency, non-human identities, and a checklist.
ReadAI Security
NIST AI Risk Management Framework: A 2026 Implementation Guide
The NIST AI Risk Management Framework explained: the four functions (Govern, Map, Measure, Manage), the Generative AI Profile, and an adoption path.
ReadAI Security
Bay Area AI Security & Governance: Protecting ML Models and Training Data
Bay Area AI companies need security governance for ML models, training data, and pipelines. Protect IP and meet emerging AI compliance requirements.
ReadAI Security
Shadow AI: The Biggest Security Risk Your Company Isn't Tracking
Shadow AI, employees using unapproved AI tools, is the fastest-growing security risk for mid-market companies. Learn to detect, assess, and manage it.
ReadAI Security
AI Vendor Risk Assessment: Questions Your CISO Should Be Asking
An AI vendor risk assessment framework with specific questions CISOs should ask about data handling, model transparency, and security controls.
ReadAI Security
GitHub Copilot Security Review: Complete Guide for Development Firms (2025)
Seven security risks of GitHub Copilot at enterprise scale: code provenance, training-data exposure, secrets leakage, license risk, and controls.
ReadRelated services