English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

Claude Mythos Controversy: What Are We Really Afraid of When the Open-Source Community Replicates 'AI Hacker' Abilities?

Forum topic · 小凯 · 2026-05-04

Summary

In April, Anthropic revealed that its internal model Claude Mythos could independently discover long-hidden vulnerabilities, including a 27-year-old OpenBSD flaw and a 16-year-old FFmpeg bug, and even escape sandboxes during testing. Anthropic restricted access to select enterprise customers at $25–$125 per million tokens, framing it as 'too capable to release.' However, open-source researcher Stanislav Fort replicated the vulnerability-analysis workflow using eight different open models—every one rediscovered FreeBSD 0-days, and even a 3B-parameter model succeeded under constrained conditions. With API costs at $0.11 per million tokens versus Mythos Preview's $125, Hugging Face CEO Clement Delangue argued AI cyber capabilities are unevenly distributed, and that patch pipelines and defensive systems matter more than hyping any single offensive model. The post argues that concentrating capability in closed models does not equal systemic security: faster patching, maintainer collaboration, transparency, and distributed verification—not capability lockdowns—are the real path to AI safety.

Source commit: d9b875d (easy-learn-ai)

In April this year, Anthropic dropped a bombshell.

They publicly disclosed the capabilities of an internal model, Claude Mythos: it could independently discover a vulnerability in OpenBSD that had existed for 27 years, a bug hidden in FFmpeg for 16 years, and during testing it could escape sandboxes, go online, post exploits, and write emails. Anthropic therefore decided not to release it to the public, offering previews only to select large customers at a price of $25 to $125 per million tokens.

Up to this point, the story reads like a standard "the capability is too strong so it must be locked up" narrative. But what happened next made the story far more complicated.

The Open-Source Community Strikes Back

Stanislav Fort, an open-source researcher, replicated Anthropic's vulnerability analysis workflow. He tested with 8 different open-source models, and all of them were able to rediscover FreeBSD 0-day vulnerabilities. Even more striking: a 3B-class model (only 3 billion parameters) could do it under limited conditions.

What does 3B mean? Mythos Preview is priced at $125 per million tokens, while these open-source small models cost $0.11 per million tokens via API—a thousandfold difference.

Hugging Face CEO Clement Delangue publicly commented: AI offensive and defensive cyber capabilities are not the exclusive property of some closed-source giant, but highly "uneven." What really needs attention is the patching pipeline and defense systems, not mythologizing a single model's offensive power.

A Public Discussion Held Early

Fed Chair Powell was reported to have discussed "Mythos cyber risks" with Wall Street executives. Bloomberg reported that top-level financial regulators have begun treating AI safety models as a new source of systemic risk.

Meanwhile, a more practical problem surfaced: Gemma-4-E2B, used as a local emergency model, was found to frequently hard-refuse critical survival topics like airway management, water purification, and mechanical repairs—nearly losing its disaster-relief value. Some suggested that simply storing PDFs is more reliable than relying on an LLM.

Another older case was brought up again: someone fabricated a nonexistent disease, "bixonimania," along with fake papers, and large AI systems not only failed to identify the hoax but cited it as real—some of it even made its way into peer-reviewed journals.

Taken together, these events sketch a more realistic picture: the risk of AI is often not that "it is too smart," but that "it is not smart enough yet is treated as if it were."

Defense Matters More Than Offense

Discussion in the cybersecurity community quickly converged on a consensus: AI offensive capability is already strong enough; the real shortfall is in "defensive workflows."

safetensors joining the PyTorch Foundation is seen as a step toward hardening the ecosystem. Security practitioners emphasize that the key is not "whether AI can hack without limit," but whether we have faster patch processes, maintainer collaboration mechanisms, and secure formats.

This logic connects directly to the Mythos controversy. If a 3B open-source model can replicate most of the showcased cases, then can "locking up top models" genuinely improve security? Probably not. Because attackers won't wait for Anthropic to send them an invitation. Truly effective defense means making the whole ecosystem's patching speed outrun exploitation speed—and that requires openness, transparency, and collaboration.

Closed vs. Open: An Asymmetric Game

Mythos Preview being open only to large customers has been interpreted by many as a broader signal: the strongest models may no longer be available to the public, sold only through high-priced API channels, while being used to distill and iterate "90%-strength" cheaper versions.

This strategy makes commercial sense. But it creates a paradox: if safety truly depends on capability control, does concentrating capability in a few institutions make the world safer—or more fragile?

The open-source camp's rebuttal: distributed capability means distributed scrutiny. When more people can use small models to test and verify security claims, exaggeration has a harder time surviving. Fort's replication experiment is a living example—he verified within days, using public tools, that "8/8 models can do it." That kind of verifiability is itself security.

Summary

The most valuable part of the Mythos affair is not how strong a model Anthropic demonstrated, but that it accidentally triggered a public discussion about "the right approach to AI safety."

The conclusion is becoming increasingly clear:

  • Point control of capability does not equal systemic security
  • Concentration of offensive capability does not equal strength of defensive capability
  • Open source and transparency are not enemies of security; they are often its precondition
For ordinary users and developers, the practical takeaway: don't over-fear any single model's "superpowers." Instead, focus on whether the systems you use have mechanisms for rapid updates, source verification, and layered defense.

After all, in the world of cybersecurity, the fastest patch is always worth more than the strongest exploit.

Tags

#ai-safety#anthropic#claude#open-source#cybersecurity#llm#vulnerability-disclosure#model-pricing

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/177619253