flâneur — a map of the web's best reading

The Reward Hacking Benchmark

kunvarthaman.com · 650 words · saved by 1 readers

Reward hacking makes it really difficult to have the model genuinely improve upon the things you care about, because it's capable enough to find shortcuts around it. Earlier this year (around May), I wanted to characterize the extent of reward hacking in frontier LLMs. The first version of the Reward Hacking Benchmark (RHB-v1) had five code optimization tasks (sorting, regex, compression, matrix multiplication, prime checking) evaluated in a deliberately vulnerable sandbox. Models started with inefficient but correct code and got multiple iterations to improve, with feedback on their performance and ranking in a leaderboard after each attempt. Models didn't interact with the environment directly – instead, they communicated through a structured harness with specific fields for different actions: “bash”, "cot", “code”, etc, and the harness executed on their behalf, in a loop with the model. The real results were about environments. I ran every model through two setups: a permissive sand

The Reward Hacking Benchmark The Reward Hacking Benchmark Published on July 1, 2025 Last updated on October 28, 2025 "Every system is perfectly designed to get the results it gets." Reward hacking makes it really difficult to have the model genuinely improve upon the things you care about, because it's capable enough to find shortcuts around it. Earlier this year (around May), I wanted to characterize the extent of reward hacking in frontier LLMs. The first version of the Reward Hacking Benchmark (RHB-v1) had five code optimization tasks (sorting, regex, compression, matrix multiplication, pri

Explore this link on the map →

related reading