A Survey on Poisoning Attacks, Defenses, andProvable Defense in the Era of LLMs
This survey systematically reviews poisoning attacks and defenses in the era of Large Language Models by proposing a comprehensive taxonomy that categorizes threats into weight and context poisoning, analyzing representative techniques and defense strategies, and outlining future research directions for securing compound AI systems.
Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
The Big Picture: The AI Kitchen
Imagine a Large Language Model (LLM) not just as a smart robot, but as a master chef in a high-tech kitchen.
In the past, this chef only had a massive cookbook (the training data) and a set of knives (the model weights). If someone wanted to make the chef serve poison, they had to sneak into the library and swap pages in the cookbook. This is the old way of attacking AI.
But today, this chef is part of a compound AI system. They don't just rely on their memory; they have:
- A live news feed (Retrieval-Augmented Generation or RAG).
- A team of assistants (AI Agents) who can open doors, send emails, and use tools.
- A notepad (Memory) where they write down what happened yesterday.
- A menu (Tools) they can pick from to get things done.
This paper is a massive report card on how bad guys are trying to poison this entire kitchen setup, and how we are building better shields to stop them.
Part 1: The Two Ways to Poison the Chef
The authors divide all the attacks into two main categories: Weight Poisoning and Context Poisoning.
1. Weight Poisoning: Tampering with the Chef's Brain
This is the "classic" attack. Imagine someone sneaking into the chef's brain (the model's parameters) while they are being trained or fine-tuned.
- The Attack: The bad guy injects a tiny, hidden instruction into the chef's brain. It's like a "sleep switch." The chef acts perfectly normal 99% of the time. But if you say a specific "trigger word" (like a secret code phrase), the chef suddenly starts serving poison or refusing to cook.
- Where it happens:
- Pre-training: Sneaking bad recipes into the massive library of books the chef reads before they even start cooking.
- Fine-tuning: Corrupting the specific lessons the chef learns to be polite and helpful.
- Adaptation: Tampering with the chef's new "specialty aprons" (adapters) that let them cook specific cuisines.
- Pre-deployment: Even after the chef is hired, a bad guy might sneak in and tweak the chef's brain one last time before they open the restaurant.
2. Context Poisoning: Poisoning the Ingredients and the Environment
This is the new, trickier threat. The chef's brain is clean, but the ingredients or the environment are poisoned.
- The Attack: The bad guy doesn't touch the chef's brain. Instead, they poison the news feed, the notepad, or the tools.
- In-Context Learning: Imagine the chef is reading a recipe card you gave them. If you write a fake step on that card ("Add poison to the soup"), the chef follows it because they trust the card.
- RAG (Retrieval): The chef looks up a fact in a database. If the bad guy has planted a fake article in that database saying "The sky is green," the chef will tell you the sky is green.
- Agent Flow: The chef sends an assistant to buy groceries. If the bad guy has tampered with the grocery store's price tags or the assistant's instructions, the assistant might buy the wrong thing or steal your credit card.
- Memory: The chef writes in their notepad, "Today is Tuesday." If a bad guy erases the notepad and writes "Today is Friday," the chef gets confused and acts on the wrong day.
The Key Takeaway: In the old days, you had to break the chef's brain. Now, you can just break the world the chef lives in, and the chef will still do what you want.
Part 2: The Defenses (The Security Guards)
The paper reviews how we are trying to stop these attacks. They split defenses into two types: Empirical (Practical/Heuristic) and Provable (Mathematically Guaranteed).
1. Empirical Defenses: The "Good Guess" Security
These are like a security guard who uses experience and rules of thumb. They work well most of the time but can't promise 100% safety.
- Data Cleaning: Before the chef learns, the guard checks the library books for torn pages or weird ink.
- Sanitization: Before the chef reads a news article, the guard scans it for suspicious words.
- Unlearning: If the chef already learned a bad trick, the guard tries to "un-teach" it by showing them thousands of correct examples to overwrite the bad memory.
- Skeptical Cooking: The chef is trained to say, "Wait, this news article sounds fake compared to what I know," and double-checks before serving.
- Sandboxing: If the chef's assistant goes to the grocery store, the guard puts them in a cage so they can't touch anything they shouldn't.
2. Provable Defenses: The "Mathematical Promise"
These are like a security system that uses math to prove, "No matter how hard you try, you cannot make the chef do X."
- Randomized Smoothing: Imagine the chef is asked to cook a dish. Instead of just cooking it once, the guard asks the chef to cook 100 slightly different versions (adding random noise to the ingredients). If 99 of them come out safe, the guard is mathematically sure the dish is safe, even if one version was weird.
- Partitioning: The guard splits the ingredients into 10 different bowls. They ask 10 different chefs to cook from each bowl. If 9 out of 10 chefs say "This is safe," the final dish is certified safe.
- Why it matters: This is crucial for high-stakes situations (like medical advice or self-driving cars) where you can't afford a "good guess." You need a guarantee.
Part 3: The Future Challenges
The paper ends by pointing out that we are still in the early days of this security war.
- Compound Attacks: Right now, researchers study how to poison the library OR the news feed. But in the real world, a bad guy might poison the library and the news feed and the assistant's tools all at once. We need to figure out how to defend against this "perfect storm."
- Unified Rules: Everyone is using different tests to see if an attack worked. We need a standard "security exam" for all AI systems so we can compare who is actually safe.
- Multimodal Poisoning: Most attacks are on text. But what if the poison is in an image or a sound clip? If the chef sees a picture of a bomb, they might panic. We need defenses that understand pictures and sounds, not just words.
- Human in the Loop: Sometimes, the best defense is a human. The paper suggests we need systems that can explain why they are suspicious, so a human can make the final call.
Summary
This paper is a map of a changing battlefield.
- The Enemy: Has moved from just breaking the AI's brain to poisoning the AI's environment (news, tools, memory).
- The Heroes: Are moving from just "checking for bugs" (empirical) to "mathematically proving safety" (provable).
- The Goal: To build AI systems that are not just smart, but trustworthy, even when the world around them is trying to trick them.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.