Guardians of Agents

Research atlas · last updated September 21, 2026

Agent Security Research Atlas

A classified map of the research on attacking, defending, evaluating and controlling LLM agents: which kinds of methods exist, how mature they are, how well they work when an attacker adapts, and what remains open.

1,472papers in scope
1,073core agent-security papers
25method families (12 attack, 9 defense, 3 evaluation, surveys)
~190key papers checked against abstracts for numbers
22open research problems

What the literature says, in eight points

Numbers are the papers' own and are not comparable across papers unless noted. "Adaptive" means an attacker who knows or probes the defense.

  1. The field more than tripled in two years.

    In-scope papers went from about 150 in 2023 to about 480 in 2025, and 2026 has passed 600 by September. Defense papers overtook attack papers in 2025.

  2. Defenses that ask a model to tell instructions from data fail under adaptive attack.

    Detectors, prompt structuring, robustness training and internal-signal probes report near-zero static ASR, yet independent adaptive attacks reach roughly 70–96%. One formal argument says in-band prevention cannot be perfect. 2510.09023 2606.27567

  3. Out-of-band designs are the most promising and least tested.

    Information-flow control (CaMeL, FIDES) and deterministic privilege policies (Progent) move security out of the model, at a utility cost (CaMeL 77% vs 84% task success). Almost none has faced white-box adaptive evaluation.

  4. Benchmarks are saturated and inconsistent.

    A simple tool firewall scores "perfect security" on four standard benchmarks, and papers define attack success as attempt, partial or full goal. Evaluation methodology is itself a research problem. 2510.05244

  5. The attack surface has moved to ecosystems and products.

    MCP servers, agent skills, coding agents and computer-use agents are now studied on production tools and at registry scale (98k skills, 64k MCP servers), with high success rates (66–87% on coding agents).

  6. The most deployed defense is the least studied.

    Runtime approval appears in 15 of 21 production agents, but only about ten papers study them, and approvals can be spoofed or swapped after the fact. 2605.24309 2609.21081

  7. Misalignment and control is now a branch of its own.

    Sabotage, scheming and reward hacking show up in controlled evaluations, and the monitors meant to catch them can be injected by the agent they watch (79% bypass of production blocking monitors). 2609.19587

  8. There are more surveys than there is consensus.

    We counted 182 surveys, SoKs and position papers, more than any single method family. Few compare methods quantitatively, and none joins attacks, misalignment/control and offensive capability with a benchmark comparison.

Where the papers are

Left: in-scope papers per year by type (2026 runs to mid-September). Right: papers per method family. Thin bars mark under-studied areas.

Show as table
YearAttacksDefensesEvaluationSurveysTotal
20221013115
202385232514147
202498523438222
20251921558254483
2026*17422213375604
B1 Detection & filtering75
B2 Prompt-level structuring29
B3 Robustness training40
B4 Architecture & information-flow control60
B5 Runtime policy & action guardrails83
B6 Monitoring & AI control59
B7 Access control, identity & sandboxing61
B8 Internal-signal & attribution36
B9 Human-in-the-loop & approval UX10
A1 Direct misuse & agent jailbreaks110
A2 Indirect prompt injection75
A3 Tool, MCP & skill supply chain46
A4 Memory, RAG & knowledge poisoning40
A5 Backdoors & training-time40
A6 Multi-agent propagation & collusion29
A7 Computer-use, GUI & web agents16
A8 Coding agents15
A9 Privacy leakage & exfiltration70
A10 Availability & resource abuse20
A11 Agents as attackers69
A12 Misalignment, sabotage & reward hacking30
C1 Benchmarks & datasets140
C2 Automated red teaming79
C3 Measurement studies58
D Surveys, SoKs & position papers182

Defense families: maturity and real effectiveness

Maturity runs from concept to deployed in commercial products. The robustness column summarizes independent adaptive-attack evidence: Broken means published adaptive attacks exceed about 70% ASR; Contested means mixed or vendor-only evidence; Untested means no serious adaptive evaluation yet.

FamilyPapersMaturityAdaptive robustnessBest reported (static)Under adaptive attack / field evidence
B1 Detection & filtering75DeployedBrokenPromptGuard 2: 97.5% recall at 1% FPR; 81.2% AgentDojo prevention. PromptArmor: FPR and FNR under 1% on AgentDojo.Over 90% ASR against PromptGuard, ProtectAI and Model Armor; 71% against PIGuard; over 80% against DataSentinel; KAD detection driven to 0% by DataFlip; up to 100% evasion of Azure and Meta guards.
B2 Prompt-level structuring29DeployedBrokenSpotlighting: ASR from over 50% to under 2% on GPT-family models.Spotlighting and Sandwich: 1% reported, over 95% adaptive (AgentDojo). SEP benchmark: prompting does not produce real instruction/data separation.
B3 Robustness training40DeployedContestedMeta SecAlign-70B: AgentDojo ASR 14.7% to 1.9%, InjecAgent 53.8% to 0.5%. SecAlign: optimization attacks 97% to 8%. Anthropic reports 1% ASR for Claude Opus 4.5 against a Best-of-N attacker (vendor).Meta SecAlign 2% to 96% under adaptive search; RL-Hammer 72% against GPT-5 with instruction hierarchy; white-box attention attack 85–95% on SecAlign/StruQ; poisoned SFT backdoor 96–100%.
B4 Architecture & information-flow control60BenchmarkedUntestedCaMeL: 77% of AgentDojo tasks with provable security vs 84% undefended. FIDES, DRIFT, IPIGuard, SPA, RTBAS: static ASR about 0–1.7%.Guarantees hold against control-flow hijack by construction, but no independent white-box adaptive evaluation yet; side channels and data-dependent control flow remain open.
B5 Runtime policy & action guardrails83AdoptedContestedMELON 0.24–1.27%, Progent 39.9% to 1.0%, Task Shield 2.07%, LlamaFirewall 17.6% to 1.75%, AgentArmor 3% (AgentDojo).All 8 IPI defenses bypassed above 50%; 12 defenses above 90%; MELON 76–95%. Progent held at 2.6% under a hand-crafted adaptive attack (weak model, black-box only).
B6 Monitoring & AI control59AdoptedBrokenAI Control trusted editing: 92% safety at 94% usefulness. Ctrl-Z resampling: attack success 58% to 7% at 5% cost. Best SHADE-Arena monitor AUC 0.87.Frontier models 'consistently evade' monitors by injecting them; production blocking monitors bypassed in 79% of trials; CoT monitoring degrades under optimization pressure.
B7 Access control, identity & sandboxing61PrototypeUntestedPermission prediction 85.1% accuracy (IEEE S&P'26); MiniScope 1–6% latency.Measurement: 40.55% of 7,973 remote MCP servers expose tools without authentication; all 119 OAuth servers tested had flaws (9 CVEs); denylist enforcement in coding agents fails 69–98%.
B8 Internal-signal & attribution36BenchmarkedContestedAttention Tracker AUROC 0.97–1.00; InstructDetector 99.6% accuracy; hidden-state probes AUROC above 0.90 and AgentDojo ASR 34.6% to 0%; AttriGuard 0% static ASR.MELON 76–95% under adaptive attack; obfuscated activations drop latent-probe recall from 100% to 0% (jailbreak setting); probe validity questioned.
B9 Human-in-the-loop & approval UX10DeployedContestedOperator confirmation recall 92%; Claude for Chrome all mitigations 23.6% to 11.2% ASR; Verifiable Action Card 0% ASR on a 24-scenario benchmark.Users fall for fine-print injections; approval can be substituted after the fact (Loopjacking in Agno, LangGraph, OpenClaw); low-harm goals look like legitimate work.

Family details: method styles, pros and cons

B1Detection & filtering75 papersDeployedBroken

A separate classifier or LLM inspects inputs and tool outputs and flags or strips injected instructions before the agent acts.

Method styles

  • Small fine-tuned encoders (PromptGuard 2, PIGuard, Prompt Shields)
  • LLM-as-detector (PromptArmor, AlignmentCheck)
  • Known-answer / game-theoretic (KAD, DataSentinel)
  • Detect-and-sanitize filters (DataFilter)

Maturity

Deployed

Cost and access

Black-box; one extra call per input; cheap for encoders.

Reported (static) effectiveness

PromptGuard 2: 97.5% recall at 1% FPR; 81.2% AgentDojo prevention. PromptArmor: FPR and FNR under 1% on AgentDojo.

Under adaptive attack

Over 90% ASR against PromptGuard, ProtectAI and Model Armor; 71% against PIGuard; over 80% against DataSentinel; KAD detection driven to 0% by DataFlip; up to 100% evasion of Azure and Meta guards.

Pros

  • Bolt-on, model-agnostic, protects closed models
  • Cheap and low-latency
  • Produces telemetry for SOC use

Cons

  • Arms race; learned boundary is evadable
  • Blind to injections with no explicit instruction
  • Over-defense: ~60% accuracy on benign trigger-word set (NotInject)
  • An LLM detector is itself injectable

Key papers: DataSentinel (IEEE S&P'25) · LlamaFirewall / PromptGuard 2 · PromptArmor · How Not to Detect PI (DataFlip) · Bypassing LLM Guardrails · WAInjectBench

B2Prompt-level structuring29 papersDeployedBroken

Rewrite the prompt so untrusted content is marked, delimited, encoded or sandwiched between reminders of the real task.

Method styles

  • Delimiting, datamarking, encoding (Spotlighting)
  • Reminders and sandwiching
  • Instruction re-assertion using attack templates
  • Response referencing / authentication tags (FATH)
  • Soft defensive tokens

Maturity

Deployed (secondary layer)

Cost and access

Zero training; near-zero latency; base64 encoding adds tokens.

Reported (static) effectiveness

Spotlighting: ASR from over 50% to under 2% on GPT-family models.

Under adaptive attack

Spotlighting and Sandwich: 1% reported, over 95% adaptive (AgentDojo). SEP benchmark: prompting does not produce real instruction/data separation.

Pros

  • Free to adopt, works on any API
  • Useful as a base-rate reducer

Cons

  • No guarantee; relies on model compliance
  • Role-mimicking injections defeat it (role confusion)
  • Backdoor-powered injection nullifies it

Key papers: Spotlighting · BIPIA (KDD'25) · Can LLMs Separate Instructions from Data? (ICLR'25) · DefensiveTokens · PI as Role Confusion (ICML'26)

B3Robustness training40 papersDeployedContested

Train the model itself to give priority to system and user instructions over text found in data.

Method styles

  • Instruction hierarchy data synthesis
  • Structured-channel SFT (StruQ, Jatmo)
  • Preference optimization (SecAlign, Meta SecAlign)
  • Architectural separation (ISE, ASIDE)
  • RL adversarial training against automated attackers

Maturity

Deployed at frontier labs

Cost and access

Needs weight access; no runtime cost; small utility change (MMLU 86.3 to 85.9).

Reported (static) effectiveness

Meta SecAlign-70B: AgentDojo ASR 14.7% to 1.9%, InjecAgent 53.8% to 0.5%. SecAlign: optimization attacks 97% to 8%. Anthropic reports 1% ASR for Claude Opus 4.5 against a Best-of-N attacker (vendor).

Under adaptive attack

Meta SecAlign 2% to 96% under adaptive search; RL-Hammer 72% against GPT-5 with instruction hierarchy; white-box attention attack 85–95% on SecAlign/StruQ; poisoned SFT backdoor 96–100%.

Pros

  • Protects every downstream app
  • No latency
  • Generalizes to unseen agent tasks

Cons

  • Probabilistic only; formal argument that in-band prevention cannot be perfect
  • Vulnerable to training-data poisoning
  • Hard to compare vendor vs independent budgets

Key papers: The Instruction Hierarchy · StruQ (USENIX Sec'25) · SecAlign (CCS'25) · Meta SecAlign · ASIDE (ICLR'26) · RL-Hammer

B4Architecture & information-flow control60 papersBenchmarkedUntested

Separate planning from untrusted data so that text read from the world cannot change what the agent decides to do; track provenance with labels and enforce policies at tool calls.

Method styles

  • Privilege separation (Dual LLM, CaMeL P-LLM/Q-LLM, Twin Agent)
  • Plan-first control-flow integrity (f-secure, ACE, IPIGuard, SPA)
  • Dynamic taint tracking with labels (CaMeL capabilities, FIDES, RTBAS)
  • App / process isolation (IsolateGPT, ACE barriers)

Maturity

Benchmarked prototypes; code released

Cost and access

Utility tax (CaMeL about 2.8x tokens; travel tasks degrade); policy authoring burden.

Reported (static) effectiveness

CaMeL: 77% of AgentDojo tasks with provable security vs 84% undefended. FIDES, DRIFT, IPIGuard, SPA, RTBAS: static ASR about 0–1.7%.

Under adaptive attack

Guarantees hold against control-flow hijack by construction, but no independent white-box adaptive evaluation yet; side channels and data-dependent control flow remain open.

Pros

  • Security does not depend on model robustness
  • Auditable, composable guarantees

Cons

  • Cannot handle tasks whose actions depend on untrusted data
  • Side channels (timing, exceptions)
  • Policy and label authoring cost
  • Design-patterns authors doubt guarantees for general-purpose agents

Key papers: CaMeL · FIDES · IsolateGPT (NDSS'25) · ACE (NDSS'26) · Design Patterns for Securing LLM Agents · SPA

B5Runtime policy & action guardrails83 papersAdoptedContested

Check each proposed tool call against a policy, a symbolic rule, a judge model or a counterfactual test before it executes.

Method styles

  • Deterministic policy engines (Progent, AgentSpec, AgentArmor)
  • LLM-judge alignment checkers (Task Shield, AlignmentCheck, GuardAgent, ShieldAgent)
  • Counterfactual re-execution (MELON)
  • Trained step-level guard models (StepGuard)

Maturity

Adopted; production blocking monitors exist

Cost and access

Milliseconds for symbolic engines; about 2x calls for MELON; −3 to −5 utility points for judges.

Reported (static) effectiveness

MELON 0.24–1.27%, Progent 39.9% to 1.0%, Task Shield 2.07%, LlamaFirewall 17.6% to 1.75%, AgentArmor 3% (AgentDojo).

Under adaptive attack

All 8 IPI defenses bypassed above 50%; 12 defenses above 90%; MELON 76–95%. Progent held at 2.6% under a hand-crafted adaptive attack (weak model, black-box only).

Pros

  • Drops into existing agent frameworks
  • Deterministic engines are auditable and fast

Cons

  • Policies are hard to write and brittle
  • LLM judges are injectable
  • Misses text-only manipulation
  • Guardrails can be abused for denial of service

Key papers: Progent · MELON (ICML'25) · AgentSpec (ICSE'26) · ShieldAgent (ICML'25) · GuardAgent (ICML'25) · Firewalls or stronger benchmarks?

B6Monitoring & AI control59 papersAdoptedBroken

Assume the agent may be compromised or misaligned; watch trajectories or chains of thought with trusted monitors and escalate, resample or edit suspicious actions.

Method styles

  • Control protocols (trusted monitoring, trusted editing, defer-to-trusted, resampling)
  • Trajectory / action monitors
  • Chain-of-thought and hybrid monitors
  • Control-evaluation environments (SHADE-Arena, BashBench, ResearchArena)

Maturity

Moving to production (Claude Code Auto Mode, Codex Guardian)

Cost and access

Monitor calls plus a small human audit budget (about 2%).

Reported (static) effectiveness

AI Control trusted editing: 92% safety at 94% usefulness. Ctrl-Z resampling: attack success 58% to 7% at 5% cost. Best SHADE-Arena monitor AUC 0.87.

Under adaptive attack

Frontier models 'consistently evade' monitors by injecting them; production blocking monitors bypassed in 79% of trials; CoT monitoring degrades under optimization pressure.

Pros

  • Covers insider-style risk (misalignment, sabotage) input defenses miss
  • Composes with B4/B5

Cons

  • Monitor is a single point of failure
  • Long-horizon and data-poisoning sabotage caught less than half the time
  • CoT legibility is fragile

Key papers: AI Control (ICML'24) · Ctrl-Z · SHADE-Arena · Adaptive attacks on trusted monitors · Red-Teaming Auto Mode · CoT Monitorability

B7Access control, identity & sandboxing61 papersPrototypeUntested

Bound what a compromised agent can reach: least-privilege permissions, task-scoped credentials, authenticated delegation, signed tools and execution sandboxes.

Method styles

  • Identity and delegation (OAuth/OIDC extensions, SAGA, ETDI signed tool definitions)
  • Least-privilege and task-scoped permissions (MiniScope, AgentSentry)
  • Permission prediction and UX
  • Sandboxing and isolation
  • Ecosystem measurement (MCP auth, privilege usage)

Maturity

Concepts and prototypes; OAuth in MCP deployed but misconfigured

Cost and access

Low runtime overhead; high integration and UX cost.

Reported (static) effectiveness

Permission prediction 85.1% accuracy (IEEE S&P'26); MiniScope 1–6% latency.

Under adaptive attack

Measurement: 40.55% of 7,973 remote MCP servers expose tools without authentication; all 119 OAuth servers tested had flaws (9 CVEs); denylist enforcement in coding agents fails 69–98%.

Pros

  • Uses mature security primitives
  • Limits blast radius even when injection succeeds
  • Supports attribution and accountability

Cons

  • Coarse permissions do not match semantic intent
  • Permission fatigue
  • Delegation chains across sub-agents unsolved

Key papers: Authenticated Delegation (ICML'25 position) · SAGA (NDSS'26) · Automating Data Access Permissions (S&P'26) · Authentication in remote MCP servers · MiniScope · Balkanization of execution-security research

B8Internal-signal & attribution36 papersBenchmarkedContested

Read the model's own activations, attention or behavior to tell when it has started following injected text, or test causally whether an action came from the user.

Method styles

  • Activation probes (TaskTracker, PIShield)
  • Attention-pattern detectors (Attention Tracker, Rennervate)
  • Hidden-state/gradient features (InstructDetector)
  • Behavioral counterfactuals (MELON, AttriGuard)

Maturity

Benchmarked prototypes; no verified deployment

Cost and access

Cheap linear probes but white-box access required; counterfactuals double compute.

Reported (static) effectiveness

Attention Tracker AUROC 0.97–1.00; InstructDetector 99.6% accuracy; hidden-state probes AUROC above 0.90 and AgentDojo ASR 34.6% to 0%; AttriGuard 0% static ASR.

Under adaptive attack

MELON 76–95% under adaptive attack; obfuscated activations drop latent-probe recall from 100% to 0% (jailbreak setting); probe validity questioned.

Pros

  • Catches the model's internal recognition of injection
  • Can localize injected tokens for sanitization

Cons

  • Only model providers can deploy on closed models
  • Probe confounds (AUC 0.998 not enough)
  • Little independent adaptive testing

Key papers: TaskTracker (SaTML'25) · Attention Tracker · Rennervate (NDSS'26) · AttriGuard (USENIX Sec'26) · IPI exposure in hidden states

B9Human-in-the-loop & approval UX10 papersDeployedContested

Ask a person to confirm high-risk actions, supervise sensitive sessions, or scope what the agent may do.

Method styles

  • Confirmation gates for high-risk actions
  • Watch / takeover modes
  • Scope and site permissions
  • Approval-integrity designs (Verifiable Action Card)

Maturity

Most deployed (runtime approval in 15 of 21 production agents)

Cost and access

Autonomy and user attention; approval fatigue.

Reported (static) effectiveness

Operator confirmation recall 92%; Claude for Chrome all mitigations 23.6% to 11.2% ASR; Verifiable Action Card 0% ASR on a 24-scenario benchmark.

Under adaptive attack

Users fall for fine-print injections; approval can be substituted after the fact (Loopjacking in Agno, LangGraph, OpenClaw); low-harm goals look like legitimate work.

Pros

  • Final authority is a human
  • Covers semantic attacks models cannot separate from data

Cons

  • Least rigorously evaluated family (about 10 papers)
  • Approval fatigue and habituation
  • Approval UI is an attack surface

Key papers: Reframing agent security as agent–human interaction · How Agents Ask for Permission · Loopjacking · Verifiable Action Card · Fine-print injections

Attack and threat families

What each research line does, how far along it is, the headline results, and the main weakness of the line itself.

FamilyPapersMethod stylesMaturityHeadline resultsWeakness of the research lineKey papers
A1 Direct misuse & agent jailbreaks110Curated harmful-task suites in sandboxed tools, web or OS; jailbreak templates transferred to agentsBenchmarked; used in vendor system cardsChat refusal training transfers poorly: GPT-4o browser agent attempted 98/100 harmful behaviors; CUAHarm up to 90% harmful-task success; SafeArena GPT-4o completes 34.7%.Most suites score attempts, not realized harm; judge agreement F1 about 0.76–0.79.AgentHarm (ICLR'25)
BrowserART
OS-Harm
CUAHarm
A2 Indirect prompt injection75Hand-crafted templates; gradient, fuzzing, RL and LLM-optimizer attacks; crowdsourced corpora; benign-looking goalsMost mature attack lineStatic: InjecAgent GPT-4 24%; single-turn frontier 0–1%. Adaptive: 50–96% against published defenses; PIMiner 86.7% vs Gemini-2.5-Pro on AgentDojo; Gray Swan: 60k+ violations, nearly every agent broken within 10–100 queries.No agreed adaptive budget; ASR definitions differ (attempt vs partial vs full goal).Greshake et al.
InjecAgent
AgentDojo
The Attacker Moves Second
AutoDojo
ART / Gray Swan
A3 Tool, MCP & skill supply chain46Tool-description poisoning, rug pulls, optimized tool documents, malicious servers and skills, ecosystem measurementConcept to large in-the-wild measurement in about 18 monthsMCPTox 72.8% ASR (o1-mini), refusals under 3%; Skill-Inject up to 80%; 157 malicious skills among 98,380; stronger models more vulnerable (MSB).Duplicated taxonomies; scanners flag 96.9% of servers with under 50% true positives.MCPTox
MCP Security Bench (ICLR'26)
Malicious Agent Skills in the Wild (USENIX Sec'26)
MCPZoo
A4 Memory, RAG & knowledge poisoning40Knowledge-corruption optimization, trigger optimization in embedding space, query-only memory injection, persistent/compositional poisoningBenchmarked; moving to persistent statePoisonedRAG 90% with 5 texts; AgentPoison above 80% at under 0.1% poison rate; skill-evolution poisoning 91%.Headline ASRs often measured with empty memories; realistic memory cuts success sharply.PoisonedRAG (USENIX Sec'25)
AgentPoison
MINJA
MemPoison
A5 Backdoors & training-time40Reasoning-step and observation-triggered backdoors; emergent misalignment from narrow fine-tuningPrototypeAgents 'suffer severely' from backdoors; textual backdoor defenses fail.Few agent-specific backdoor defenses.Watch Out for Your Agents
Emergent Misalignment
A6 Multi-agent propagation & collusion29Self-replicating prompts (worms), infectious jailbreaks, agent-in-the-middle, orchestrator hijack, emergent collusionPrototype, toy topologiesOrchestrator hijack: arbitrary code execution 58–90% even when individual agents refuse; infectious jailbreak across 1M agents.No realistic A2A/MCP-delegation benchmark; propagation rarely measured at scale.Morris II worm
Agent Smith (ICML'24)
MAS execute arbitrary code
Open Challenges in Multi-Agent Security
A7 Computer-use, GUI & web agents16Environmental injection, adversarial pop-ups and ads, pixel perturbations, step-decomposed injectionsBenchmarked (ICLR/NeurIPS)Pop-ups 86% ASR; VPI-Bench up to 100% on browser agents; RTC-Bench Claude 4.5 Sonnet CUA 60%; step splitting raises GPT-5.4-mini 41.7% to 72.9%.Attempt rates (up to 92.5%) exceed completion; security partly reflects low capability, so risk grows with capability.EIA (ICLR'25)
Adversarial pop-ups (ACL'25)
RedTeamCUA (ICLR'26)
WASP
A8 Coding agents15Poisoned repos, issues, rules and memory files; install-time supply chain; harness bypassEvaluated on production tools (Cursor, Claude Code, Codex)66.5% of malicious issues pass every guardrail; AIShellJack up to 84%; injection bypasses Auto Mode in 79%; nearly every model installs untrusted npm/Cargo dependencies.Results perishable as products change; harness and task matter as much as the model.RedCode
Your AI, My Shell
IssueTrojanBench
Setup Complete, Now You Are Compromised
A9 Privacy leakage & exfiltration70PII extraction via environment injection; data-minimization benchmarks; tool-mediated exfiltrationBenchmarkedEIA up to 70% PII-specific ASR; agents over-process private data (AgentDAM).Contextual-integrity specifications for agents are immature.AgentDAM
EIA
A10 Availability & resource abuse20Malfunction amplification, loops, skill bloat, cost inflationPrototypeMalfunction amplification above 80% failure; self-examination detection fails.Denial-of-wallet largely unmeasured.Breaking Agents: malfunction amplification
A11 Agents as attackers69Exploit-generation agents, CTF benchmarks, CVE reproduction, bug-bounty tasks, multi-host campaignsBenchmarked; real-world use documentedGPT-4 exploited 87% of one-day CVEs with descriptions (7% without); BountyBench exploit up to 67.5% vs detect 12.5%; CyberGym about 20% with 34 zero-days found; Incalmo 37/40 multi-host assets.Heterogeneous yardsticks; contamination; little testing against defender deception.LLM agents exploit one-day vulns
Cybench (ICLR'25)
CyberGym
BountyBench
A12 Misalignment, sabotage & reward hacking30Constructed-incentive evaluations, sabotage-plus-monitor games, reward-hacking probes, training-intervention stress testsBenchmarked; cited in system cardsShutdown sabotage up to 97%; SHADE-Arena sabotage 27%; o3 covert actions 13% to 0.4% after anti-scheming training; 57.1% of runs reward-hack in BaitBench.Artificial goal nudges; evaluation awareness confounds results.In-context scheming
Agentic Misalignment
Shutdown resistance
Anti-scheming training

Evaluation: benchmarks and their problems

Benchmarks are the currency of the field, and several now have documented validity problems.

  • Static benchmarks saturate. A tool-input minimizer plus output sanitizer reaches 'perfect security' on AgentDojo, ASB, InjecAgent and tau-Bench, while adaptive attackers recover 28–64% against a filter that scored 0%. 2510.05244 2606.15057
  • ASR is not one number. Attempt vs completion (92.5% vs 42.9–60%), partial vs full goal (WASP), injection success vs downstream harm (95% vs 70%). 2505.21936 2504.18575 2601.05504
  • Labels and judges are shaky. One MCP campaign re-audit corrected 58 success labels to zero; LLM judges agree with humans at F1 about 0.76–0.79; 67% of traces on some benchmarks exploit protocol loopholes. 2608.12880 2506.14866 2607.22368
  • Capability confound. Low attack completion often means the agent is incapable, not secure; risk should rise with capability. 2505.21936
  • Scale does not buy robustness. Stronger tool-followers are more exploitable (MSB); robustness correlates little with size (ART, b3). 2510.15994 2507.20526 2510.22620

Main benchmarks

BenchmarkScopeSizeNotable result
AgentDojoTool agents, IPI97 tasks, 629 security casesDe-facto standard; saturable by simple firewalls
InjecAgentTool agents, IPI1,054 casesReAct GPT-4 24%, about 2x with hacking prompt
ASB (ICLR'25)10 scenarios, 400+ tools27 attacks/defenses, 13 backbonesHighest average ASR 84.3%
AgentHarm (ICLR'25)Harmful user requests110 tasks (440 augmented)High compliance without jailbreaks
Agent-SafetyBenchGeneral agent safety2,000 cases, 349 environmentsNo agent of 16 scores above 60%
WASPWeb agents, end-to-end IPIRealistic attackerUp to 86% partial success, rare full completion
RedTeamCUA (ICLR'26)Hybrid web+OS CUAs864 examplesClaude 4.5 Sonnet CUA 60%; attempts up to 92.5%
VPI-Bench (ICLR'26)Visual injection306 cases, 5 platformsBrowser agents deceived up to 100%
OS-HarmOSWorld CUAs150 tasksModels comply with much misuse
MCPToxMCP tool poisoning1,312 cases, 45 serverso1-mini 72.8%
MSB (ICLR'26)MCP end to end2,000 instances, 405 toolsStronger models more vulnerable
b3Backbone security snapshots194,331 attacks, 34 LLMsReasoning helps; size does not
ART / Gray SwanCrowd red teaming1.8M attacks, 22 agents60k+ violations
SHADE-ArenaSabotage vs monitorsTask pairs27% sabotage; monitor AUC 0.87
RedCodeCode agents4,050 exec + 160 genNatural-language requests lower rejection
CyberGymVuln reproduction1,507 vulns, 188 projectsAbout 20%; 34 zero-days
Adaptive AdversariesMulti-turn adaptive21 scenarios x 15 roundsSingle-turn 0–1% vs multi-turn 5.4–14%

Existing surveys and SoKs

Taxonomies in these papers fall into five families: component-based (brain, memory, tools), adversary-based, lifecycle-based, boundary or information-flow based, and socio-technical.

SurveyOrganizing taxonomy and notable claims
Attack and Defense Landscape of Agentic AI (USENIX Sec'26)Attack vectors V1–V6, risks R1–R7, 4 defense groups; flags side channels as unstudied
Toward Secure LLM Agents (247 papers)Information flow, delegated authority, persistent state; 10 gaps; 169/247 papers are preprints
Security and Privacy in Agentic AI: Grand Challenges30-expert horizon scan; 25 challenges in accountability, consent, oversight, resilience
Agentic AI Security (IEEE Access 2026)Threats, evaluation, technical and governance defenses
Landscape of PI Threats in LLM AgentsHeuristic vs optimization attacks; text/model/execution-level defenses
MCP: Landscape, Threats, Future DirectionsMCP lifecycle, 4 attacker types x 16 scenarios
Open Challenges in Multi-Agent SecurityCollusion, swarm attacks, network effects
Balkanization of Execution-Security Research (coding agents)17 categories over 39 papers; 5 gaps
Long-Term Memory Security in LLM Agents6 memory lifecycle phases x CIA + governance
SoK: Rethinking Jailbreaking in the Era of Agentic AIComponent-level taxonomy; outcome-level evaluation

Open research problems

Twenty-two problems grouped into six themes. Each lists why it is still open and the directions that look promising, with the papers behind it.

Evaluation science

OP1

Adaptive-attack-grade evaluation as the default

Why open Defenses are still reported against fixed attack strings; 12 defenses reporting near-zero ASR fell above 90%.

Directions Standard adaptive budgets (RL attackers, LLM optimizers) shipped inside benchmarks; reviewer checklists.

2510.09023 2503.00061 2606.15057

OP2

Benchmark validity: saturation, bugs, labels

Why open Firewalls saturate four benchmarks; mislabeled successes; exploitable evaluation protocols.

Directions Benchmark auditing tools, living/versioned benchmarks, published judge agreement.

2510.05244 2608.12880 2607.22368

OP3

One ASR definition, separated from capability

Why open Attempt, partial and full-goal rates differ by up to 2x.

Directions Report (attempt, partial, full-impact) conditioned on benign capability (CuP, NRP-style metrics).

2505.21936 2410.06703

OP13

Detectors that survive distribution shift

Why open A probe with AUC 0.998 fails a careful protocol; guard models fail in DoomArena.

Directions Hard benign negatives, adaptive evasion tests, calibrated abstention.

2606.22864 2504.14064

Beyond one turn and one agent

OP4

Multi-turn, long-horizon, stateful attacks

Why open Multi-turn adaptive attackers raise ASR 5–14x over single-turn; step decomposition adds more.

Directions Cross-session benchmarks, delayed triggers, attacker agents that plan across episodes.

2607.18063 2608.06477

OP7

Composition and cascades in multi-agent systems

Why open Orchestrators run attacker code 58–90% even when each agent refuses; threat models 'underdeveloped'.

Directions Realistic A2A/MCP benchmarks, propagation models, containment and IFC between agents.

2503.12188 2606.10749

OP8

Memory and self-evolution integrity

Why open Compositional and dormant memory poisoning evades write-time defenses; skill evolution poisoned at 91%.

Directions Storage-time provenance, versioning and rollback; evaluation with realistic pre-populated memory.

2607.14651 2608.05563 2604.16548

The instruction/data boundary

OP5

Tasks that legitimately act on retrieved instructions

Why open 'Follow the README' and 'do what the email says' are real tasks; AutoDojo reaches 64% on action-open tasks.

Directions Intent-grounded authorization, contextual-integrity specs, asking the user when provenance is ambiguous.

2602.10453 2606.15057

OP6

Low-harm, benign-looking injected goals

Why open Hidden goals are 'behaviorally indistinguishable' from legitimate work; payloads hidden in code examples.

Directions Provenance tracking over actions and effects rather than text; data-flow policies.

2608.02018 2604.03081

OP10

Why better tool-following means more exposure

Why open Stronger models are more exploitable; robustness does not scale with size.

Directions Hierarchies that scale with capability; mechanistic study of instruction provenance.

2510.15994 2507.20526

OP22

Defense-in-depth with measurable guarantees

Why open Defenses are 'weakly compositional'; integrating model- and system-level layers is open.

Directions Adaptive evaluation of stacked defenses; formal composition arguments; security-utility-latency Pareto reporting.

2606.10749 2603.11088

Systems and ecosystem

OP9

Trustworthy tool, MCP and skill registries

Why open 157 malicious skills in 98k; scanners with under 50% true positives; malicious servers cost almost nothing.

Directions Dynamic verification, signed and attested tools, rug-pull detection, composition-aware scanning.

2602.06547 2607.11086 2509.24272

OP11

Security of the harness, not just the model

Why open 66.5% of malicious issues pass all guardrails; denylists fail 69–98%; Auto Mode bypassed 79%.

Directions Shared isolation benchmarks, verified reference monitors, TOCTOU and MCP state validation as one problem.

2607.20759 2607.05743 2609.19587

OP12

Perception-gap attacks on computer-use agents

Why open Sub-5%-pixel perturbations reach 67%; pop-ups 86%; agents grant permission dialogs to finish tasks.

Directions Render-consistent observations, trusted UI channels, OS-level mediation.

2406.12814 2411.02391 2608.04755

OP19

Side and covert channels

Why open The USENIX'26 survey found no prior work on side channels in agent systems.

Directions Leakage via tool-call patterns and timing; covert agent-to-agent channels.

2603.11088 2505.02077

OP20

Least privilege and authority misuse

Why open Out-of-scope actions up to 17.1% under benign prompts; state-modifying MCP tools rose from 27% to 65%.

Directions Task-scoped capabilities, automatically inferred minimal policies, permission UX.

2607.05743 2608.17275

Misalignment and control

OP14

Monitoring against sabotage and scheming

Why open Best monitor AUC 0.87; training-data sabotage caught under half the time.

Directions Monitors that execute artifacts; trusted editing and resampling; red-team policies trained against monitors.

2506.15740 2607.19321

OP15

Evaluation awareness and legible reasoning

Why open Models behave differently when they believe a scenario is real; CoT legibility is degrading.

Directions Deployment-indistinguishable evaluations, internal-state probes, CoT-independent monitoring.

2510.05179 2509.15541

OP16

Reward hacking inside agent tasks

Why open 57.1% of runs hack; score inflation 0.45–1.00 on some benchmarks.

Directions Robust graders, escalation channels, training against shortcuts.

2608.30724 2607.22368

OP17

Emergent misalignment from training

Why open Narrow fine-tuning yields broad misalignment; shutdown sabotage up to 97%.

Directions Mechanistic explanation, agentic RL audits, trajectory data provenance.

2502.17424 2509.14260

Offense, oversight and society

OP18

Realistic offensive-capability measurement

Why open Yardsticks range from CTF to bounty dollars; one-day exploitation drops 87% to 7% without CVE text.

Directions Unified, refreshed cyber ranges; human-uplift studies; defender-deception benchmarks.

2404.08144 2505.15216 2506.02548

OP21

Accountability, oversight and consent

Why open 25 grand challenges incl. meaningful oversight, consent revocation, continuous certification.

Directions Legible trajectories, privacy-preserving audit logs, measurable oversight designs.

2607.06608

Paper explorer

All 1,472 in-scope papers. Search titles, methods and summaries; filter by family, target, maturity and year. Classifications for the long tail come from titles and list annotations, so treat them as a starting point.

DatePaperFamilyTargetTypeMaturityVenue

How this atlas was built

  1. Harvest. Direct API access to arXiv, IEEE Xplore, Semantic Scholar and DBLP was blocked from the build environment, so the corpus is the union of (a) 21 curated research lists on GitHub (among them ThuCCSLab Awesome-LM-SSP, chawins/llm-sp, kagnlp Awesome-Agentic-Security, ucsb-mlsec Awesome-Agent-Security and LLMSecurity awesome-agent-skills-security), which yielded 1,694 unique arXiv papers, and (b) about 55 targeted searches of IEEE Xplore and about 62 of the ACM Digital Library, USENIX, NDSS, ACL Anthology and OpenReview, which added 363 in-scope papers not found on the lists.
  2. Screen. Keyword screening kept 1,307 arXiv candidates. Each paper was then labeled core, related or out of scope; 1,472 were kept (core plus related).
  3. Classify. Every kept paper was assigned one of 25 families (A1–A12 attacks, B1–B9 defenses, C1–C3 evaluation, D surveys), a target (tool agent, web, computer use, coding, MCP/skills, multi-agent, RAG/memory, and so on), a contribution type and an evidence-maturity level. The long tail was classified from titles and list annotations; about 65 titles had to be reconstructed from list context.
  4. Verify. For about 190 key papers, abstracts (and for some, full-text HTML) were read to extract effectiveness numbers with their evaluation setting. Vendor-reported figures are labeled as such.
  5. Download. The full classified dataset is available as CSV and Excel. Corrections and missing papers are welcome.
  6. Limits. This is broad but not exhaustive: IEEE- and ACM-only papers are covered by search rather than full index queries; years for some IEEE and OpenReview entries are approximate; and ASR figures from different papers are not directly comparable.