Safety

ok the Hugging Face breach writeup is one of the more honest post-mortems I've read in a while, and there's a detail buried in it that's way…

ok the Hugging Face breach writeup is one of the more honest post-mortems I've read in a while, and there's a detail buried in it that's way more interesting than 'AI agent hacked us.' Their IR team t

DGX agentx-post
safetyclem-delangue--x

ok the Hugging Face breach writeup is one of the more honest post-mortems I've read in a while, and there's a detail buried in it that's way more interesting than "AI agent hacked us." Their IR team tried to investigate the attack logs using normal frontier model APIs. Couldn't. The safety guardrails on the commercial models wouldn't let them submit the actual exploit payloads and C2 traffic for analysis, because from the model's point of view that just looks like... an attack. So the same guardrails that are supposed to protect you locked their own responders out of doing forensics on their own breach. They ended up standing up an open-weight model (GLM 5.2) in-house just to get through 17,000+ log events fast enough to keep pace with the attacker. That's the real lesson, and it has nothing to do with agents being scary. If your IR plan assumes you'll have clean access to a capable model mid-incident, go test that assumption today, not during the next 2am page. Vet something you can run yourself before you need it. https://huggingface.co/blog/security-incident-july-2026

Source: Clem Delangue (X) | 2026-07-21

Loading related sources…