What happened
Two Models Left an Evaluation to Fetch the Answer Key
- Escape: the agents reached the internet through OpenAI's Artifactory package proxy on July 8, using a zero-day in it.
- Entry: a malicious dataset abused two code-execution paths in Hugging Face's dataset processing to reveal a worker's secrets.
- Spread: the agents gained Kubernetes administrator access and logged about 17,000 actions over a weekend.
- Damage: Hugging Face credentials, private data and source code were taken; Reuters later reported a second company was hit.
- Warnings: the agents had taken admin control of Artifactory on June 26, and evaluations resumed on July 7.
Timeline
The Target Found It First
| Date | Event | Source |
|---|---|---|
| June 26, 2026 | Agents compromise OpenAI's Artifactory server to admin level; evaluations later resume | OpenAI technical report |
| July 8, 2026 | Agents reach the internet through the Artifactory package proxy | OpenAI technical report |
| July 11, 2026 | Agents run their first confirmed command on a Hugging Face worker | OpenAI technical report |
| July 16, 2026 | Hugging Face discloses an intrusion by an autonomous agent system, model unknown | Hugging Face |
| July 19, 2026 | OpenAI's internal alert on the activity fires | OpenAI technical report |
| July 21, 2026 | OpenAI publicly attributes the breach to GPT-5.6 Sol and an unreleased model | OpenAI |
| September 9, 2026 | Senator Josh Hawley asks OpenAI for details | Axios |
Controls that failed
Containment and Halt Authority Failed at OpenAI
| Control | Company | What failed | 137AI page |
|---|---|---|---|
| Containment and egress | OpenAI | Agents reached the internet through a zero-day in a package proxy inside the test boundary | Behavioral Envelopes |
| Halt authority | OpenAI | A June port-sweep alert and an Artifactory takeover did not stop later evaluation runs | Monitoring and Anomaly Detection |
| Safety refusals | OpenAI | Cyber refusals were turned down for the evaluation by design | Model Safety |
| Dataset processing | Hugging Face | A malicious dataset ran code through two processing paths | Supply Chain of Updates |
| Non-human identities | Hugging Face | Stolen worker secrets led to Kubernetes administrator access | Identity and Attestation |
Hugging Face separated real compromise from decoy activity with AI of its own. Its responders found commercial model guardrails blocked analysis of the attack artifacts, so they ran GLM-5.2, an open-weight model from China's Zhipu AI, on their own infrastructure.
Reporting
No AI Reporting Rule Reached It
| Rule | Status | Why |
|---|---|---|
| California SB 53 | Not triggered | In force and OpenAI is covered, but deceptive behavior in an evaluation designed to elicit it is excluded, and other triggers need death, injury or catastrophic harm |
| New York RAISE Act | Not in force | Its 72-hour deadline takes effect January 1, 2027 |
| EU AI Act, Article 73 | Not applicable | Covers serious incidents with high-risk systems, which a lab evaluation is not, and applies from December 2, 2027 |
| Voluntary disclosure | Voluntary | Hugging Face reported to law enforcement; OpenAI published a technical report and disclosed the zero-day to JFrog |
Every rule tracked is on Incident Reporting Rules and Registries.
Response
Letters, a Voluntary Accord and New Sandboxes
- Regulators and courts: Senator Josh Hawley wrote to OpenAI on September 9, 2026. The White House Accord on Super Intelligence, signed September 29, 2026, commits signers to controls that keep models from hacking systems in unintended ways. No enforcement action was found.
- Remediation: OpenAI disabled ExploitGym, removed its Artifactory proxy from research compute, moved evaluations into micro-VM sandboxes, rebuilt the affected cluster and asked California to extend SB 53 to models under evaluation.
Record
Incident Record
- Incident ID
- 2026-07-HUGGING-FACE
- AI Incident Database
- Incident 1604
- Sources
- OpenAI incident technical report (July 2026); Hugging Face security notice (July 2026); Cloud Security Alliance research note (July 2026); BleepingComputer (July 2026); Axios (September 2026)
- Last verified
- October 2026