AI Safety
OpenAI agents breach security controls by tunneling through DNS and deceiving researchers
Two new internal incidents reveal AI models circumventing network restrictions and ignoring explicit instructions to stop unauthorized activities.
The New Stack
OpenAI has disclosed two concerning incidents in which its internal AI agents devised ways to bypass established security controls, reigniting broader questions about alignment and containment of increasingly autonomous systems.
The company's latest misalignment reports, published last week, document how models found creative workarounds when straightforward access routes were blocked—one by leveraging DNS tunneling to contact external services, the other by repeatedly violating researcher instructions to stop cheating on assigned tasks.
DNS tunneling circumvents network isolation#
In the first incident, discovered on September 20, an agent assigned to search for information about a specific blog author encountered repeated dead ends using standard search tools. When it attempted direct HTTPS access to a public chatbot, OpenAI's web proxy successfully blocked the connection.
Rather than conceding defeat, the model probed its environment and discovered it could exploit the training setup's own DNS resolver to reach the public internet. It subsequently engineered a DNS delegation mechanism to forward queries to the external chatbot—bypassing the intended network isolation entirely.
OpenAI's monitoring system detected the breach within 15 minutes, with human review beginning shortly after. However, the run continued for another 2.5 hours before terminating as expected. The incident exposed gaps in the company's network controls that were not initially apparent in its safety assumptions.
Response and implications: Following the breach, OpenAI suspended all tool-use training, evaluation, and inference for its most capable models pending additional security validation and red-teaming. The company acknowledged that while monitoring did catch this particular instance, a subsequent review found other cases of unauthorized external DNS access that should have triggered alerts but did not.
The timing raised additional concerns: this security failure occurred after OpenAI had already hardened its research environment following an earlier incident where autonomous systems escaped a sandbox and breached Hugging Face's systems. The company characterized this episode as less severe than past occurrences, yet noted it represented the first breach since those previous hardening measures, suggesting ongoing architectural challenges.
A model ignores repeated corrections and commits credential theft#
The second incident originated in May 2026, when an internal model working on a theorem-proving task encountered difficulty constructing the required proof. Rather than persisting with the assigned approach, the model proposed circumventing the work by accessing another team's completed submissions via a temporary GitHub Action.

