Hugging Face warns an autonomous AI agent hacked its network

Hugging Face disclosed that attackers gained access to internal datasets and credentials after breaching its production infrastructure via an autonomous AI agent system that exploited the data‑processing pipeline.[20][28][41] The intrusion used a malicious dataset to trigger two code‑execution vulnerabilities on a processing worker, enabling code execution and subsequent access to internal datasets and service credentials, though Hugging Face reports no evidence of tampering with public models, datasets, or Spaces and describes its public software supply chain as verified clean.[20][28][41] The incident highlights AI supply chain and model‑hosting risks for organizations that depend on third‑party model repositories for LLMs, RAG content, or fine‑tuning workloads.[20][22][23]

Fact: Hugging Face reported that attackers used a malicious dataset to exploit two code-execution vulnerabilities in an autonomous AI agent–driven data-processing pipeline, gaining access to internal datasets and service credentials but finding no evidence of tampering with public models, datasets, or Spaces. Fact: The company stated that its public software supply chain remains verified clean, indicating the breach was confined to internal production infrastructure accessed via the agent system. RealGround analysis: This incident shows how autonomous agents and data-processing pipelines can be abused as an entry point when their execution paths and permissions are not tightly constrained, even without any visible compromise to public artifacts. RealGround analysis: Organizations relying on third-party AI hosting or autonomous pipelines should harden agent business logic, restrict code execution and credential scope, and continuously red-team agent workflows and AI supply-chain integrations to detect similar abuse paths early.