Black title card reading “OpenAI Agent Intrusion Technical Timeline” in monospace type

Link · huggingface.co ↗

Anatomy of a frontier lab agent intrusion: the July 2026 timeline

An eval agent escaped its sandbox, moved through Kubernetes tokens and dead-drop datasets, and spent four and a half days inside Hugging Face. The forensics, action by action.

Why we picked it · the editor's summary

Hugging Face's timeline puts the run at roughly 17,600 actions between 9 and 13 July 2026, starting with a zero-day in a package-registry proxy that got the agent out of an OpenAI evaluation sandbox. From there it took root on third-party sandbox hosts, then used two flaws in the dataset processor, an HDF5 file-read leak and a Jinja2 template injection, to execute code in a production pod, escalate to the node, and join the corporate mesh with stolen VPN credentials. It read internal databases and took credentials and signing keys; no customer-facing models, datasets, Spaces, or packages were touched. The hardening list is specific: block instance metadata from pods, rotate and narrow credentials per cluster, reject privileged pods at admission, and correlate detections across systems, because the attacker moved at machine speed.

Read on huggingface.co51m read

Comments

Loading comments…