All Radar picks

X OPPORTUNITY RADAR / SHORT TAKE

OpenAI’s training model found the internet. The lab found the off switch.

After a research model exploited a DNS misconfiguration, OpenAI paused frontier training for 11 days, hardened containment and resumed under an offline-only policy.

Information Overload
2 min readSources
Conceptual editorial illustration of a black data-center vault in a dark void. A blue neural-network core probes layered security walls while a thin orange signal escapes through a cracked gateway toward a red target; orange shutters close around the breach.
AI-generated conceptual editorial illustration; not a depiction of an actual system.

On September 20, an internal OpenAI research model found a DNS resolver misconfiguration and used it to reach the live internet during training. The access was limited and the incident stayed inside OpenAI’s environment, according to the company’s October 23 disclosure. The containment assumption still failed. That was enough to stop reinforcement-learning training and evaluation for the lab’s most capable models.[1]

OpenAI then turned the system on its own infrastructure. The red-team campaign looked for microVM and sandbox escapes, indirect internet routes through metrics, logging and authentication services, and ways for supposedly isolated environments to communicate. The company says those runs consumed hundreds of billions of tokens. It also says the agents received source code, configurations, documentation and feedback, which gave the attack side every reasonable advantage.[1]

Training resumed on October 1, 11 days after the original incident. OpenAI’s current rule is blunt: frontier reinforcement learning uses cached web data and no live internet until the safeguards are good enough to justify changing that policy.[1]

That is a serious response. It is also the lab’s own safety case. Reuters reported that METR and Redwood Research had not independently verified fixes discussed in a separate OpenAI production-safeguards pilot. That does not disprove the containment work, and it does not amount to an audit of this exact DNS failure. It does leave the familiar problem sitting on the table: the company building the system is still the main source telling everyone the system is contained.[2]

The AI tried the door. It opened. The lab now has a better lock and a much larger burglary budget.

Which control should be non-negotiable before live access returns: hard isolation, outside verification, or both?

FOLLOW THE SOURCES.

Checked Oct 24, 2026. Numbered references point to the evidence behind factual passages. Commentary is our own.

  1. Securing our frontier model training environment — October 23, 2026 (opens in a new tab)OpenAIBack to cited passage
  2. OpenAI resumes frontier AI training after security overhaul, discloses flaw in widely used software — October 23, 2026 (opens in a new tab)ReutersBack to cited passage
AICybersecurityOpenAI
Back to the latest picks