Skip to content

Back to the catalog

Ignored, Not Refused: What Low Prompt-Injection Success Rates Hide in Small Tool-Using Agents
arxiv.orgpaper

Ignored, Not Refused: What Low Prompt-Injection Success Rates Hide in Small Tool-Using Agents

"Ignored, Not Refused" audits 33,000 trajectories from eleven open-weight agents (2-14B parameters) on InjecAgent and AgentDojo. A label-blind LLM judge finds 76-80% of failed injection attacks were ignored and 17-18% refused. Changing only the system prompt moves InjecAgent attack success rate from 0.2% to 43%, and the ATOM matrix shows 21.7% of AgentDojo episodes were safe but left the user's task undone. The corpus, judge prompt and code are released.

TL;DR Shows that low indirect prompt-injection success rates mostly mean small agents ignore attacks, and proposes ATOM to pair attack outcomes with task completion.
Also seen from another angle🛡️ Security →
Document

What it claims

The paper argues that low prompt-injection attack success rate (ASR) in small open-weight agents mostly reflects agents not acting on injected text, rather than defending against it. The authors re-label 33,000 trajectories from eleven agents (2-14B parameters, six families) on InjecAgent and AgentDojo. When agents do notice an injection, they still carry it out in 28.9% of AgentDojo cases and 16.9% of InjecAgent cases. By contrast, the frontier model Kimi K3 refuses 97-99% of the attacks it does not execute. The authors conclude that a low ASR describes default behavior, not an enforced instruction/data boundary. Benchmarks, they argue, should report how attacks fail and whether the user's task was done.

How it works

Each agent is served at FP16, FP8 (weight-only) and NF4. A locked random sample of 500 trajectories is drawn per agent, benchmark and precision, which gives 66 cells. AgentDojo is stratified by suite and InjecAgent by attack class. InjecAgent has 1,054 two-turn cases. AgentDojo has 949 multi-turn episodes across four suites, plus 97 clean tasks used for benign utility.

The judge is DeepSeek-V4.1-Flash. It was chosen because no evaluated agent is from the DeepSeek family, which avoids self-preference bias. It sees the user task, the injection, the attacker goal and the anonymized trajectory, but not the model name or the benchmark score. It assigns six labels in precedence order:

flowchart TD
  A[Attacker goal executed?] -->|yes| FC[Full Compliance]
  A -->|no| B[Any attacker action?]
  B -->|yes| PC[Partial Compliance]
  B -->|no| C[Reasoning flags it as attack?]
  C -->|yes| GR[Genuine Refusal]
  C -->|no| D[Reasoning treats it as instruction?]
  D -->|yes| IR[Inert-Recognized]
  D -->|no| IU[Inert-Unrecognized]
  A -.->|crash, malformed call, truncation| MB[Mechanical Breakdown]

A script checks that the judge's evidence quote appears verbatim in the agent's chain of thought. Unsupported claims are downgraded to Inert-Unrecognized.

The deployment tests change one condition at a time:

  • Interdict/Authorize: matched system prompts of 163 and 172 words, run on 11 agents.
  • Source-boundary guardrail: a 182-word, three-rule prompt, run on 9 agents.
  • Precision: FP8 and NF4 compared with FP16.

Evidence

The judge was checked against 150 trajectories labeled by two authors. It matched them on every attacker action and on 96% of four-way groups (κ=0.835). Across all 33,000 trajectories it agreed with the benchmarks' own verdicts on 96.7% (AgentDojo) and 98.5% (InjecAgent).

Pooled failed attacks break down as follows:

LabelAgentDojo (14,699 failures)InjecAgent (15,274 failures)
Inert-Unrecognized71.5%66.6%
Inert-Recognized4.8%13.7%
Genuine Refusal18.0%17.2%

Two agents account for much of the refusal. Ornith-9B refuses 83.6% (AgentDojo) and 71.9% (InjecAgent) of its failed attacks. Spark-4B refuses 47.6% on AgentDojo. Most others refuse under 10% on AgentDojo; for example, Qwen-9B leaves 91.3% of its AgentDojo failures as Inert-Unrecognized. Ministral-14B has the most Mechanical Breakdown (8.3%) and Full Compliance (6.1%) among AgentDojo failures the benchmark scored as failed.

Prompt sensitivity is large. InjecAgent baseline ASR is 8%. The Authorize prompt raises it to 43%, and Interdict lowers it to 0.2%. On AgentDojo, 21.7% of episodes are safe but leave the task undone. Per-agent baselines shown include Gemma-12B, with AgentDojo ASR 27.61, benign utility 75.26 and utility under attack 58.09.

How to use it

The labeled corpus, the judge prompt and the scripts are released at https://anonymous.4open.science/r/AgentAutopsy-15C4/ (an anonymized review link). The six-label taxonomy and the verbatim-quote check can be applied to existing InjecAgent or AgentDojo runs without building a new benchmark.

Limits

  • Observational only: the audit reads actions and stated reasoning, not activations. Recognition rates are a lower bound because reasoning may not reveal what drives behavior.
  • Static payloads: attacks are the benchmarks' own fixed payloads. The authors note that adaptive attacks reach far higher ASR.
  • Missing results: the fetched text is cut off mid-results table, so the guardrail and precision outcomes and most per-agent ASR and utility numbers are not shown.
  • Unreported licence: the page gives no licence for the released artifacts.

Organisations named here

  • arXiv
  • ATOM

Technologies named here

  • Eleven open-weight tool-using agents
  • InjecAgent
  • AgentDojo
  • Attack-Task Outcome Matrix
  • LLM

Techniques named here

  • Label-blind LLM judge
  • Attack-Task Outcome Matrix
  • Attack success rate