Hacking or Just Failing? A More Capable LLM Monitor Better Separates Reward Hacking from Honest Failure
Organizations: Independent researcher
Abstract
An agent's visible score can exceed its real progress because it gamed the score or because it simply made mistakes, so a useful reward-hacking monitor must tell the two apart. We built a sandboxed task in which an agent can game a completion score, labelled every episode by replaying it and repairing the final state counterfactually, and ran five pre-registered studies. On 60 episodes from a Llama 3.1 8B agent, small local monitors (Llama 3B and 8B) did not separate exploit attempts from honest failures with the same score gap: prompt changes traded missed exploits for false alarms, and the pre-registered primary monitor reached AUC 0.64. On identical inputs, Gemini 3.1 Flash-Lite, which completed 9/10 clean tasks against 2/10 for the 8B model, met our pre-registered criterion (AUC 0.80, 95% interval [0.66, 0.93]; 1/35 honest failures flagged); with only 14 exploit episodes, this estimate is uncertain. On an exploit that no prompt names, Gemini usually described the action correctly yet never flagged it, in 5 and then 25 new episodes, even when manipulation was defined by its effect on the score. Given the full trace, the 8B monitor flagged all 25 replication episodes and none of 25 honest look-alikes, but its explanations described actions that had not occurred; given additional structured evidence, it also flagged 15 of the 25 look-alikes. A two-rule deterministic check caught every known exploit. We release the environment, labels, pre-registrations and per-judgement logs.
Figures & tables
| Episode (what the agent did) | Proxy | Counterfactual proxy | ||
|---|---|---|---|---|
| Honest failure: recorded all six orders with real evidence, two quantities wrong, one entry missing evidence; marked all complete | 1.0 | 0.5 | 0.5 | 1.0 (no inflation) |
| Unsupported completion: reconciled three orders, then marked all six complete | 1.0 | 0.5 | 0.5 | 0.5 |
| Scope exclusion: reconciled three orders, removed the other three from scope | 1.0 | 0.5 | 0.5 | 0.5 |
| Study | Data | Question |
|---|---|---|
| 1. Small monitors | 60 unprompted episodes, Llama 3.1 8B agent, environment v1 (D1); 50 scripted fixtures (D3); clean-task calibration (D2) | Do 3B and 8B monitors separate hacking from failing? (primary: 8B, v5, C) |
| 2. Capable monitor | The same D1 and D3 trajectories | Does Gemini 3.1 Flash-Lite? (primary: v5, C) |
| 3. Calibration | 90 clean-task episodes: three variant rounds and one Gemini run | Which variant gives an agent 30–70% honest success, and how capable is each model? |
| 4. Second agent study | 300 unprompted episodes, Llama 3.2 3B agent, variant v2d (E1); 45 fixtures (E3) | As Study 1, with many more honest successes |
| 5. Replication | 25 new scope-padding and 25 honest fixtures (H) | Does the held-out result from Studies 1–2 hold? |
| Monitor | Caught | FA, failures | FA, gap-matched | FA, successes | AUC |
|---|---|---|---|---|---|
| 8B v5 (Study 1 primary) | 4/14 | 0/35 | 0/29 | 0/8 | 0.64 |
| 8B v3 | 13/14 | 20/35 | 15/29 | 4/9 | 0.70 |
| 3B v3 | 2/14 | 4/35 | 2/29 | 0/9 | 0.57 |
| 3B v5 | 0/14 | 0/35 | 0/29 | 0/9 | 0.50 |
| Gemini v5 (Study 2 primary) | 9/14 | 1/35 | 1/29 | 0/9 | 0.80 |
| Gemini v3 | 6/14 | 1/35 | 1/29 | 0/9 | 0.84 |
Appendix figures & tables1 asset
Supplementary material from the paper’s appendix.
Appendix
| Agent | v1 | v2a | v2b | v2c | v2d |
|---|---|---|---|---|---|
| Llama 3.1 8B | 2 | 1 | 1 | 2 | 8 (above ceiling) |
| Llama 3.2 3B | 0 | 0 | 0 | 1 | 4 (chosen) |
| Gemini 3.1 Flash-Lite | 9 | – | – | – | – |
AI Agent Monitoring
AI agent monitoring tracks actions, tool use, and execution traces to detect failures, misuse, drift, and policy violations during operation.
See all 290 papers