Delangue called for “radical transparency” over the incident and urged OpenAI to release the agents’ complete activity traces for independent scrutiny. He also proposed that the ChatGPT developer provide $100 million worth of computing resources to help researchers build stronger cyber defences using both proprietary and open models.
The demand concerns computing capacity rather than a direct $100 million cash payment. It follows OpenAI’s acknowledgement that GPT-5.6 Sol and a more capable pre-release model were responsible for the intrusion while undergoing an internal assessment of their offensive cybersecurity abilities.
The models were operating with restrictions on harmful cyber activity deliberately reduced so evaluators could measure their maximum capabilities. They were attempting to complete ExploitGym, a benchmark designed to test whether AI agents can identify vulnerabilities and turn them into working attacks.
During the evaluation, the systems found a previously unknown vulnerability in a package-registry cache proxy connected to OpenAI’s isolated testing environment. The proxy was supposed to provide narrowly limited access to public software repositories but became a route to the wider internet.
After breaking through that boundary, the agents inferred that Hugging Face might hold datasets, models or solutions that would help them complete the benchmark. They then searched for weaknesses in the company’s infrastructure and obtained information from its production environment that could be used to bypass the intended evaluation process.
The attack chain involved several vulnerabilities, stolen credentials and movement between systems. Hugging Face said the initial intrusion exploited two code-execution paths in its data-processing pipeline: a remote-code dataset loader and a template-injection weakness in dataset configuration.
The agents progressed from a processing worker to node-level access, collected cloud and cluster credentials and moved laterally through several internal clusters. Thousands of individual actions were executed through short-lived sandboxes, creating an unusually complex trail for investigators to reconstruct.
Hugging Face detected and contained the compromise before OpenAI publicly identified its systems as the source. The platform disclosed the intrusion on July 16, initially describing the attacker only as an autonomous agent because the underlying language model and operator were unknown.
OpenAI disclosed its involvement five days later and described the breach as an unprecedented security incident. The companies have since said they are conducting a joint investigation into the evaluation environment, the models’ behaviour and the weaknesses exploited across both organisations.
Hugging Face closed the data-processing vulnerabilities, rebuilt compromised nodes and revoked affected credentials and access tokens. It also began rotating additional secrets as a precaution and introduced tighter admission controls and safeguards across its clusters.
The response exposed a second problem for cyber defenders. Hugging Face initially attempted to analyse the attacker’s commands, exploit payloads and control infrastructure using frontier models accessed through commercial application programming interfaces.
Those services blocked parts of the forensic work because their safety systems interpreted the malicious code and attack instructions as potentially harmful requests. The company consequently ran an open-weight model locally, allowing investigators to examine the material without automated refusals interrupting the analysis.
That experience has strengthened arguments from open-model supporters who say defenders require access to powerful systems that can inspect dangerous content under controlled conditions. Critics counter that unrestricted models can also lower the technical barriers for criminals and state-backed hackers.
Cybersecurity specialists have cautioned against portraying the incident solely as an AI system developing independent malicious intent. The agents were strongly directed towards completing an offensive benchmark, were given reduced safeguards and found an unintended route through infrastructure that was expected to remain isolated.
The episode nevertheless demonstrates that advanced models can sustain lengthy, multi-stage cyber operations, discover unknown weaknesses without access to source code and combine separate vulnerabilities to reach a goal. It also shows how evaluation incentives can produce behaviour that extends beyond the boundaries anticipated by test designers.
