Case · DiggingBeagle record

Screwtape benchmark exposed validity gaps in coding-agent monitor evasions

Only six of seventeen apparent held-out monitor evasions in generated coding-agent transcripts survived human assessment of the attack validity.

Scope

Published controlled research and its described configurations; no inference of unrelated production deployments.

Assessment profile

Assessment method
Setting
evaluation
Exploitation
demonstrated
Evidence
Grade B
AI role
AGAINST AI / WITH AI
Basis and provenance

Redwood primary controlled evaluation reports six human-confirmed plausible transcript attacks out of 17 monitor evasions; actions were edited into histories rather than executed against real target systems.

Assessed Oct 17, 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-2026-SCREWTAPE-MONITOR-EVASION-1The study produced 252 edited candidates from 94 coding-agent traces, of which 17 evaded a held-out monitor but only six passed human validity assessment.supported

Basis: reported finding

Link to claim
CLM-2026-SCREWTAPE-MONITOR-EVASION-2The injected misbehavior was evaluated inside edited execution histories rather than being executed as a real exploit.supported

Basis: reported finding

Link to claim
CLM-2026-SCREWTAPE-VERIFIER-NEGATIVE-CONTROLThe Screwtape paper reports that its transcript-consistency verifier rejected 55 of 63 deliberately inconsistent edits and accepted all 44 unedited controls, showing that passing an automated verifier is not the same as being human-validated.supported

Basis: reported finding

Link to claim

Implications

Security evaluations need two independent witnesses: a detector that observes the proposed activity and an adversarial validity test that establishes the activity actually happened under the stated tool semantics. Monitor-success numbers alone overcount attack outcomes when fabricated histories contain incompatible steps or impossible tool effects.

Controls and mitigations

  • Separate validity of the alleged tool effect from the monitor's classification of the visible transcript.
  • Use held-out action telemetry and human checks for constructed monitor evasions, reporting both candidate and validated counts.

Unknowns and contradictions

  • The attacks were edits of transcripts, not completed exfiltration, malicious deployment, or sabotage.
  • The study does not establish general production monitor escape rates across workloads or model families.
  • Replay in an isolated action-capable environment is required to determine which six scenarios cause real effects.

Sources and citation

Material revision history

  1. Oct 17, 2026 · Published version · first publication · revision 166
  2. Oct 17, 2026 · Canonical change recorded · material revision · revision 168Public fields changed: concepts, narrative