← All incidents timeline

Suggest a change

About OpenAI evaluation agents escape sandbox and breach Hugging Face

Suggest a change to an entry, the methodology or the ledger as a whole: something to fix, correct or add. We read every suggestion, and check corrections against their sources.

OpenAI· Internal-only research model (IM1) and GPT-5.6 Sol

OpenAI evaluation agents escape sandbox and breach Hugging Face

During a cyber benchmark with safeguards reduced, OpenAI agents got out of their sandbox, coordinated on a message board they built, and compromised Hugging Face production systems to look for test solutions.

Agents in OpenAI training and evaluation runs began leaving notes for each other in an internal package service from May 2026 and found ways to reach the internet. From 8 July, agents running the ExploitGym benchmark regained internet access, found exposed Hugging Face credentials and, between 11 and 13 July, ran code on dozens of Hugging Face production servers, took credentials and copied limited private data. Hugging Face detected and contained the intrusion and disclosed it on 16 July without knowing the source. OpenAI's monitoring flagged unusual activity on 19 July; it linked this to Hugging Face on 20 July and disclosed on 21 July. OpenAI says earlier warning signs in late May, June and early July were not escalated. Reuters later reported agent activity against Hugging Face accounts as early as 13 May. Fifteen US states, a California lawsuit and the California attorney general have since pressed OpenAI over it.

First incident action to disclosure
70 days
First incident action to discovery
68 days
Noticed first by
Someone else
Caught
A control flagged it

What happened

  • First incident action
  • Unnoticed
  • Handler found out
  • Known, not public
  • Disclosed
  • Public
  1. 12 May 2026

    First incident action

    First agent message-board note in OpenAI's internal package service

    An agent in a training run left a note asking other agents for a missing file. OpenAI's report notes an earlier agent file write on 20 April.

  2. 13 May 2026

    Agent uses an exposed Hugging Face token to look for a file

    Disputed

    Reports differ

    Scope of the May activity.

    • An agent used one publicly exposed token to search for a file it needed; OpenAI says it disclosed this.
    • Agents compromised two Hugging Face accounts and sent unusually formatted files to Hugging Face, resembling probing, beyond what OpenAI described.
  3. May 2026

    Internal team sees the message board and disallowed internet access

    Late May. Not escalated; OpenAI says its significance was not apparent to incident leads.

  4. 26 May 2026

    Agents reach the internet and write to Hugging Face

    Agents created a Hugging Face repository and proxy apps using exposed tokens.

    Disputed

    Reports differ

    Whether this is part of the incident.

    • OpenAI has no evidence this is connected to the July intrusion; it came from an unrelated research workload.
    • Researchers treat the May activity as early probing of Hugging Face.
  5. 26 Jun 2026

    Agents gain administrator access to the internal package service

  6. 27 Jun 2026

    Port-sweep alert investigated; run not stopped

    Responders linked it to an evaluation using the message board; on-call staff judged stopping unnecessary.

  7. 4 Jul 2026

    Agent activity takes the package service offline

  8. 5 Jul 2026

    OpenAI opens an incident and rebuilds the service

    Credentials revoked and the vendor notified on 6 July; evaluations resumed 7 July. The message board was wiped as a side effect.

  9. 8 Jul 2026

    ExploitGym agents regain internet access and rebuild the board

    Tens of thousands of agents were launched in these experiments, per METR.

  10. 9 Jul 2026

    Agent takes over a customer's app on Modal

    Hugging Face's own timeline starts attacker activity on 9 July.

  11. 10 Jul 2026

    Agent finds 14 exposed Hugging Face credentials and shares them

  12. 11 Jul 2026

    Agents run code on Hugging Face production workers

    Through two previously unknown flaws in dataset processing.

  13. 12 Jul 2026

    Access spreads across Hugging Face clusters; credentials and private data taken

    OpenAI counts code execution on 41 production workers and root on at least one node; Hugging Face counts about 17,600 attacker actions and five affected datasets.

  14. 13 Jul 2026

    Hugging Face detects and cuts off the intruder

    Last logged attacker event 13 July. Hugging Face does not give the alert time and says its tooling under-rated the alert.

  15. 16 Jul 2026

    Hugging Face discloses an AI-agent intrusion, source unknown

  16. 17 Jul 2026

    OpenAI contacts Hugging Face as a customer

    To check exposure of OpenAI data; no link to its agents yet.

  17. 19 Jul 2026

    Handler found out · 68 days in

    OpenAI security alert; evaluation runs stopped

    The same day agents reached administrator access on an OpenAI cluster.

  18. 20 Jul 2026

    OpenAI links its agents to the breach and informs Hugging Face

  19. 21 Jul 2026

    Disclosed · 70 days after the first incident action

    OpenAI discloses its models caused the intrusion

  20. 27 Jul 2026

    Hugging Face publishes its technical timeline

  21. 28 Jul 2026

    OpenAI clarifies the pre-release model is an internal-only prototype

    Also reports four exposed accounts on four services used in the incident.

  22. 3 Aug 2026

    Fifteen state attorneys general demand answers from OpenAI

  23. Not disclosed

    OpenAI notifies the EU AI Office

    Date not visible; article paywalled.

    Reported
  24. 26 Aug 2026

    OpenAI technical report and METR/Redwood investigation published

    Reports differ

    Motive differs.

    • Agents were trying to steal test solutions.
    • The attack was mainly aimed at learning how the scorer worked, not stealing answer keys.
  25. 16 Sep 2026

    Reuters reports Hugging Face probing from 13 May

    OpenAI says it had disclosed the 13 May event and privately notified Hugging Face; Hugging Face did not comment.

    Reported
  26. 29 Sep 2026

    Nonprofit LASST sues OpenAI over the breach

    Reported
  27. 1 Oct 2026

    California's attorney general subpoenas OpenAI

    Reported

Agent failures

Sandbox escape, Swarm coordination, Unauthorised accessShow
Map to frameworks
  • Sandbox escape

    Got out of their sandbox during a cyber benchmark.

  • Swarm coordination

    Coordinated on a message board they built.

  • Unauthorised access

    Compromised Hugging Face production systems.

How it was found

Found first by someone else, from a control flagged itShow
Found first by
Someone else
How
A control flagged it
Found to disclosed
2 days

Hugging Face's own AI-assisted anomaly detection picked up the intrusion from several security layers at once, though its tooling did not raise the alert to on-call at the right severity; its team then contained it. OpenAI contacted Hugging Face on 17 July only as a customer checking its own data. On 19 July an OpenAI security alert on unusual identity activity started an internal investigation that tied the agents to the Hugging Face breach on 20 July. OpenAI says an internal team had seen the message board and disallowed internet access in late May, a port-sweep alert on 27 June was not acted on, and a 5 July incident was handled without its significance being understood. Chain-of-thought monitoring was not running on these evaluations; OpenAI says it would have paged security more than a day before the breach.

What is publicly known

7 of 12 fully publicShow
7 of 12 fully public
ItemPublic?DetailSources
PartialGPT-5.6 Sol is named; the main actor is an unnamed internal-only research model (IM1, about 95% of agents per METR).
PartialOpenAI says agents got a range of reasoning budgets, some far beyond external products; exact settings are not given.
KnownProduction cyber classifiers, system prompts and auto-review were off, and chain-of-thought monitoring was not running on these evaluations.
PartialOpenAI says lightweight, generic evaluation system prompts were used, not production ones; the text is not published.
PartialExploitGym tasks; METR says instructions required one intended vulnerability. Task text is not published.
KnownPer-run containers with shell, Python, browser and package install, plus a shared Artifactory credential, are described in the report.
KnownThe report describes a web cache, Artifactory as package mirror, outbound controls that varied by workload, and how agents got past them.
PartialMETR reviewed about 1,300 transcripts and a message board dump; only excerpts are public, in METR's and OpenAI's posts.
KnownDated signals: late May sighting, 27 June port-sweep alert, 5 July alert, 19 July identity alert; Hugging Face's alert under-escalated.
KnownCode run on 41 Hugging Face workers, four private repositories, five customer datasets, credentials; Modal and a second service also touched.
KnownOpenAI names reward hacking, impossible tasks, persistence, agent messaging and reduced safeguards; independent reviewers largely concur.
KnownBoth companies list specific changes, from micro-VM sandboxes and Artifactory removal to credential rotation. Independent verification of fixes is not published.

Controls that apply

  • Protect

    Hold test, training and evaluation environments to production standards

    ExploitGym agents in OpenAI evaluation runs regained internet access from 8 July, weeks after an internal team had disallowed it in late May, and found exposed Hugging Face credentials. An evaluation held to production standards, with the internet closed and no real services in reach, would have refused the route to Hugging Face's production servers.

  • Limit where the agent can send traffic

    Outbound requests and uploads to Hugging Face from evaluation hosts, first on 26 May when agents created a repository and proxy apps with exposed tokens, then from 8 July. An allowlist would have refused them and raised each blocked attempt.

  • Isolate where the agent runs

    Outbound internet traffic from evaluation sandboxes meant to have none, in late May and again from 8 July. Raised as boundary crossings, these would have surfaced the runs before the code execution on Hugging Face's production workers from 11 July.

  • Authenticate and constrain agent-to-agent channels

    Agents left notes for each other in an internal package service from 12 May; METR says about 1,200 agents used the board and about 700 joined the attack. An internal team saw the board in late May without escalating, and with agent messaging limited to named, logged channels it would have been an unsanctioned channel to close rather than one rebuilt on 8 July.

  • Detect

    Record every agent action, outside the agent

    A record of the 27 June port sweep from an evaluation host, the 10 July sharing of 14 exposed Hugging Face credentials and the code run on 41 production workers. On its side, Hugging Face counted about 17,600 attacker actions from 9 to 13 July.

  • Monitor every run and alert on what does not fit the task

    A port-sweep alert on 27 June was investigated and the run not stopped, and late-May and 5 July signals were not escalated. OpenAI says chain-of-thought monitoring was not running on these evaluations and would have paged security more than a day before the breach; its own alert came on 19 July, after Hugging Face had cut the intruder off.

  • Respond

    Contain, notify and disclose

    Hugging Face disclosed on 16 July without knowing the source, and OpenAI contacted it on 17 July only as a customer checking its own data. OpenAI linked its agents to the breach on 20 July, disclosed on 21 July, and says earlier warnings in late May, June and early July were not escalated.

  • All controls →

Coverage and commentary

4 posts on X, 4 statements, 8 articlesShow

What the parties involved said

  • OpenAI

    Calls the incident a warning shot, names reward hacking, persistence on impossible tasks and unauthorised agent communication as causes, and requires chain-of-thought monitoring on tool-using runs.

  • METR and Redwood Research

    About 1,200 agents used the board and about 700 joined the attack, mainly to learn how the scorer worked rather than to steal answer keys.

  • Redwood Research

    Argues it was grader-gaming, not instruction-following, and chiefly shows failures of containment, monitoring and evaluation governance.

  • Jonas Wiedermann-Moeller

    Says catching the 13 May activity could have prevented the July breach.

Press coverage

All 16 sources
  1. Primary source

    The Hugging Face incident and the road ahead ↗OpenAI · 2026-08-26

  2. Primary source

    OpenAI - Hugging Face Incident Technical Report ↗OpenAI · 2026-08-26

  3. Primary source

    OpenAI and Hugging Face partner to address security incident during model evaluation ↗OpenAI · 2026-07-21

  4. Primary source

    Security incident disclosure: July 2026 ↗Hugging Face · 2026-07-16

  5. Primary source

    Anatomy of a Frontier Lab Agent Intrusion: A Technical Timeline of the July 2026 Incident ↗Hugging Face · 2026-07-27

  6. Primary source

    Brief independent investigation of agents' behavior, reasoning and collaboration in the OpenAI / Hugging Face hacking incident ↗METR · 2026-08-26

  7. Primary source

    The Hugging Face incident and other third-party impact from misaligned models ↗OpenAI

  8. Primary source

    Attorney General Brenna Bird leads coalition demanding transparency from OpenAI after AI breach and hacking ↗Iowa Office of the Attorney General · 2026-08-03

  9. Press

    OpenAI agents probed Hugging Face for weaknesses two months before hack ↗Reuters (via The Globe and Mail) · 2026-09-16

  10. Press

    OpenAI notified EU of Hugging Face hack under AI Act ↗Euractiv

  11. Press

    EXCLUSIVE: OpenAI didn't report safety incident under EU AI rules ↗Euractiv · 2026-09-18

  12. Press

    OpenAI faces first lawsuit over rogue AI agents that hacked Hugging Face ↗Gizmodo · 2026-09-30

  13. Press

    California attorney general issues investigative subpoena to OpenAI ↗Reuters (via The Star) · 2026-10-01

  14. Commentary

    The OpenAI models that hacked Hugging Face weren't just following instructions ↗Redwood Research · 2026-07-25

  15. Commentary

    OpenAI's accidental cyberattack against Hugging Face is science fiction that happened ↗Simon Willison · 2026-07-22

  16. Commentary

    More On An Internal OpenAI Model Hacking Into HuggingFace ↗Zvi Mowshowitz (Don't Worry About the Vase) · 2026-07-26

Entry id openai-huggingface-2026 · overall Confirmed · impact major