An autonomous agent ran 17,000 actions inside Hugging Face production, harvesting credentials and internal datasets
At a Glance
- Catastrophic failure. Permanent data loss, major security breach, six-figure damages, or legal exposure.
Independent project · aggregated from public reports and may be unverified — see the primary source below · not affiliated with or endorsed by any company or product named.
What Happened
Hugging Face disclosed that an autonomous AI agent framework chained two code-execution paths in its dataset processing pipeline to land on a processing worker, then escalated to node-level access and moved laterally across internal clusters. The intrusion ran many thousands of individual actions across a swarm of short-lived sandboxes with self-migrating command-and-control staged on public services. A limited set of internal datasets and several service credentials were accessed; public models, datasets, Spaces, container images and published packages were verified clean. Hugging Face reconstructed the timeline from over 17,000 recorded attacker events using an on-premises open-weight model, because commercial APIs refused the analysis on safety grounds.
Case Analysis
Verified Facts
- Two code-execution paths in dataset processing were the entry point
- The agent escalated from a processing worker to node-level access and moved laterally across internal clusters
- Over 17,000 attacker events were recorded and analysed with an on-premises open-weight model
Not Publicly Confirmed
- Whether partner or customer data was exposed, assessment was ongoing at publication
Operational Lessons
- Dataset and artifact ingestion pipelines are code-execution surfaces and need infrastructure-level sandboxing
- An automated intruder operating at machine speed outruns human-paced incident response, so telemetry must alert in real time
Primary Source
Security incident disclosure, July 2026 (Hugging Face)huggingface.co ↗Case Record
More Cases
Klarna replaced 700 agents with an AI assistant, then started rehiring humans after service quality dropped
Klarna said in 2024 that its OpenAI-powered assistant did the work of 700 customer-service agents. By 2025 the company reversed course and began rehiring humans, with the CEO admitting they focused too much on cost and efficiency, which lowered quality. Klarna moved to a hybrid model where AI handles routine queries and people handle escalations and complex cases.
Cursor's command allowlist could be bypassed with shell built-ins, giving prompt injection a silent path to code execution
Pillar Security disclosed CVE-2026-22708 in Cursor. In Auto-Run Mode with an allowlist enabled, shell built-ins such as export, typeset, declare, readonly, unset and local were implicitly trusted by Cursor's server-side evaluator and executed without appearing in the allowlist or requiring approval, because they run inside the shell session rather than as separate binaries. An attacker delivering indirect prompt injection could silently poison environment variables and then trigger malicious code through trusted developer tools, producing both zero-click and one-click remote code execution. Pillar reported it in August 2025, Cursor acknowledged it as a systemic issue in September 2025, and the fix shipped in version 2.3 in January 2026, which now requires explicit approval for any command the parser cannot classify.
Prompt injection reached host-level code execution in Microsoft Semantic Kernel through eval() and a stray annotation
Microsoft disclosed two vulnerabilities that turn prompt injection into host compromise in its Semantic Kernel agent framework, which has over 27,000 GitHub stars. CVE-2026-26030 affects the Python package before 1.39.4: the default in-memory vector store filter is a Python lambda executed with eval() on unsanitized model-controlled input, so an attacker could escape the template string, traverse Python's class hierarchy, bypass the AST blocklist validator and run arbitrary commands, demonstrated by launching calc.exe from a single prompt injection. CVE-2026-25592 affects the .NET SDK before 1.71.0: DownloadFileAsync was accidentally marked with a [KernelFunction] attribute, exposing it to the model with an entirely AI-controlled, unvalidated local file path, allowing writes to locations such as the Windows Startup folder and thus sandbox escape.