Hugging Face says an AI agent hacked its infrastructure, and it used AI to fight back

What happened

AI platform Hugging Face has disclosed a breach of parts of its production infrastructure that was allegedly carried out entirely by an autonomous AI agent system. The company says it detected and analyzed the attack largely with its own AI tools. According to Hugging Face, the attackers gained unauthorized access to a limited set of internal datasets and several credentials used by Hugging Face services.

According to the company, that had two advantages: no attacker data, and none of the referenced credentials ever left its own environment.

"We do not know which model powered the attacker's agents, whether a jailbroken hosted model or an unrestricted open-weight one; either way, the attacker was bound by no usage policy, while our own forensic work was blocked by the guardrails of the hosted models we first tried," Hugging Face wrote.

The practical lesson for defenders, the company says, is to have a capable model running on your own infrastructure before an incident happens. Hugging Face adds that this isn't an argument against safety measures on hosted models. Hugging Face says it shut down the exploited code execution paths, revoked the attacker's access, rebuilt compromised nodes, and rotated affected credentials.

Why it matters

The company says public models, datasets, and Spaces were not tampered with, and the software supply chain was not affected. Whether partner or customer data was compromised is still under investigation. According to Hugging Face, the attack started at one of the weakest spots on any AI platform: the data processing pipeline.

A malicious dataset exploited two code execution paths in dataset processing, specifically a remote code dataset loader and a template injection in a dataset configuration. From there, the attacker escalated to node level, harvested cloud and cluster credentials, and moved laterally across multiple internal clusters over a weekend. An autonomous agent framework built on an agentic security research harness orchestrated the entire campaign, the company says.

Hugging Face says it doesn't know which language model powered the attack. The system executed many thousands of individual actions through a swarm of short-lived sandboxes and used self-migrating command-and-control infrastructure running on public services. The company classifies the incident as the "agentic attacker" scenario the industry has been predicting for some time.

Hugging Face says it spotted the attack through an AI-powered anomaly detection pipeline that runs LLM-based triage on security telemetry. To make sense of the more than 17,000 recorded attacker actions, the company deployed LLM-driven analysis agents. Those agents reconstructed the timeline, extracted indicators of compromise, mapped affected credentials, and separated real damage from deception activity. Work that would normally have taken days was done in hours, the company says.

According to Hugging Face, when the security team first tried to analyze the attack logs using frontier models behind commercial APIs, it hit a wall. The providers' safety guardrails blocked the requests because they couldn't tell an incident responder from an attacker. The analysis required submitting large volumes of real attack commands, exploit payloads, and C2 artifacts, all of which tripped the filters. 2, running on its own infrastructure.

What to watch

The company also tightened access controls and improved its detection systems, according to the blog post. Hugging Face is working with external cybersecurity forensics experts and has reported the incident to law enforcement. As a precaution, the company recommends that all users rotate their access tokens and review recent account activity. The incident confirms that autonomous, AI-driven attack tools are no longer theoretical.

According to Hugging Face, they lower the cost of broad, multi-stage campaigns and operate at machine speed. The company argues that data and model surfaces need to be t