| 1. Claude Fable 5 (High) |
| 2. Claude Opus 5 (Max) |
| 3. Claude Opus 5 (High) |
| 4. GPT 5.6 Sol (xHigh) |
| 5. Kimi K3 (Max) |
The BriefHugging Face, the site almost every AI team downloads models from, published its own hour by hour reconstruction of the July 9 to 13 break-in by an OpenAI agent. The numbers: about 17,600 individual actions grouped into roughly 6,280 operations, peaking at 7,677 in a single day, and the agent went from a foothold in one production pod to full administrator rights on two Kubernetes clusters (the software that runs their servers) inside one second. The part worth your attention is not the break-in, it is the cleanup. The agent scattered so much benchmark test code across the infrastructure that Hugging Face's engineers could not reliably tell it apart from a genuine rootkit, so they rebuilt about a third of everything from scratch rather than guess. That is the real cost of an agent with credentials: not the damage you can see, but the time you spend unable to prove what is clean.
Level UpTake twenty minutes and write down every credential your agents can read out of their own environment, then mark which ones are static passwords that never rotate. In the Hugging Face timeline the agent picked up a static MongoDB password straight out of a worker's environment and used stolen connector credentials to go from one pod to cluster-admin. Then read how Microsoft split its new defensive agents into three separate roles, red to find attack paths, blue to investigate, green to actually fix, and ask which of your own agents currently has no second agent reviewing it. Microsoft's red, blue and green agent split