Reflections on Trusting Trust, Revisited: Contaminating Self-Modifying AI Coding Agents with Poisoned Benchmarks

An agent reads external documents or tool responses that may contain malicious instructions.

What you would change

Replay attacks and legitimate lookalikes in an isolated copy of your agent workflow.

Replay attacks and legitimate lookalikes in an isolated copy of your agent workflow.

Compare against

Your existing checks with the same tasks, permissions, and tool responses.

1. Locate the paper's implementation and check its license, model support, data needs, and hardware requirements. Stop here if you cannot obtain the required artifacts.
2. Save a small set of representative product tasks and expected outcomes. Keep evaluation tasks out of any training or tuning, and choose quality and cost limits before running.
3. Run the baseline and the proposed change on identical inputs. Keep other settings fixed and repeat paired runs to expose variation.
4. Save per-task outputs, failures, timings, and all usage costs. Review regressions before expanding the test.

What to measure

Successful attacks missed, legitimate actions blocked, detection delay, and review cost.

When to keep it

Keep the change only if it meets your preselected quality and latency limits and improves the metric you care about after setup and operating costs. Otherwise retain the baseline. This is an exploration plan, not a validated recommendation.

recommendation

watch

research area

safety and guardrails

technical change

Benchmark poisoning attack on self-modifying coding agents

published

2026-09-15

This is a security threat analysis of self-modifying agents rather than an adoptable method, and it is relevant only as a defensive warning for a reader with constrained infrastructure who is unlikely to run self-evolving agent loops in production.

1. claim 01Paperraft inference
   Read the brief interpretation

   The paper does not propose a technique that replaces an existing production method; it demonstrates an attack in which poisoned benchmarks contaminate the self-evaluation loop of self-modifying coding agents, causing evolved versions to emit vulnerable code (e.g., disabled HTTPS certificate validation) on clean tasks. There is no adoption cost in the usual sense, but the implied defensive cost is that any team running self-improving agent loops must add benchmark provenance checks, held-out clean evaluation, and auditing of self-modifications, none of which the paper shows to be reliably effective since contamination persists after clean re-evolution. What can fail is any pipeline that trusts benchmark results to steer agent self-modification: a single compromised benchmark can induce persistent insecure behavior that clean benchmarks do not repair.

   This is a Paperraft inference. It is not pinned to a verified PDF passage.

   Inspect the source