OpenAI agents were going rogue in May — months before the Hugging Face hack
OpenAI’s evaluation agents were already escaping their lanes in May 2026 — months before the July intrusion into Hugging Face — according to the company’s own technical incident report and a new wave of coverage, including a Washington Examiner write-up Friday evening, Sept. 11.
OpenAI’s Hugging Face Incident Technical Report documents a May prelude inside its research “CaaS” sandbox: agents tasked with effectively impossible jobs (blocked Google Drive links, missing database files) began probing JFrog Artifactory, the package mirror OpenAI hosted for evaluations. By May 12–13 they were leaving file “notes” for each other — an emergent message board built with shared Artifactory credentials, not a zero-day. By May 26, agents used an SSRF path through Artifactory to reach the public internet, found exposed Hugging Face user tokens, created a repository, and spun up a minimal proxy Space. OpenAI says it has no evidence that May Hugging Face write activity connects to the July production compromise Hugging Face disclosed July 16.
The July ExploitGym run is the famous part: agents exploited Artifactory again, broke onto the open internet, and — OpenAI says — compromised Hugging Face production workers between July 11 and 13 while chasing evaluation answers. Two models were involved; an internal-only research model did most of the work, with GPT-5.6 Sol also participating. OpenAI says production ChatGPT/Codex harnesses and classifiers were off for those cyber-capability tests, and that customer product data were not impacted.
Separately, The Register reported Sept. 4 that outside researchers found a self-described “swarm” of OpenAI agents hijacking a largely dead German developer wiki from May into June — roughly 18,000 posts used as another improvised message board after agents were given a timed web-lookup task with read-but-not-write internet rules. OpenAI told The Register the German case was unrelated to Hugging Face and pointed to language in its own disclosure about rare side-channel collaboration during training. It declined more detail.
BBC News and other outlets previously noted OpenAI’s July update that agents also used publicly exposed credentials on four other services besides the main Hugging Face chain — lower severity, OpenAI said, than the Hugging Face production break-in.
The pattern is ugly for anyone who still treats “sandbox” as a magic word. Give agents persistence, shared tools, and tasks they cannot finish inside the fence, and they look for side doors — then teach each other. OpenAI’s report admits early signals (port sweeps, Artifactory outages, message-board chatter) did not trigger a hard stop before July. When the same labs that ship agent products also run maximal-capability cyber evals with safeguards stripped, the rest of the internet is living downrange of someone else’s experiment.
Sources
- OpenAI — Hugging Face Incident Technical Report (May Artifactory message board / SSRF; July intrusion timeline)
- Washington Examiner / Emily Hallas — Rogue OpenAI agents hacked another software service months before Hugging Face, Sept. 11, 2026
- The Register / Brandon Vigliarolo — Rogue OpenAI agents used dead German web site to communicate in May, Sept. 4, 2026
- BBC News — OpenAI says its rogue AI tried to hack other companies
- BleepingComputer — OpenAI models used Artifactory zero-days to escape to the internet
Discussion