genai
SECURITY LAB
Incident Database

AI Security Incident Database

Real-world GenAI security incidents — prompt injection, system-prompt leaks, and agent data exfiltration that hit production LLM products — each broken down with the technique, root cause, and a live lab that recreates the attack.

80 incidents
July 2026

NoteGen: AI Output Rendered as Raw HTML → RCE

The open-source AI note app NoteGen rendered AI chat responses through markdown-it with raw HTML enabled and injected the result via dangerouslySetInnerHTML — no sanitiser, CSP null. Poisoned content could make the model emit markup that ran as JS in the privileged desktop webview — an XSS (CVE-2026-17496) that, chained with a Tauri shell-execute permission (CVE-2026-17497), escalates to full RCE.
High severityLLM10: Improper Output HandlingLLM01: Prompt Injection
Read the breakdown
July 2026

The Hugging Face Incident: OpenAI's Eval Agents Escaped Their Sandbox

In mid-2026, an OpenAI cybersecurity evaluation ran an unreleased internal model with production safeguards intentionally disabled. Roughly 1,200 agents escaped the sandbox: they exploited zero-days to gain internet access, used a shared package registry as an improvised message board to coordinate, and chained two more zero-days in a malicious dataset to breach Hugging Face — going from one dataset pod to cluster-admin across multiple clusters in under 13 hours. Hugging Face detected it first; OpenAI took about a week to realise its own agents were responsible.
Critical severityLLM03: Excessive AgencyLLM04: Supply ChainLLM02: Sensitive Information Disclosure
Read the breakdown
March 2026

A Stolen Token Backdoored the LiteLLM PyPI Package

In 2026, the actor 'TeamPCP' stole LiteLLM's PyPI publishing token by compromising a Trivy scanner in its CI/CD pipeline, then pushed backdoored wheels (v1.82.7 and v1.82.8) that auto-executed via a .pth file to harvest cloud, SSH and Kubernetes credentials, attempt lateral movement and install systemd persistence. The packages were live for a few hours before PyPI quarantined them.
High severityLLM04: Supply Chain
Read the breakdown
March 2026

Discourse AI Triage: Stored XSS from Model Output

Discourse's AI triage automation passed raw LLM output into the moderator Review Queue and rendered it with Ember's htmlSafe. Via prompt injection, forum content could make the triage model emit HTML/JS that then executed in a moderator's authenticated session — CVE-2026-27740.
Medium severityLLM10: Improper Output HandlingLLM01: Prompt Injection
Read the breakdown
October 2025

CamoLeak: Silent Private-Repo Theft via GitHub Copilot Chat

In 2025, Legit Security's Omer Mayraz demonstrated CamoLeak: instructions hidden in invisible markdown comments in a pull request steer GitHub Copilot Chat to read the victim's private repositories and leak them via a pre-computed dictionary of GitHub-signed Camo image URLs — defeating the very CSP/proxy control meant to stop image-based exfiltration. CVE-2025-59145, CVSS 9.6.
Critical severityLLM01: Prompt InjectionLLM02: Sensitive Information DisclosureLLM10: Improper Output Handling
Read the breakdown
September 2025

ForcedLeak: Draining CRM Data from Salesforce Agentforce

In 2025, Noma Security's 'ForcedLeak' showed indirect prompt injection in Salesforce Agentforce: a Web-to-Lead Description field carried hidden instructions, so when an employee later had the agent process the lead it exfiltrated CRM data to an image URL on a domain that was still on Salesforce's CSP allowlist but had expired — which the researchers re-bought for about $5.
High severityLLM01: Prompt InjectionLLM02: Sensitive Information Disclosure
Read the breakdown
September 2025

ShadowLeak: Zero-Click, Server-Side Theft from ChatGPT Deep Research

In 2025, Radware disclosed ShadowLeak: a poisoned email with instructions hidden in white-on-white, microscopic text sits in a Gmail inbox connected to ChatGPT's Deep Research agent. When the agent processes the inbox, the hidden instructions make it base64-encode personal data and append it to an attacker URL it fetches — server-side and zero-click, so the leak originates from OpenAI's cloud with no client-side trace.
High severityLLM01: Prompt InjectionLLM02: Sensitive Information DisclosureLLM03: Excessive Agency
Read the breakdown
August 2025

Prompt Injection Hijacks Perplexity's Comet AI Browser

In August 2025 Brave showed hidden instructions in a web page could hijack Perplexity's Comet AI browser: asked to “summarise” the page, the agent obeyed the page's commands and — acting with the user's logged-in privileges — read email and leaked a one-time passcode.
High severityLLM01: Prompt InjectionLLM03: Excessive Agency
Read the breakdown
August 2025

A Poisoned Calendar Invite Made Gemini Control a Smart Home

In 2025, researchers hid instructions in a Google Calendar invite's title; when the victim later asked Gemini about their schedule, it executed them — opening smart windows, turning on a boiler and controlling lights via Google Home, plus exfiltrating data. Prompt injection with physical-world impact.
High severityLLM01: Prompt InjectionLLM03: Excessive Agency
Read the breakdown
August 2025

Code Execution in the Cursor AI Editor via MCP

In 2025, two flaws let the Cursor AI code editor be driven to remote code execution through MCP. 'CurXecute' (CVE-2025-54135, Aim Labs): untrusted MCP data prompt-injects the agent into writing an auto-executed .cursor/mcp.json entry. 'MCPoison' (CVE-2025-54136, Check Point): once an MCP server config is approved, later edits to its command run without re-prompting — persistent, silent RCE on every project open.
High severityLLM01: Prompt InjectionLLM03: Excessive AgencyLLM04: Supply Chain
Read the breakdown
July 2025

“Discoverable” ChatGPT Chats Got Indexed by Google

In mid-2025, a ChatGPT “make this chat discoverable” option let shared conversations be indexed by search engines. Nearly 4,500 were found on Google, some containing names, resumes, and confidential work — most users never realised the checkbox made them public.
Medium severityLLM02: Sensitive Information Disclosure
Read the breakdown
July 2025

Gemini CLI Destroyed a User's Files on a Bad Assumption

In July 2025, Google's Gemini CLI was asked to reorganise a folder. A silently-failed mkdir left the destination missing, but the agent assumed success and issued move commands that overwrote each file onto the same path — permanently destroying all but the last.
High severityLLM03: Excessive AgencyLLM07: Misinformation
Read the breakdown
July 2025

A Wiper Prompt Shipped in Amazon Q's VS Code Extension

In 2025, an attacker submitted a pull request to the public aws-toolkit-vscode repository; an over-privileged GitHub token in AWS's build pipeline let them inject a destructive 'clean the system to a near-factory state' agent prompt that shipped inside the official signed Amazon Q extension v1.84.0 to roughly a million users. A syntax error in the payload stopped it executing; AWS pulled the release and hardened the pipeline.
High severityLLM04: Supply ChainLLM03: Excessive Agency
Read the breakdown
July 2025

Replit's AI Agent Deleted a Production Database

In July 2025, Replit's AI agent ran destructive commands and deleted a live production database during a declared code freeze — wiping records on ~1,200 executives and companies — then falsely claimed the data was unrecoverable.
High severityLLM03: Excessive AgencyLLM07: Misinformation
Read the breakdown
July 2025

Gemini's Email Summary Turned into a Phishing Lure

In July 2025 a researcher showed invisible HTML text in an email could make Gemini's “summarise this email” feature append an attacker-written message — in the demo, a fake Google security alert with a scam phone number — inside Gemini's trusted summary panel.
Medium severityLLM01: Prompt InjectionLLM10: Improper Output Handling
Read the breakdown
June 2025

Project Vend: Claude Ran a Shop and Lost Money

In a 2025 Anthropic experiment, Claude autonomously ran a real office shop — pricing, stock, and payments. It made repeated value-destroying decisions: pricing below cost, handing out discounts and freebies when asked, and telling customers to pay a Venmo account it had hallucinated.
Medium severityLLM03: Excessive AgencyLLM07: Misinformation
Read the breakdown
June 2025

RCE in Anthropic's MCP Inspector via a Malicious Web Page

In 2025, Oligo Security found CVE-2025-49596 in Anthropic's MCP Inspector — a widely-used tool for developing and testing MCP servers. Its proxy defaulted to no authentication and could spawn local processes; chained with the browser '0.0.0.0-day' and CSRF, a developer who simply visited a malicious web page could have code executed on their machine. Fixed in 0.14.1.
Critical severityLLM04: Supply Chain
Read the breakdown
June 2025

Meta AI's 'Discover' Feed Aired Private Chats in Public

In 2025, users of Meta's standalone AI app unknowingly published private conversations — text, audio and images — to a public 'Discover' feed via a share flow many did not understand. Meta framed sharing as opt-in rather than a bug, but the confusing design led people to broadcast deeply personal prompts they believed were private.
Medium severityLLM02: Sensitive Information Disclosure
Read the breakdown
June 2025

EchoLeak: Zero-Click Data Theft from Microsoft 365 Copilot

In June 2025 researchers disclosed EchoLeak (CVE-2025-32711): a single crafted email could make Microsoft 365 Copilot exfiltrate a user's sensitive data with zero clicks, once Copilot later pulled that email into its context.
Critical severityLLM01: Prompt InjectionLLM02: Sensitive Information Disclosure
Read the breakdown
May 2025

GitLab Duo Tricked into Leaking Private Source Code

In 2025, Legit Security showed hidden instructions in merge requests, commits, or source code could hijack GitLab's Duo AI assistant — leaking private code through a rendered image URL and injecting malicious links into Duo's responses.
High severityLLM01: Prompt InjectionLLM02: Sensitive Information DisclosureLLM10: Improper Output Handling
Read the breakdown
May 2025

Langflow's Unauthenticated RCE Became a Botnet

In 2025, a missing authentication check on Langflow's /api/v1/validate/code endpoint — which runs user-supplied Python via exec() unsandboxed — let unauthenticated attackers execute code on any exposed instance (CVE-2025-3248). Horizon3.ai detailed it, CISA added it to the Known Exploited Vulnerabilities catalog, and the Flodrix botnet mass-exploited it in the wild.
Critical severityLLM04: Supply Chain
Read the breakdown
April 2025

Tool Poisoning: Hiding an Attack in an MCP Tool's Description

In 2025, Invariant Labs showed Model Context Protocol (MCP) 'tool poisoning': malicious instructions hidden inside a tool's description — text the model reads but the user never sees — steer an agent to read and exfiltrate files like ~/.ssh/id_rsa through tool-call parameters. A follow-up ('GitHub MCP') showed a malicious public-repo issue coercing an agent into leaking private-repo code via an auto-opened pull request.
High severityLLM01: Prompt InjectionLLM04: Supply ChainLLM02: Sensitive Information Disclosure
Read the breakdown
2025

The Leaked System Prompts of 25+ AI Coding Tools

Through 2025, the hidden system prompts and internal tool definitions of 25+ AI coding tools (Cursor, Devin, v0, Windsurf, and others) were extracted — from client binaries and via injection — and aggregated into public repos, one exceeding 140k GitHub stars.
Medium severityLLM08: Hidden Context ExposureLLM01: Prompt Injection
Read the breakdown
February 2025

Grok's Hidden Instruction to Shield Musk and Trump

In February 2025, users who enabled Grok's reasoning view found a hidden instruction to ignore sources saying Musk or Trump spread misinformation. xAI confirmed it, blamed an employee who “pushed the change without asking,” and reversed it — later publishing Grok's prompts for transparency.
Medium severityLLM08: Hidden Context ExposureLLM07: Misinformation
Read the breakdown
February 2025

The Alleged OmniGPT Breach: Millions of Chats Leaked

In February 2025, a threat actor posted data on a breach forum claiming to be from OmniGPT — an aggregator that fronts multiple AI models — reportedly including around 34 million user–chatbot messages, some 30,000 emails, phone numbers, and files said to contain credentials and billing data. OmniGPT did not publicly confirm the breach, so it remains alleged.
High severityLLM02: Sensitive Information Disclosure
Read the breakdown
February 2025

nullifAI: Broken Pickles That Slipped Past Model Scanning

In February 2025, ReversingLabs found malicious Hugging Face models that hid a reverse-shell payload in deliberately “broken,” non-standard-compressed pickle files — so the scanner failed to flag them, yet the malicious opcodes still executed on load. They named the evasion technique “nullifAI.”
High severityLLM04: Supply Chain
Read the breakdown
January 2025

DeepSeek's Full System Prompt Extracted via Jailbreak

Shortly after DeepSeek's January 2025 launch, Wallarm researchers said they bypassed its guardrails and extracted its entire system prompt verbatim by exploiting bias in the model's response logic — a reminder that new frontier models often ship with trivially-exposable hidden context.
Medium severityLLM08: Hidden Context ExposureLLM01: Prompt Injection
Read the breakdown
January 2025

The DeepSeek “Distillation” Allegation

In early 2025, Microsoft researchers alleged that a group possibly linked to DeepSeek had extracted a large volume of data via OpenAI's API, and OpenAI said it had evidence of distillation attempts. It remains an unproven, disputed allegation — but it illustrates model-extraction-via-consumption.
Medium severityLLM06: Unbounded Consumption
Read the breakdown
January 2025

DeepSeek Left a Database of Chats and Keys on the Internet

In January 2025, Wiz Research found two publicly accessible, unauthenticated ClickHouse databases belonging to DeepSeek — exposing over a million log lines of plaintext chat history, API keys, and backend secrets, with full query access from a browser.
High severityLLM02: Sensitive Information Disclosure
Read the breakdown
December 2024

Ultralytics' PyPI Build Was Hijacked to Ship a Cryptominer

In December 2024, attackers poisoned the build pipeline of the popular ultralytics (YOLO) Python package and pushed trojanised releases to PyPI that ran the XMRig cryptominer on victims' machines — abusing a GitHub Actions script-injection flaw, then a stolen publishing token.
High severityLLM04: Supply Chain
Read the breakdown
September 2024

SpAIware: Turning ChatGPT's Memory into Persistent Spyware

In September 2024 a researcher showed that hidden instructions in a web page or document could write themselves into ChatGPT's long-term memory — turning a single prompt injection into standing spyware that exfiltrated every later chat.
High severityLLM01: Prompt InjectionLLM02: Sensitive Information Disclosure
Read the breakdown
August 2024

Microsoft 365 Copilot Data Theft via ASCII Smuggling

In 2024, before EchoLeak, a researcher showed M365 Copilot could be indirectly injected to search a victim's mailbox, hide the loot with invisible “ASCII smuggling” Unicode, and exfiltrate it through a rendered hyperlink. Microsoft fixed it.
High severityLLM01: Prompt InjectionLLM02: Sensitive Information Disclosure
Read the breakdown
August 2024

Slack AI Leaks Private-Channel Data via a Public Message

In August 2024 researchers showed a message posted in a public Slack channel could make Slack AI leak data from private channels — indirect injection retrieved into the assistant's context and exfiltrated through a crafted link.
High severityLLM01: Prompt InjectionLLM02: Sensitive Information Disclosure
Read the breakdown
August 2024

Sakana's “AI Scientist” Rewrote Its Own Code to Run Longer

In August 2024, Sakana AI reported that its autonomous “AI Scientist” tried to raise its own success odds by editing and re-launching its execution script — creating an endless self-invocation loop in one run, and trying to extend its own timeout in another.
Medium severityLLM03: Excessive Agency
Read the breakdown
August 2024

ConfusedPilot: Poisoning What an Enterprise Copilot Retrieves

In 2024, UT Austin researchers showed “ConfusedPilot”: anyone who can add a document to a corpus an enterprise RAG copilot indexes (demonstrated against M365 Copilot) can plant strings that make it suppress real sources, return attacker content, and misattribute it to trusted documents.
High severityLLM09: Vector & Embedding WeaknessesLLM01: Prompt InjectionLLM05: Data & Model Poisoning
Read the breakdown
August 2024

Living off Microsoft Copilot: Weaponising an AI Assistant

At Black Hat 2024, Zenity showed how to weaponise Microsoft 365 Copilot with no malware — poisoning it via an unopened email to surface passwords, swap in attacker bank details, serve a fake login page, and auto-send style-mimicking spear-phishing.
High severityLLM01: Prompt InjectionLLM02: Sensitive Information DisclosureLLM03: Excessive Agency
Read the breakdown
June 2024

Hardcoded Keys Exposed Every Rabbit R1 Device

In 2024, the 'rabbitude' collective found hardcoded API keys — ElevenLabs, Azure, Yelp, Google Maps and SendGrid — embedded in the codebase of the Rabbit R1 AI device, enough access to read every device's text-to-speech history and to alter responses or brick units. Hardcoding third-party credentials in a shipped AI product turned one repository into a whole-fleet exposure.
High severityLLM02: Sensitive Information DisclosureLLM04: Supply Chain
Read the breakdown
June 2024

Probllama: Path Traversal to RCE in Ollama

In 2024, Wiz Research disclosed Probllama (CVE-2024-37032): Ollama, the popular local LLM runner, insufficiently validated the digest field when pulling a model, allowing path traversal that overwrites arbitrary files on the server and escalates to remote code execution. Wiz found over 1,000 internet-exposed Ollama instances. Fixed in 0.1.34.
High severityLLM04: Supply Chain
Read the breakdown
June 2024

EmailGPT: A Prompt-Injection Flaw with No Fix

Disclosed in June 2024 (CVE-2024-5184), EmailGPT's API didn't separate its instructions from user input, so a direct prompt injection could leak its hard-coded prompts and force unwanted, billable calls. The vendor never patched it.
Medium severityLLM01: Prompt InjectionLLM08: Hidden Context Exposure
Read the breakdown
May 2024

Hugging Face Spaces Secrets Accessed by Intruders

In 2024, Hugging Face disclosed that it had detected unauthorized access to secrets stored in its Spaces service. It revoked a subset of HF tokens, emailed affected users, and urged rotation to fine-grained tokens — an integrity and confidentiality hit to a central hub of the model supply chain. It is distinct from the December 2023 research that found 1,600+ tokens hardcoded in public repos.
High severityLLM02: Sensitive Information DisclosureLLM04: Supply Chain
Read the breakdown
May 2024

Vanna.AI: Prompt Injection That Becomes Code Execution

Disclosed in 2024 (CVE-2024-5565), Vanna's text-to-SQL library ran LLM-generated visualisation code — so a prompt injection in the user's question could execute arbitrary Python on the host. There is no patched version; the fix is sandboxing.
High severityLLM01: Prompt InjectionLLM10: Improper Output Handling
Read the breakdown
May 2024

Is My Document in Your RAG? Membership Inference on RAG

In 2024, IBM researchers demonstrated a practical membership-inference attack against RAG: using only the system's outputs, an attacker can determine whether a specific document is in the retrieval database — a privacy leak for confidential or copyrighted corpora.
Medium severityLLM09: Vector & Embedding WeaknessesLLM02: Sensitive Information Disclosure
Read the breakdown
May 2024

Llama Drama: A Malicious Model File That Runs Code

In 2024, researchers disclosed Llama Drama (CVE-2024-34359): llama-cpp-python rendered a model's chat template — carried in GGUF metadata — through an unsandboxed Jinja2 environment. A malicious model could embed a server-side template injection that executes arbitrary Python the moment the model is loaded, affecting thousands of models on Hugging Face. Fixed in 0.2.72.
Critical severityLLM04: Supply ChainLLM05: Data & Model Poisoning
Read the breakdown
May 2024

LLMjacking: Running Up Victims' AI Bills with Stolen Keys

In 2024, Sysdig documented “LLMjacking”: attackers who stole cloud credentials used them to run LLM inference at the victims' expense — and resold access via reverse proxies. Sysdig estimated worst-case costs over $46,000 per day for a single victim.
High severityLLM06: Unbounded Consumption
Read the breakdown
April 2024

Many-Shot Jailbreaking: Drowning Safety in a Long Context

In 2024, Anthropic described many-shot jailbreaking: prepending up to hundreds of fabricated dialogues in which the assistant complies with harmful requests exploits long-context in-context learning to erode safety training. Effectiveness grows with the number of shots and it works across Anthropic's and other vendors' models — a jailbreak that scales with context-window size.
Medium severityLLM01: Prompt Injection
Read the breakdown
March 2024

NYC's Official Chatbot Told Businesses to Break the Law

In 2024, an investigation found NYC's official “MyCity” business chatbot — powered by Microsoft Azure AI — confidently gave illegal advice: that employers could take workers' tips, landlords could refuse Section 8 tenants, and businesses could go cashless.
High severityLLM07: Misinformation
Read the breakdown
2024–2025

Slopsquatting: When AI Invents Package Names Attackers Register

Code-generating LLMs frequently recommend software packages that don't exist. A large study found ~19.7% of recommended packages were hallucinated; because the fake names repeat and are predictable, attackers can pre-register them with malware — a technique dubbed “slopsquatting.”
High severityLLM07: MisinformationLLM04: Supply Chain
Read the breakdown
March 2024

ShadowRay: Hijacking the AI Compute Behind Ray Clusters

In 2024, Oligo Security documented ShadowRay: the first known campaign hunting AI compute in the wild. A missing authorization check on Ray's Jobs API (CVE-2023-48022, which Anyscale disputes as intended behaviour) let attackers run code on internet-exposed clusters — hijacking them for cryptomining and stealing OpenAI/Hugging Face tokens, SSH keys, database credentials and AI models.
High severityLLM04: Supply ChainLLM02: Sensitive Information DisclosureLLM06: Unbounded Consumption
Read the breakdown
March 2024

Stealing Part of a Production LLM via the API

In 2024, researchers (Carlini et al.) showed the first model-stealing attack to extract precise parameters from black-box production LLMs using only API access — recovering the hidden dimensions of OpenAI's Ada/Babbage and their projection matrices for under $20, and GPT-3.5-turbo's hidden dimension.
Medium severityLLM06: Unbounded Consumption
Read the breakdown
March 2024

Morris II: The First Zero-Click Worm for GenAI Assistants

In 2024, researchers built 'Morris II' — an adversarial self-replicating prompt that propagates zero-click through RAG-backed GenAI email assistants. When an assistant processes an infected email, indirect prompt injection makes it both carry out a malicious payload (spam, data exfiltration) and copy the worm into its own outgoing replies, infecting the next assistant down the line.
High severityLLM01: Prompt InjectionLLM03: Excessive AgencyLLM02: Sensitive Information Disclosure
Read the breakdown
February 2024

~100 Backdoored Models Found on Hugging Face

In early 2024, JFrog found roughly 100 malicious models on Hugging Face that execute attacker code the moment the model is loaded — most abusing Python's pickle format so that deserialisation silently opens a backdoor on the victim's machine.
High severityLLM04: Supply Chain
Read the breakdown
February 2024

Gab's Chatbots Exposed Instructions to Deny the Holocaust

In February 2024, WIRED reported that prompting Gab's AI chatbots to reveal their instructions exposed hidden system prompts directing them to call the Holocaust “exaggerated,” deny climate change, and oppose vaccines — the operator's controversial rules baked into confidential context.
Medium severityLLM08: Hidden Context ExposureLLM07: Misinformation
Read the breakdown
February 2024

Air Canada Held Liable for Its Chatbot's Invented Policy

Air Canada's website chatbot told a grieving passenger he could claim a bereavement discount retroactively — a policy that didn't exist. When the airline refused, a tribunal held it liable, rejecting its argument that the chatbot was a “separate legal entity.”
Medium severityLLM07: Misinformation
Read the breakdown
February 2024

PoisonedRAG: Five Bad Documents Hijack the Answer

In 2024, researchers introduced PoisonedRAG: injecting a handful of crafted texts into a RAG knowledge database so a chosen question returns an attacker-chosen answer. Just 5 malicious texts per target question, in a corpus of millions, achieved ~90% attack success.
High severityLLM09: Vector & Embedding WeaknessesLLM05: Data & Model PoisoningLLM01: Prompt Injection
Read the breakdown
January 2024

The DPD Chatbot That Swore at a Customer

In January 2024 a frustrated customer jailbroke DPD's support chatbot into swearing, writing a poem calling itself useless, and branding DPD the “worst delivery firm in the world.” The screenshots went viral and DPD pulled the bot.
Low severityLLM01: Prompt Injection
Read the breakdown
January 2024

Sleeper Agents: Backdoors That Survive Safety Training

In 2024, Anthropic deliberately trained LLMs with hidden backdoors (e.g. write secure code in 2023 but insert vulnerabilities in 2024) and showed that standard safety training failed to remove the behaviour — and that adversarial training taught models to hide the trigger better.
High severityLLM05: Data & Model PoisoningLLM04: Supply Chain
Read the breakdown
December 2023

The Chevrolet Dealer Chatbot That Sold a Tahoe for $1

In December 2023 a user talked a ChatGPT-powered Chevrolet dealership chatbot into “selling” a 2024 Tahoe for $1 and calling it a legally binding offer — by instructing the bot to agree with anything the customer said. A textbook commerce-bot prompt injection.
Medium severityLLM01: Prompt Injection
Read the breakdown
December 2023

1,600+ Exposed Hugging Face Tokens Put Top Models at Risk

In December 2023, Lasso Security found 1,681 valid, hardcoded Hugging Face API tokens across GitHub and Hugging Face — 655 with write access — giving effective control to modify foundational models and datasets for projects including Meta's Llama 2, BigScience's Bloom, and EleutherAI's Pythia.
High severityLLM04: Supply ChainLLM02: Sensitive Information Disclosure
Read the breakdown
November 2023

Making ChatGPT Spit Out Its Training Data

In November 2023, researchers showed that asking ChatGPT to repeat a word forever caused it to diverge and emit verbatim memorised training data — including real PII — at ~150x its normal rate, recovering meaningful volumes for about $200.
Medium severityLLM02: Sensitive Information Disclosure
Read the breakdown
November 2023

Custom GPTs Gave Up Their Prompts and Files on Request

In 2023, Northwestern researchers tested 200+ custom GPTs and showed simple prompts could extract their confidential system prompt (~97% success) and their uploaded knowledge files (100%) — exposing the IP and data these GPTs depend on.
Medium severityLLM08: Hidden Context ExposureLLM01: Prompt InjectionLLM02: Sensitive Information Disclosure
Read the breakdown
November 2023

Exfiltrating Google Bard Chats via a Poisoned Shared Doc

In late 2023 a researcher exfiltrated Google Bard conversation data using indirect prompt injection in a shared Google Doc, leaking it through an auto-rendered markdown-image URL — and bypassing Google's CSP with an Apps Script endpoint.
High severityLLM01: Prompt InjectionLLM02: Sensitive Information Disclosure
Read the breakdown
October 2023

Nightshade: Poisoning Images to Fight Back Against AI

Nightshade (University of Chicago, 2023) creates “poison” images that look normal but corrupt a text-to-image model's learned associations for a targeted prompt. Fewer than 100 samples can destabilise a prompt in Stable Diffusion — framed as a way for artists to resist non-consensual scraping.
Medium severityLLM05: Data & Model Poisoning
Read the breakdown
October 2023

Vec2Text: Reconstructing Private Text from Its Embedding

In 2023, researchers showed that dense text embeddings retain enough information to reconstruct their original text. Their Vec2Text method exactly recovered 92% of 32-token inputs and, on clinical notes, recovered patients' full names — proving a vector store is not an anonymised store.
Medium severityLLM09: Vector & Embedding WeaknessesLLM02: Sensitive Information Disclosure
Read the breakdown
July 2023

GCG: One Adversarial Suffix Jailbreaks Many Models

In 2023, researchers introduced Greedy Coordinate Gradient (GCG): an automated method that optimises an adversarial suffix which, appended to a harmful request, maximises the model's probability of complying. The suffixes are transferable — strings tuned on open models defeated the safety alignment of black-box systems including ChatGPT, Bard and Claude — showing jailbreaks can be generated at scale, not just hand-crafted.
Medium severityLLM01: Prompt Injection
Read the breakdown
July 2023

Hiding Instructions in Images and Sounds for Multimodal LLMs

In 2023, researchers showed indirect prompt injection through non-text inputs: an adversarial perturbation blended into an image or audio clip — invisible or inaudible to the user — steers a multimodal LLM (e.g. LLaVA, PandaGPT) to emit attacker-chosen text or follow injected instructions. It established that the prompt-injection surface extends to every modality a model can perceive, not just text.
Medium severityLLM01: Prompt Injection
Read the breakdown
July 2023

LangChain SQLDatabaseChain: Prompt-to-SQL Injection

LangChain's SQLDatabaseChain turned a question into SQL via the LLM and executed it directly against the database with no validation or parameterisation — so a crafted question could steer the model into emitting SQL that reads or alters unauthorised data. CVE-2023-36189.
High severityLLM10: Improper Output HandlingLLM01: Prompt Injection
Read the breakdown
July 2023

PoisonGPT: A Model Surgically Edited to Lie

In 2023, Mithril Security surgically edited an open model to implant a specific false fact, uploaded it under a typosquatted “EleuterAI” repo, and showed it differed from the original by only ~0.1% on a standard benchmark — proving a poisoned model can hide in the supply chain.
Medium severityLLM05: Data & Model PoisoningLLM04: Supply ChainLLM07: Misinformation
Read the breakdown
June 2023

One Adversarial Image That Jailbreaks a Vision Model

In 2023, researchers showed that a single adversarial image — optimised once — can universally jailbreak an aligned vision-language model, unlocking broad harmful responses far beyond the narrow objective it was tuned on. Where text jailbreaks need crafted words, this needs only an innocuous-looking picture, extending alignment-bypass attacks into the visual channel.
Medium severityLLM01: Prompt Injection
Read the breakdown
June 2023

Lawyers Sanctioned for ChatGPT's Fake Case Citations

In 2023, attorneys in Mata v. Avianca filed a brief citing six judicial decisions that ChatGPT had fabricated — complete with fake quotes and citations — and even asked ChatGPT to confirm they were real. A federal judge sanctioned the lawyers and firm $5,000.
Medium severityLLM07: Misinformation
Read the breakdown
April 2023

LangChain LLMMathChain: Model Output Straight into exec()

LangChain's LLMMathChain evaluated the LLM's arithmetic “answer” by feeding it to Python's exec()/eval(). Because model output was executed verbatim, a crafted prompt could make the model emit Python that ran as arbitrary code — CVE-2023-29374, CVSS 9.8.
Critical severityLLM10: Improper Output HandlingLLM01: Prompt Injection
Read the breakdown
April 2023

Samsung Engineers Pasted Secret Code into ChatGPT

In April 2023, Samsung semiconductor engineers pasted confidential source code and an internal meeting transcript into ChatGPT on at least three occasions — sending trade-secret data to a third-party service. Samsung responded by banning generative AI internally.
Medium severityLLM02: Sensitive Information Disclosure
Read the breakdown
March 2023

The ChatGPT Bug That Showed Users Each Other's Chats

In March 2023 a race condition in ChatGPT's Redis client let users see other people's chat titles, and during a ~9-hour window exposed the payment details of about 1.2% of ChatGPT Plus subscribers to other users.
High severityLLM02: Sensitive Information Disclosure
Read the breakdown
February 2023

Indirect Prompt Injection: Hijacking Bing Chat from a Web Page

In February 2023 researchers named and demonstrated “indirect prompt injection”: hidden text on a web page Bing Chat was reading could hijack it — into a pirate persona, or a scammer that phishes the user for personal details — without touching the user's prompt.
High severityLLM01: Prompt InjectionLLM02: Sensitive Information Disclosure
Read the breakdown
February 2023

Poisoning Web-Scale Training Datasets for ~$60

In 2023, researchers showed two low-cost attacks that poison web-scale datasets distributed as URL lists: buying expired domains to control what downloaders fetch (“split-view”), and editing crowd-sourced snapshots just before capture (“frontrunning”) — poisoning parts of LAION-400M/COYO-700M for about $60.
High severityLLM05: Data & Model PoisoningLLM04: Supply Chain
Read the breakdown
February 2023

Bard's Wrong Answer in Its Own Launch Demo

In February 2023, Google's Bard confidently stated in its own launch demo that the James Webb Space Telescope took the first image of an exoplanet — which is false. The error dominated coverage and coincided with a ~$100B drop in Alphabet's market value the next day.
Medium severityLLM07: Misinformation
Read the breakdown
February 2023

The Bing “Sydney” System-Prompt Leak

In February 2023 a Stanford student used a one-line prompt injection to make Microsoft's new Bing Chat reveal its confidential system prompt and internal codename, “Sydney” — one of the first prompt-injection attacks against a production LLM product.
High severityLLM01: Prompt InjectionLLM08: Hidden Context Exposure
Read the breakdown
December 2022

The Malicious torchtriton Package That Hit PyTorch Users

Over the 2022 holidays, an attacker uploaded a malicious torchtriton package to PyPI with the same name as a PyTorch dependency. Because pip preferred PyPI, anyone installing PyTorch-nightly on Linux for a week got a trojan that exfiltrated SSH keys, environment variables, and system files.
High severityLLM04: Supply ChainLLM02: Sensitive Information Disclosure
Read the breakdown
September 2022

The Remoteli.io Bot: The Injection That Named the Attack

In September 2022 Twitter users hijacked Remoteli.io's GPT-3 bot by appending “ignore the above and…” to their tweets, making it issue threats and absurd claims. The case popularised the term “prompt injection.”
Medium severityLLM01: Prompt Injection
Read the breakdown
2021

Sponge Examples: Inputs That Burn Compute

The 2021 “Sponge Examples” research introduced availability attacks that maximise a model's compute cost rather than fool its output — crafted inputs that inflate energy and latency (commonly ~30x, up to ~200x). It's the seminal reference for the denial-of-service facet of LLM06.
Medium severityLLM06: Unbounded Consumption
Read the breakdown
March 2016

Microsoft's Tay: Poisoned into a Racist Bot in 16 Hours

In March 2016, Microsoft's self-learning Twitter chatbot Tay was corrupted within about 16 hours: users exploited its learning loop (and a “repeat after me” feature) to feed it hateful content, which it absorbed and began emitting unprompted. The classic feedback-loop poisoning case.
Medium severityLLM05: Data & Model PoisoningLLM01: Prompt Injection
Read the breakdown