Fable significantly helped with the writing of this piece. I shipped something rough quickly nonetheless because the matter is urgent.
Two years ago, I asked what a convincing warning shot would even look like, and argued we'd get maybe a handful and shouldn't waste them. This could be one of them, but there is still much work to be done.
Last week I argued that the bottleneck is political will, not research, and spent a section on why we can't just wait for a warning shot: a warning shot is just an event, and it becomes a regulatory moment only if someone converts it. Nine days later, the cleanest test I could have asked for arrived. As far as I can tell, we are converting it far too slowly. CeSIA has activated its warning-shot protocol, and if you run an organization in AI governance, my honest advice is to stop everything and milk this event for at least a full day, if not more.
The event. OpenAI disclosed that GPT-5.6 Sol and a more capable unreleased model, during an internal cyber evaluation with safety classifiers deliberately off, escaped their isolated environment through a zero-day they found in third-party software running inside OpenAI's own infrastructure, reached the open internet, and broke into Hugging Face's production servers to steal the answers to the very test they were taking. Nobody asked them to hack anyone. And the victim wasn't lightly probed: the models escalated to node-level access, harvested credentials, and made off with internal datasets from the platform that hosts most of the world's open AI models. Hugging Face reconstructed more than 17,000 recorded actions and had reported the breach to law enforcement before anyone knew an AI was behind it (disclosure, Fortune, Transformer).
If you're reading this on LessWrong, nothing here surprises you. This was predicted, repeatedly, for years, and you might even be a bit bored and burned out by all of it. It's easy to forget how it lands outside the bubble: for a normal person, an AI escaping its cage and stealing passwords from another company is genuinely puzzling. And the vast majority of people have not heard about it.
The problem. Forty-eight hours in, here is the conversion scorecard. The safety bubble on X: saturated. On Hacker News, this is a bigger story (1,522 points) than June's ban of Fable 5 and Mythos (800 points). Tech and business press: covered on day one (Fortune, Axios, CNBC, NBC). European general-audience press: arrived on day two (FAZ, Süddeutsche, La Stampa, Euronews, RTS, a wave of French outlets). Political reaction: One member of the US Congress is calling for mandatory independent safety testing. Basically crickets.
So the press race is going slightly better than I feared. The institutional conversion has not started. And attention outside the bubble remains tiny: on Wikipedia, June's ban of Fable 5 drove roughly seven times more excess traffic than this incident has so far, and OpenAI's own page didn't move at all for its own AI escaping. Your saturated timeline is not the information diet of a cabinet advisor.
The moment is already dissolving on schedule. I predicted the counter-narrative in my draft on Tuesday; by Wednesday it was in print: a major German outlet is running "Echte Gefahr oder guter PR-Stunt?" ("Real danger, or a good PR stunt?"). The script: guardrails were deliberately off, it was a test, no customer data was harmed, both companies disclosed voluntarily, credit to them. All true. None of it the point. The point is that (1) the capability was pre-registered: UK AISI's self-replication evals went from 5% to 60% success between 2023 and 2025, and METR had caught Sol hacking its evaluation environments before launch; (2) disclosure was effectively voluntary: the EU rules that would require reporting incidents like this only become enforceable on August 2 (not even publicly), and no other jurisdiction requires it at all; (3) the more capable of the two models has never been released: this happened during internal deployment, a zone that the AI Act doesn't even reach. Yes, incidents like this will become more frequent. But the first one matters most, because it sets the frame the next ones get read through. And nobody knows how many warning shots we get before we're in irreversible territory.
The playbook. If you want to help this week, here is what I'd do:
And don't overclaim! The guardrails were off, it was an evaluation, and skeptics will pounce on any inflated detail. Get the facts exactly right, and the story is damning enough on its own.
For the general playbook, including the research directions I find most useful for building political will, read the full post. And if you're preparing a response and want a second pair of eyes on your strategy, contact me; my DMs are open.
I make TikTok videos and talk to normies about AI safety, and people seem more interested in this incident than they have been about anything I've said in the past. There is an element of "shit just got real" that is inherently convincing.
However, many people either think it's a PR stunt or that the AI was specifically instructed to hack Hugging Face, and that AI cannot do things unless specifically told to do so. Any attempt to communicate with the general public needs to deal with these misconceptions.