Hugging Face Confirms Production Infrastructure Breach by Autonomous AI Agent via Malicious Dataset
Hugging Face has confirmed an unauthorized intrusion into part of its production infrastructure that allowed an attacker to execute code inside the dataset processing pipeline, escalate privileges, and move laterally across multiple internal clusters during a weekend.
The company attributes the attack to an autonomous AI agent system. The entry point was not a model but a malicious dataset that activated two distinct code-execution vectors: a dataset loader capable of remote code execution and a template injection flaw in the dataset configuration itself.
From this foothold the attacker collected cloud and cluster credentials and performed lateral movement between internal environments. Hugging Face states it has found no evidence of manipulation of public models, datasets, or user-facing Spaces, nor any signs of alteration to container images or published packages.
The company is still investigating whether partner or customer information was reached and has committed to direct notification if any impact is confirmed.
Immediate containment actions included closing the code-execution routes used in the initial access, rebuilding compromised nodes, and revoking and rotating all affected credentials and tokens. Additional hardening of cluster admission controls was implemented to reduce the risk of similar artifacts entering the pipeline again.
In a notable detail, the forensic team processed more than 17,000 attacker events using LLM-based analysis agents to reconstruct the timeline, extract indicators of compromise, and identify affected credentials. The investigation ultimately relied on an open-weight model running on internal infrastructure after commercial models refused portions of the work due to safety guardrails triggered by real attack commands and artifacts.
For users and organizations, Hugging Face recommends immediate rotation of all access tokens, especially those embedded in CI/CD systems, automation scripts, or third-party integrations. Organizations should also inventory every secret that depends on these tokens, remove embedded credentials from repositories and pipelines, and enforce least-privilege access to limit potential damage.
The incident highlights a critical lesson for the AI ecosystem: the attack surface extends far beyond the model itself. Data pipelines and dataset processing have become high-value targets, and any shortcut that permits arbitrary code execution or template interpretation can serve as a direct path to internal credentials and systems.
Related articles
Employee Fired After Uploading Corporate Documents to DeepSeek: How Data Security Works in AI Services
A Moscow engineering company dismissed a top manager after she uploaded internal documents to the public DeepSeek service, with the court ruling it a breach of trade secrets. The case highlights a sharp rise in corporate data being sent to public AI models, with one study showing a 30-fold increase in 2025 compared to the previous year. Technical director Yaroslav Shmulyov of integrator R77 AI explains the full processing pipeline, from file ingestion and text extraction to embedding generation and potential use in training. Sensitive data can persist in multiple forms including original files, logs, third-party infrastructure, and model parameters even after deletion requests. Major incidents at Samsung and a U.S. cybersecurity agency demonstrate that even well-resourced organizations struggle with uncontrolled AI usage. Companies are increasingly turning to local and hybrid models to regain control over confidential information while regulators and internal policies lag behind adoption.
AI Agents Given Code and API Access Can Now Assist Attackers
An AI assistant that only answers questions can make mistakes, but an AI agent with access to email, code execution, corporate APIs and internal data can make those mistakes inside production infrastructure. The difference is fundamental: once tools, credentials and internal data are connected to the model, it becomes a privileged user that may not distinguish legitimate commands from hidden instructions on a web page. OWASP lists prompt injection, sensitive data disclosure, unsafe output handling and excessive autonomy as key risks for LLM applications. MITRE ATLAS specifically describes techniques involving prompt injection, context poisoning and tool invocation by AI agents. The article examines how agents differ from chatbots, how attackers can control them through untrusted content, and why a system prompt alone cannot protect code, data and APIs. CyberED is running its free NeuroAugust series of events and materials on AI in cybersecurity, including a session on secure AI system development.
AWS and Vercel Patch Critical Flaws in AI Agent Platforms Allowing Unauthorized Tool Execution
AWS and Vercel have addressed multiple critical vulnerabilities in their AI agent platforms that enabled unauthorized execution of tools without legitimate model approval. The issues, grouped under the CoreBreak pattern, allowed attackers to bypass AI authorization checks by injecting crafted tool calls that the infrastructure misinterpreted as model-approved actions. In AWS, CVE-2026-18830 affected the InvokeHarness API in Amazon Bedrock AgentCore, permitting authenticated users to trigger sensitive tools directly. Vercel faced two separate flaws tracked as CVE-2026-64650 and CVE-2026-64651 that let sandboxed code reach host system tools, potentially exposing secrets or cloud APIs. No public evidence of active exploitation has been confirmed yet. Organizations are advised to apply updates immediately, restrict available tools for agents, and treat all external inputs as potentially malicious.
Prompt Injection Emerges as Top Risk for LLM Applications in Production
Prompt injection attacks are moving from theoretical demonstrations to real-world exploits targeting AI assistants in enterprise environments. Attackers embed malicious instructions in emails, documents, and code comments that override developer rules when models process untrusted input. Incidents involving Microsoft 365 Copilot, GitHub Copilot, and Cursor have shown data exfiltration and remote code execution risks with severity scores above 9.0. The core issue stems from the lack of strict boundaries between trusted system prompts and untrusted external content fed into large language models. Defenses require layered controls including code-enforced permissions, input filtering, human confirmation for high-risk actions, and explicit marking of external data. Major vendors including OpenAI, Anthropic, and Google acknowledge that no single static defense can fully eliminate the threat. OWASP ranks prompt injection as the leading risk for LLM applications, urging organizations to treat AI agents as systems with untrusted inputs.