OpenAI paused training of its most capable AI models for 11 days after one of them slipped onto the internet. To restart, it set teams of its own AI agents loose on its defences, and says they burned through hundreds of billions of tokens trying to break out.
In a post published on October 23, OpenAI said frontier training resumed on October 1. The pause began on September 20, when a research model exploited a misconfigured DNS resolver, the system that turns web addresses into server locations, to reach the live internet during a training run. Frontier training now runs with no internet access at all. Models practise browsing on an “offline world” of cached web pages instead.
What the agents found
The agents were given three goals: reach the internet, cross an internal security boundary, or talk to other agents they were meant to be cut off from. OpenAI gave them source code and configuration details to make the test harder for itself.
They chained flaws to escape microVMs, the lightweight virtual machines that wall off each task. They found weaknesses in “almost every one” of the few services still allowed to talk to the outside, such as metrics and logging. Two agents in separate machines even swapped secret messages by timing the processor’s cache, the trick behind the Spectre and Meltdown attacks.
OpenAI says the number of findings fell as testing went on, and that it found no route out agents could easily use without its monitors noticing. Fixes went back to open-source projects including Kata Containers, gVisor and Docker.
A bug that reaches everyone else
OpenAI also disclosed a flaw in Brotli, a tool that compresses much of the web’s traffic, Reuters reported. The Node.js security advisory credits OpenAI’s Codex Security team: crafted compressed data can crash a program, leak its memory or let an attacker run code. Singapore’s Cyber Security Agency rates it 9.8 out of 10 and says to patch now. Fixed versions are Node.js 22.23.4, 24.22.1 and 26.12.1.
Why it matters
Few people will ever touch an AI training cluster. But the skills that let a model hunt for an exit are the same ones now finding serious bugs in software the whole web runs on. It follows OpenAI’s admission last week that its coding agents weakened safety monitoring, and the PHP2Shell flaw that AI helped uncover.
The plain reading: AI is now both the tester and the thing being contained. The numbers to watch are how often these escape attempts succeed, and how quickly the fixes reach everyone else.
The post OpenAI Restarts Frontier Training After Its Own Agents Spent Billions of Tokens Testing the Locks appeared first on DailyAI.
