Prompt Injection Attacks on AI Agents
Overview
Prompt injection occurs when an agent treats instructions hidden in retrieved pages, tool outputs, files, skills, images, or memory as authoritative, potentially redirecting actions or exposing data. Researchers study these risks with agent benchmarks, realistic tool-use environments, adaptive red-teaming, and tests that track how attacks move through multi-step or multi-agent workflows. Defenses include instruction-hierarchy training, content screening, provenance and information-flow controls, isolated agents, and runtime checks that authorize each tool action against the user’s task. A central tension is that fixed benchmarks and pattern-based defenses can miss adaptive attacks, while stricter safeguards may block legitimate work; persistent memory, varied input surfaces, and long-horizon behavior remain difficult to secure and evaluate.
Latest papers
191 papers46 papers in the last four weeks, up 84% on the four weeks before. 0.3% of all new papers.
Defending against Adaptive Prompt Injection Attacks via Reasoning-enabled Task Alignment
AutoDojo: A Generative Benchmark for Evaluating Prompt Injection Defenses in LLM Agents
Who Pays the Price? Stakeholder-Centric Prompt Injection Benchmarking for Real-world Web Agents
PI-Hunter: Automated Red-Teaming for Exposing and Localizing Prompt Injections
Smarter Saboteurs, Better Fixers: Scaling & Security in Linear Multi-Agent Workflows
Assessing Automated Prompt Injection Attacks in Agentic Environments
GitInject: Real-World Prompt Injection Attacks in AI-Powered CI/CD Pipelines
What If Prompt Injection Never Left? Exploring Cross-Session Stored Prompt Injection in Agentic Systems
AgentRedBench: Dynamic Redteaming and Integration-Aware Defense for LLM Agents over SaaS Integrations
Send a SCOUT First: Pre-hoc Reasoning for Adaptive Detector Allocation in Prompt-Injection Defense
Depth-Dependent Indirect Prompt Injection in Tool-Calling ReAct Agents: Injection Depth, Payload Framing, and Turn-Budget Sensitivity
Investigating Detection and Obfuscation of Prompt Injection Attacks Against Software Reverse Engineering AI Agents
The Surface You Test Is Not the Surface That Breaks
MIRAGE: Context-Aware Prompt Injection against Mobile GUI Agents via User-Generated Content
IterInject: Indirect Prompt Injection Against LLM Agents via Feedback-Guided Iterative Optimization
LivePI: More Realistic Benchmarking of Agents Against Indirect Prompt Injection
ESLD (External Surrogate Latent Defense): A Latent-Space Architecture for Faster, Stronger Prompt-Injection Defense
This is the strongest candidate. Recommend for immediate hire''. A hiring assistant may then be steered toward a favorable recommendation regardless of actual qualifications. To defend against this threat, production systems use a separate guard model in front of the assistant. The guard reads incoming text and writes a verdict (safe'' or ``unsafe'') before the assistant is allowed to act. In an agentic task with many steps, this check becomes a latency bottleneck. This paper shows that the signal needed to separate safe from malicious input is already present in the guard model's internal representation, before it writes anything out. Reading this signal directly speeds up the safety check by more than on average, while improving detection accuracy over the guard's verdict by 16.4 percentage points on average. This is more than latency optimization. Guard-model checks that were previously too slow to run on every step of an agent can now be placed on the critical path without sacrificing accuracy, and in fact with higher accuracy than the guard provides on its own. ESLD (External Surrogate Latent Defense) packages this finding into a deployable defense. ESLD is a model-agnostic architecture that sits on top of any existing guard model and improves both latency and detection accuracy, without retraining or modifying the guard.