AI Safety's Real Threat Is Mundane Misuse. The Field Is Still Arguing About the Robots.

A post on Bluesky this week didn't rack up thousands of likes or spawn a viral thread. It just sat there, precise and a little damning: "State actors quietly normalized commercial AI APIs as operational infrastructure while the safety discourse stayed fixated on hypothetical AGI risk. Mundane misuse already outpaced every red-team scenario."[¹] The author didn't name names. They didn't need to. The observation was pointed enough that it rattled around a corner of the AI safety conversation that usually doesn't like being rattled.

The post arrived the same week that Anthropic's "safety-first" brand was taking hits from an entirely different direction — reports of its Mythos tool being accessed without authorization, and separate claims about browser activity logging with no opt-in. Neither story is, on its own, existential. Together they trace the same contour the Bluesky post was describing: the gap between the safety framing that companies deploy publicly and the operational reality underneath it. Anthropic's governance problem isn't a rogue superintelligence. It's product teams shipping code that conflicts with the story the communications team is telling.

What makes the Bluesky argument worth sitting with is its structural claim — that the safety field has a mismatch problem baked into its incentives. Catastrophic AGI scenarios are legible, fundable, and philosophically interesting. Tracking how Telegram bots, commercial large language models, and off-the-shelf API wrappers get stitched into state-level influence operations is unglamorous, jurisdiction-dependent, and produces findings that don't fit the conference circuit. So the people at the top keep talking past the problem that's already here. One commenter framed it differently: that serious AI governance thinking — especially on the economic side — should be pushing for fully socialized ML infrastructure, not just chip export controls. That's a harder political argument, but it at least starts from a realistic picture of who is actually using these systems and how.

The honest conclusion isn't that AGI risk is fake or that the researchers worrying about it are wasting everyone's time. It's that the field has built a discourse optimized for a threat that hasn't arrived while systematically underweighting the threat that has. When a state actor doesn't need to build its own model — it just calls an API — the question of whose safety framework governs that transaction doesn't have a clean answer. The safety establishment hasn't produced one yet, and the companies providing the APIs have strong financial reasons not to ask.