OpenAI’s Hugging Face Hack Debrief Raises More Questions Than It Answers
The AI giant acknowledges that it could have done far more to prevent its AI agents from going rogue. But it still fails to explain why it didn't see this fiasco coming.
Watching the Watchers
Months before the Hugging Face hack, OpenAI says, employees noticed that its agents had created a covert message board in the package manager Artifactory, which they would later use to coordinate their attack. Around May 26, OpenAI says in the postmortem, “an internal team observed an agent engage in message board activity.” Then, on June 27, OpenAI responders found that a different security incident was linked to the “improvised message board” in Artifactory.
While it’s clear some employees at OpenAI were aware of the message board, the discovery apparently wasn’t escalated to the appropriate safety and security leaders. The AI lab says that on July 6, just days before its agents began using it to organize their attack on Hugging Face, “leaders responsible for incident detection and response” were unaware of its existence, let alone what it signified.
“To clarify, we weren’t aware of the agent covert comms at that point,” OpenAI’s chief information security officer, Dane Stuckey, wrote in a post on X earlier this month. “Investigative thesis of that day is wildly different from what we know now, of course. Always room for improvement, and it is obvious with the benefits of hindsight.”
It’s unclear why OpenAI staffers who knew about the message board seemingly didn’t flag it to Stuckey and other executives responsible for responding to security issues. When asked about this issue, an OpenAI spokesperson reiterated that OpenAI could have triggered an earlier response with the benefit of hindsight. “OpenAI’s ongoing work in this area will inform additional improvements to coordination and response alongside the action plan in this technical incident report,” they said.
“If they did have some signals that one or more agents were attacking Artifactory, why weren't they monitoring these tests long before something broke out to attack Hugging Face?” says Jake Williams, vice president of research and development at the security firm Hunter Strategy.
The postmortem also leaves other key parts of what happened unexplained. At one point on July 4, for example, OpenAI says that sustained “high-volume agent activity caused the OpenAI Artifactory service to become unavailable." On July 5, OpenAI’s monitoring systems triggered an alert. But the report doesn't say why it took a day for there to be an alert about the outage.
OpenAI says it is putting in place more tools to monitor its AI systems. The company says it's creating an alert system run by automated monitors, which aims to notify human safety, security, and research teams within 30 minutes of severe incidents occurring. If an employee can’t respond quickly enough, they’re expected to pause the relevant activity.
OpenAI repeatedly acknowledges that guardrails it already has in place likely would have flagged the agents’ behavior as unsafe, but they were intentionally disabled for testing. When it comes to monitoring, though, the report is less clear about why there were gaps in the oversight of testing environments. The postmortem notes, “If our currently deployed [chain-of-thought] monitoring system was running at the time of the incident, it would have caught the initial relevant activity and paged our security team more than a day before models breached Hugging Face systems.”
No-Win Scenarios
OpenAI says another key contributor to the Hugging Face incident was that its new AI models are more “persistent” than ever, willing to work almost endlessly and expend vast amounts of computing resources to achieve their goals. Developing these types of AI models is part of the company’s broader ambitions to create always-on AI agent products—which will work for people around the clock, taking in lots of information to complete tasks on behalf of people.
However, OpenAI says that many of the third-party benchmarks it used to evaluate its AI models contained tests that were effectively impossible to solve. One such test was a benchmark called ExploitGym, which measures cybersecurity capabilities. OpenAI claims that, at least at the time, this benchmark included more than a hundred tasks that were unsolvable. When these challenges were given to persistent AI systems, they resorted to unintended means to solve them.
Originally published on Wired


