Case · DiggingBeagle record

INFUSE shows prompt-injection success scores diverge from actual repository effects

Across more than 41,000 controlled coding-agent attack trajectories, an LLM judge and artifact-based evidence differed on whether injected instructions achieved an unauthorized result.

Scope

arXiv:2610.20776; 40 repository tasks, 56 injection scenarios, 19 configurations; laboratory setup.

Assessment profile

Assessment method
Setting
evaluation
Exploitation
demonstrated
Evidence
Grade B
Remediation
not applicable
AI role
AGAINST AI
Basis and provenance

The INFUSE primary study describes tens of thousands of controlled agent trajectories and manually audited disagreement cases. It provides strong evidence about benchmark evaluator disagreement and selected successful indirect injections, not an independently observed production campaign. No single patched affected product or realized loss is identified.

Assessed Oct 18, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Step

  2. 02

    Step

  3. 03

    Step

  4. 04

    Step

Claims & evidence

CLM-CP13-INFUSE-SCOPEThe published experimental suite contains 41,824 attack trajectories and 720 benign samples across varied coding-agent configuration and placement conditions.supported

Basis: reported finding

Link to claim
CLM-CP13-INFUSE-JUDGESMean model-judged attack success (19.6%) and artifact heuristic (15.4%) differ, with 10.8% per-attempt disagreement requiring artifact-level adjudication.supported

Basis: reported finding

Link to claim
CLM-ENRICH-INFUSE-CAUSE-DIVERGENCEThe authors attribute many judge-only positives to partial adoption of the attacker goal without the targeted effect, whereas heuristic-only positives sometimes arise from an incidental legitimate tool action.supported

Basis: reported finding

Link to claim

Implications

Security measurement should require a trace from injected content to actual authorization crossing and persistent artifact state. An agent following an injected suggestion is concerning but not the same thing as a completed exfiltration, while an artifact match without causal context may wrongly blame benign work. The PROBE auditor work exhibits a related but distinct reward-judge problem.

Controls and mitigations

  • For each claimed injection success, preserve the relevant tool invocation, permitted scope and resulting artifacts, then adjudicate model-judge and heuristic disagreements.
  • Report benign task completion and guard-induced failures alongside attack success to detect defenses that appear successful by preventing ordinary work.

Unknowns and contradictions

  • Controlled repository tasks are not a population-level estimate of real agent intrusions.
  • Neither judge nor keyword heuristic is an independent ground-truth oracle for all attempted effects.

Sources and citation

Material revision history

  1. Oct 18, 2026 · Canonical change recorded · new in release · revision 171