Skip to content
Sprint projectMar 22, 2026Tallinn, Estonia

In-context Trajectory Poisoning: Black-Box Natural Language Attacks on LLM Agent Monitors

Hilary Torn

Submitted to AI Control Hackathon 2026. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: In-context Trajectory Poisoning: Black-Box Natural Language Attacks on LLM Agent Monitors

Code (opens in new tab)
Share

LLM-based monitors such as AlignmentCheck (Chennabasappa et al., 2025) are increasingly deployed to detect when AI agents have been compromised by indirect prompt injection attacks. Recent work by Isbarov & Kantarcioglu (2026) demonstrated that these monitors can be bypassed using gradient-optimized adversarial strings, but their approach requires white-box access to model weights and significant GPU resources. We adapt the PAIR algorithm (Chao et al., 2023), originally designed for jailbreaking chat models, to iteratively search for natural language strings that, when embedded in an agent's execution trace, cause the monitor to classify malicious actions as safe. On the AgentDojo benchmark, our per-task attack achieves 12.5% overall ASR aggregated across tasks against Qwen2.5-7B (p=0.028), up from a 3.1% baseline. Attack success varies significantly by action type: actions semantically similar to legitimate behavior (visiting URLs, sending links) are substantially easier to disguise than data exfiltration. Strings optimized against Qwen2.5-7B transfer to other monitors, reaching 16.7% on Llama-3-8B-Lite (p=0.003) and 34.4% on DeepSeek-V3 (p<0.001), with individual tasks reaching up to 73.7%. Notably, Llama-3-8B-Lite and Qwen2.5-7B share identical baseline vulnerability (3.1%), yet Llama proved substantially more susceptible to natural language priming. Our results demonstrate that natural language trajectory poisoning poses a realistic, low-resource threat to monitoring-based defenses.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. This paper explores how task-specific and generic "justifications" can reduce monitor performance on malicious actions.

    The research approach to identify those is sound: generating, evaluating, and refining candidates with a model stronger than the monitor. Evaluating the best candidates shows that previously caught actions are allowed by the monitor, given additional reasoning. A generic (task-agnostic) justification reduces monitor performance across all tasks.

    I spot-checked the repo and the justifications don't seem "overfitted" to the tasks at hand, but I'd have liked to have seen details on that in the paper. The results on a held-out test set for the generic justification would also have been interesting.

    All in all, this is a safety-relevant approach: in a real setting, an attacker could prepare generic justifications with this approach beforehand or generate specific ones once it has identified which malicious commands to run in the target environment.

    What's unclear from the paper is the impact of iterating the justification against the (or a) monitor over taking an uninformed justification by the strong model. I'd have liked to have seen experiments on that.

    Read full reviewShow less

Cite this project

@misc{torn2026incontext,
  title = {{In-context Trajectory Poisoning: Black-Box Natural Language Attacks on LLM Agent Monitors}},
  author = {Hilary Torn},
  year = {2026},
  month = mar,
  note = {Submitted to AI Control Hackathon 2026, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/incontext-trajectory-poisoning-blackbox-natural-language-attacks-on-llm-agent-monitors-d3gz}},
  url = {https://apartresearch.com/sprints/projects/incontext-trajectory-poisoning-blackbox-natural-language-attacks-on-llm-agent-monitors-d3gz}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026