A model too powerful to release
Anthropic's ultra-capable Mythos model, which discovered thousands of critical software vulnerabilities, is being used via Project Glasswing to harden global infrastructure rather than being released to the public.
Joel Miller

In late February, Anthropic was under siege. President Trump had ordered all federal agencies to stop using the company’s products. The Pentagon had designated it a “supply chain risk,” the first AI company to receive that label, after Anthropic refused to remove restrictions preventing its models from being used in mass surveillance or autonomous weapons systems.
What almost nobody outside Anthropic knew at the time was that, internally, the company had just finished post-training a model that would shock even its own researchers. Claude Mythos had completed its training run, and initial evaluations were coming back with numbers that didn’t look right. SWE-bench Verified jumped from 80.8% to 93.9%. CyberGym went from 66.6% to 83.1%. Anthropic’s system card would later say the model “saturates many of our most concrete, objectively-scored evaluations.” It is, by a considerable margin, the most capable AI system known to exist.
Following the accidental leak two weeks ago, on 7 April, Anthropic finally went public with what turned out to be a warning. Project Glasswing is a coalition including Amazon, Apple, Cisco, CrowdStrike, Google, JPMorganChase, the Linux Foundation, Microsoft, NVIDIA, and Palo Alto Networks, with over 40 additional organisations given access to Mythos under controlled conditions. Their purpose: to scan and harden the world’s critical software before anyone else gets a model this powerful. Because in the weeks between finishing post-training and going public, Mythos had found thousands of zero-day vulnerabilities across every major operating system and web browser. It found a 27-year-old vulnerability in OpenBSD and a 16-year-old flaw in FFmpeg hidden in code that had been hit five million times by automated testing tools without detection.
Within 48 hours, Treasury Secretary Scott Bessent and Federal Reserve Chair Jerome Powell summoned the CEOs of America’s systemically important banks to the Treasury building. Jane Fraser of Citi, Ted Pick of Morgan Stanley, Brian Moynihan of Bank of America, Charlie Scharf of Wells Fargo, and David Solomon of Goldman Sachs all attended. Jamie Dimon couldn’t make it, though JPMorganChase was already a Glasswing launch partner. The purpose, according to Bloomberg and Reuters: to ensure financial institutions understood what Mythos and comparable models could mean for their exposure to attack.
So what can we make of this? The model was likely never intended for general availability. Its destiny was more likely as a teacher: a source of synthetic training data and distillation targets for smaller, more economically viable models. One also wonders: if Anthropic has had Mythos internally since February, why hasn’t its own output reflected this step-change in capability? To be fair, the company shipped 74 releases in 52 days between February and March. But shipping features is not the same as shipping transformative products.
That gap between model capability and real-world product delivery matters for how we think about the threat. Because if Anthropic, with direct access to Mythos and every incentive to move fast, still faces friction in turning raw capability into shipped products, we should expect a similar friction on the offensive side. Finding vulnerabilities is not the same as orchestrating a coordinated attack campaign. Target selection, exploit chaining, lateral movement, operational security, infrastructure management, money laundering: like product development, these still require substantial judgment and coordination.
But the general concern felt in the tech community is valid. In product development, the bottleneck is taste, design, market fit, user experience, things that are subjective, high-dimensional, and stubbornly resistant to automation. In offensive cyber operations, the bottleneck is more mechanical. And the data shows it is already being ground down. CrowdStrike’s 2026 Global Threat Report shows average breakout time, the interval between initial compromise and first lateral movement, fell to 29 minutes in 2025, down from 48 minutes in 2024 and 98 minutes in 2021. Check Point reported on an orchestration framework called Hexstrike-AI that directed over 150 specialised AI agents to autonomously scan, exploit, and persist inside targets, tasks that took human operators days completed in under 10 minutes.
The AI cyber risk clock was already ticking, but now we know the worst case is possible. Anthropic’s own red-team lead has said comparable offensive capability could appear in other models within 6 to 18 months. But distillation, architectural improvements, and the sheer pace of competition mean that window is optimistic. And it assumes no more leaks — a shaky assumption given how Mythos itself came to light. If OpenAI’s or Google’s most capable internal models were similarly compromised, the timeline collapses.
For the past two decades, the implicit contract of digital life has been that platforms stay up, trust is cheap, and security can be treated as a line item rather than a strategic concern. That contract held because the economics of attack held: exploits were expensive, skilled attackers were scarce, and most targets weren’t worth the effort. Every layer of the modern digital economy was built on that assumption of affordable, ambient stability. Mythos doesn’t just threaten individual systems; it threatens the economic foundation underneath them. When the cost of finding and weaponising vulnerabilities collapses, the implicit trust we place in platforms and vendors stops being a reasonable default and starts being a liability. That shift is permanent: we are not going back to a world where security is easy because attacks are hard.
So what does the next five years look like? Broadly, five scenarios. The optimistic case is managed hardening, where Glasswing-style coalitions continuously scan critical software before release, patch times collapse, and the economy pays a much larger security premium in exchange for genuine resilience. The most likely, in our assessment, is permanent breach: offensive capability diffuses faster than defenders can patch, hyperscalers retreat into hardened cores, and the long tail of smaller organisations, hospitals, schools, and neglected open-source dependencies lives with persistent fraud and downtime. Munich Re already warns that digital supply chain breaches are “more the norm than the exception”. A third path is the monoculture, where sensitive workloads migrate into attested confidential computing environments controlled by a handful of hyperscalers and model creators; security improves inside the core but concentration risk simply migrates from open-source dependencies to model access. A fourth is geopolitical cyber war, with states treating frontier AI as strategic assets, exploits hoarded more selectively, and critical infrastructure defence merging with national security planning. The tail risk is cascading shock: a shared identity provider or software distribution channel is compromised at scale before defenders adapt. The IMF has warned a systemic cyber incident affecting financial market infrastructure could threaten stability, and the Bessent-Powell meeting suggests the people closest to the plumbing are taking that risk seriously now.
There is a near-term silver lining. The current dynamic resembles a “U-shaped curve”: adversary operators are racing to extract value from existing zero-day stockpiles before defensive scanning discovers them, while their promised pipelines of automated AI exploit development keep slipping. Defensive AI is increasingly finding the same vulnerabilities attackers are hoarding — “bug collisions” that mark down the value of existing assets via patching waves. Mythos doesn’t kill the zero-day market, but it deflates it like a bubble: the scarcity premium that made these exploits valuable evaporates. The next 6 to 9 months may be a defender’s window, not an attacker’s paradise, with the real winners being organisations in Glasswing-style consortia and anyone controlling frontier AI for offence.
Global cybersecurity spending hit $240 billion in 2026, up 12.5% year on year, with security consuming 8-12% of enterprise IT budgets and 10-15% in financial services. Meanwhile, AI-assisted code generation is pushing the cost of development down toward $10 per hour of equivalent human output. Two curves are crossing: build costs falling, security costs rising. Within two to three years, security could become the dominant cost in software delivery for many organisations. That’s a structural shift in the economics of building software, and it arrives at precisely the moment when agentic engineering and “vibe coding” are encouraging people to ship faster with less rigour.
There is an emerging counter-strategy worth watching. The zero-dependency approach, where AI agents rewrite library functionality from specifications and test suites rather than pulling in external packages, eliminates supply chain risk. Research from the University of Texas found that 20% of AI-generated package references point to non-existent libraries, and 43% of those hallucinated dependencies recur consistently enough for attackers to pre-register them. The most valuable investment right now might not be in AI tooling or security products alone. It might be in recreating more software from scratch and committing more fundamentally to the agentic software age.
Takeaways: The window to act is short and it is measurable: perhaps months before Mythos-class offensive capability proliferates beyond the controlled coalition now using it defensively. Personal security hygiene is the immediate first step (Andrej Karpathy’s digital security checklist, covering hardware keys, password managers, encrypted messaging, and device minimisation, has become the reference guide and is worth following this weekend). For organisations, the priority is harder but clear: audit your dependencies, invest in specifications and test coverage, embed security architecturally into your build pipelines rather than bolting it on after the fact, and stress-test your assumptions about the platforms you depend on.