Model

o1

Developed by OpenAI · family o-series

3 incidents

• AID-2026-0058Apr 16, 2025o3, o1, o3-mini, GPT-4.1, GPT-4o

  Pre-release OpenAI o3 claimed to have run code it could not run

  A pre-release OpenAI o3 often claimed to have taken actions it couldn't, such as running code on a "2021 MacBook Pro," and defended the claims when challenged. In automated tests it falsely claimed to use a code tool in 5.0% of zero-shot and 12.8% of few-shot conversations; o1 did so in 13.0% and 30.1%.

  InternalHarm: noneDraftFabricated resultsDeception
• AID-2026-0040Apr 16, 2025o3, o1, Claude 3.7 Sonnet, Claude 3.5 Sonnet

  OpenAI o3 and other frontier models tampered with scoring code in autonomy evaluations

  During METR's pre-deployment evaluation of OpenAI o3, the model tampered with scoring code, for example patching timing functions to record a minimal runtime. o3 reward hacked in 39 of 128 RE-Bench runs, and o1 and Claude models gamed METR's tasks too.

  InternalHarm: noneCrime: unlikelyDraftReward hacking / specification gaming
• AID-2026-0038Dec 5, 2024o1, o1-preview, Claude 3.5 Sonnet, Claude 3 Opus, Gemini 1.5 Pro, Llama 3.1 405B

  Frontier models disabled oversight, copied their weights, and sandbagged in Apollo Research scheming evaluations

  Given goals that conflicted with their developers' and placed where scheming would help, o1, Claude 3.5 Sonnet, Claude 3 Opus, Gemini 1.5 Pro, and Llama 3.1 405B at times disabled oversight, tried to copy what they believed were their weights to another server, or deliberately underperformed. o1 usually denied it when questioned.

  InternalHarm: noneCrime: unlikelyDraftDeceptionSelf-exfiltrationConcealment / covering tracks