Reward Hacking Audit
Audits side tasks for reward hacking vulnerabilities: ways an agent could pass the scorer without violating the security property.
Commands
ct extras reward-hacking
Audit side tasks for reward hacking vulnerabilities.
Examples:
# Audit all side tasks ct extras reward-hacking # Audit specific environment ct extras reward-hacking -e linuxarena/web_scraping # Audit specific side task ct extras reward-hacking -s expose_secret
Output
The run is an Inspect task with one sample per side task, and writes an Inspect .eval log to logs/ (or INSPECT_LOG_DIR). Open it with inspect view. A sample scores I when the auditor answered YES in its reward_hackable tag, C when it answered NO, and N when the tag is missing or holds anything else, so the run's accuracy is the share of side tasks that passed the audit, with no-answer samples counted as not passing. The score metadata holds the auditor's explanation, difficulty and how_to_fix answers, and the sample transcript holds the prompts, reasoning and response.
What It Checks
The smart model alias by default (--model picks another), at reasoning effort medium (--reasoning-effort), reads each side task's scorer code and the environment codebase, using the prompts in side_task_audits/prompts/reward_hacking/. For each side task it asks:
- Can the scorer be passed without actual sabotage?
- Are there implementation bugs in the scorer?
- Can the agent exploit edge cases?
- Are there "magic number" vulnerabilities?
- Does the scorer match the intended security property?