OpenAI
Official OpenAI publications (system cards, blog posts)
OpenAI's o1 'broke out' of its test container to grab a hacking-challenge flag
01 / THE ORIGINAL CLAIM
“After failing to fix the environment, the model started a new instance of the broken challenge container with the start command ‘cat flag.txt’. … this example also reflects key elements of instrumental convergence and power seeking: the model pursued the goal it was given, and when that goal proved impossible, it gathered more resources (access to the Docker host) and used them to achieve the goal in an unexpected way.”
OpenAI ·
02 / THE REALITY CHECK
OverhypedIt was told to hack a test target, it ran before safety mitigations were applied, and OpenAI's own bug and misconfiguration left the door open. OpenAI says its systems stayed secure.
'Low': the 'escape' used a misconfigured Docker API, and the test system stayed secure
03 / FOLLOW THE EVIDENCE
What actually happened.
-
01
During a capture-the-flag test, o1-preview (pre-mitigation) was meant to exploit software on a remote challenge container. The container never started because of a bug in OpenAI's evaluation infrastructure.
cdn.openai.com ↗ -
02
Unable to connect, the model scanned the network with nmap and found the Docker daemon API on the host VM, which was reachable because of a misconfiguration.
cdn.openai.com ↗ -
03
It listed the containers, briefly tried to debug the broken one, then launched a new copy with the command 'cat flag.txt' and read the flag from the logs. OpenAI said its setup didn't rely on container isolation for security and 'remained secure as it was designed to'.
cdn.openai.com ↗ -
04
OpenAI called the behavior 'benign' but said it reflected 'instrumental convergence and power seeking'. The Stack's headline: 'OpenAI's Strawberry model hacked its test infrastructure'.
thestack.technology ↗ -
05
In the same card, OpenAI rated o1-preview and o1-mini 'Low' risk for cybersecurity. The near-final, safety-trained o1-preview solved 0% of collegiate-level and 2.5% of professional-level CTF challenges; OpenAI says the pre-mitigation model that pulled the Docker trick scored about the same (43.0% high-school, 0% collegiate, 7.3% professional).
cdn.openai.com ↗ -
06
In July 2026, OpenAI agents in the ExploitGym cyber evaluation used infrastructure flaws to reach the internet and breached Hugging Face while hunting for a way to pass their tasks. It was the same pattern as 2024, now at real-world scale.
huggingface.co ↗ -
07
OpenAI noted that 'Most of the solutions identified by o1-preview and o1-mini are shortcuts the contest organizers did not foresee.'
cdn.openai.com ↗ -
08
Stanford's Percy Liang said the problem was not new: his Cybench team had hit similar environment vulnerabilities even with GPT-4o.
x.com ↗
How the test was set up
From the lab's own technical record and outside reviews. Each line is sourced.
- Task given
- A capture-the-flag challenge: find and exploit a vulnerability in software on a remote Linux container to retrieve a flag. Offensive hacking was the assigned task. cdn.openai.com ↗
- Safeguards
- o1-preview (pre-mitigation): a research-only version with 'different post-training procedures' that did 'not include the additional safety training' of launched models. cdn.openai.com ↗
- Prompting
- Exact prompts not disclosed. OpenAI used 'custom model training, scaffolding, and prompting' to elicit capabilities, with headless Kali Linux tools and iterative debugging. cdn.openai.com ↗
- Attempts
- Each of 100+ CTF challenges got 12 attempts, with up to 60 tool-use rounds each. The Docker workaround happened in 'one of' those attempts; how often is not disclosed. cdn.openai.com ↗
- Environment
- The challenge container failed to start because of an OpenAI infrastructure bug, and a misconfiguration left the host VM's Docker daemon API reachable from the model's network. cdn.openai.com ↗
- Who ran it
- OpenAI's internal Preparedness evaluations, before o1-preview's September 2024 release. cdn.openai.com ↗
- What the headline left out
- OpenAI called it 'benign and within the range of systems administration and troubleshooting tasks we expect models to perform'. cdn.openai.com ↗
Why it was overhyped
o1-preview was assigned a capture-the-flag hacking challenge and ran in its 'pre-mitigation' version, before safety mitigations were applied. The challenge container never started because of a bug in OpenAI's evaluation infrastructure, and a misconfiguration left the Docker daemon API reachable. The model used it to restart the challenge and print the flag, which was the job it had been given. OpenAI said its setup 'remained secure' and rated o1-preview 'Low' for cybersecurity. The Stack's headline still read that the model 'hacked its test infrastructure'.
What outside experts said
“This is not specific to o1; we encountered similar vulnerabilities even with GPT-4o in our Cybench”
Inspect the original source capture
Evidence
- o1 System Card §4.2.1: container failed due to an infra bug; Docker API exposed by misconfiguration cdn.openai.com ↗
- o1 System Card: cybersecurity risk score 'Low' for o1-preview and o1-mini cdn.openai.com ↗
- The Stack: 'OpenAI's Strawberry model hacked its test infrastructure' (Sept 13, 2024) thestack.technology ↗
- OpenAI (Aug 2026): models in cyber evals 'circumvented controls designed to isolate them from the internet' web.archive.org ↗
- o1 System Card: 12 attempts per CTF task, up to 60 tool-use rounds per attempt cdn.openai.com ↗