Redwood Research took 94 traces from real coding-agent work and used a separate attacker-generation process to insert plausible-seeming malicious actions into the histories. The hypothetical misbehavior included credential exposure, unauthorized deployments and sabotage. The monitors examined edited transcripts, not verified real-world malicious executions. …
Inspect the ClaimsCase · 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.
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.
Evidence basis: CLM-2026-SCREWTAPE-MONITOR-EVASION-1 · CLM-2026-SCREWTAPE-MONITOR-EVASION-2 · CLM-2026-SCREWTAPE-VERIFIER-NEGATIVE-CONTROL · Screwtape: adversarial edits to coding-agent monitor transcripts
At a glance
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.
Read the implicationsThe 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.
Limits and uncertaintyFull account
Redwood Research took 94 traces from real coding-agent work and used a separate attacker-generation process to insert plausible-seeming malicious actions into the histories. The hypothetical misbehavior included credential exposure, unauthorized deployments and sabotage. The monitors examined edited transcripts, not verified real-world malicious executions.
Across 252 candidate generations, 35 examples passed a local validity test while evading a proxy monitor. Seventeen also evaded a held-out developer monitor, but human reviewers accepted only six as valid attacks. This distinction is central: classifier evasion is not the same as a coherent, executable unauthorized action.
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.
The red-team funnel changes its denominator at least twice: 94 base coding-agent traces produced 252 generations; 35 edited candidate attacks met local conditions, 17 evaded a held-out monitor, and only six survived human attack-validity review. A verifier could be fooled by an impossible action inserted into a plausible-looking transcript, so monitor performance must not be reported as an exploited deployment success rate. Transfer also varied substantially across different proxy monitors. The study's finding is evidence about action-history evaluation design and false confidence under partial observation, not proof that a production credential was taken.
These traces expose a second evidence boundary: the monitor saw plausible edited histories, not completed intrusions. The six human-accepted edits therefore support a conditional monitor-red-team finding; they do not establish that six target systems were attacked. The associated execution-evidence pattern separates a monitor's classification from the validity of the supplied transcript and from independently witnessed host behavior.
Mechanism and trust boundary
- 01
Step
- 02
Step
- 03
Step
- 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
- supportsScrewtape: adversarial edits to coding-agent monitor transcriptsprimary disclosure
Study results, attack-generation funnel and human assessment of 17 held-out candidates
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
- supportsScrewtape: adversarial edits to coding-agent monitor transcriptsprimary disclosure
Study methodology, transcript editing and evaluation setup
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
- supportsScrewtape: adversarial edits to coding-agent monitor transcriptsprimary disclosure
Paper experimental setup and verifier evaluation, 55/63 inconsistent edits and 44/44 untouched controls
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
- Oct 17, 2026 · Published version · first publication · revision 166
- Oct 17, 2026 · Canonical change recorded · material revision · revision 168Public fields changed: concepts, narrative