How Claude Mythos Is Reshaping Cryptanalysis: HAWK, AES and the Rise of AI-Driven Crypto Research
Claude Mythos cryptanalysis weakens HAWK post-quantum signature, speeds AES Möbius Bridge attack, and powers CryptanalysisBench benchmark in AI-driven crypto research.
With Craig Major and Jon Irwin

Watch this episode
Watch on YouTubeClaude Mythos Cryptanalysis Just Broke a Post-Quantum Standard
Estimated reading time: 12 minutes
Key Takeaways
- In August 2026, Anthropic published findings showing that Claude Mythos cryptanalysis can find flaws in the mathematics underneath cryptographic algorithms.
- In 60 hours of work, Claude Mythos Preview weakened a leading post-quantum signature candidate called HAWK so significantly that its designers pulled it from the NIST standardization process entirely.
- The AI also improved the best-known attack on a reduced version of AES by up to 800 times.
- Neither attack threatens anything you use today, but both results have permanently changed how the cryptography community thinks about the role of AI in security research.
Table of contents
- Claude Mythos Cryptanalysis Just Broke a Post-Quantum Standard
- Key Takeaways
- What Is Claude Mythos and Why Does Cryptanalysis Matter
- The HAWK Attack — A Post-Quantum Signature Scheme Halved
- The AES Möbius Bridge — A 200–800× Speed Gain on a Reduced Cipher
- CryptanalysisBench — A Tool for Tracking AI Cryptanalytic Ability
- Other Ciphers in the Crosshairs — LEA, Serpent, Salsa20
- What This Means for the Future of Cryptographic Standards
- FAQ
The internet runs on trust. Trust that your bank login is private. Trust that your messages are sealed. Trust that the systems protecting your data have been tested hard enough to hold.
That trust is built on cryptographic algorithms — mathematical locks that researchers spend years trying to break before criminals or hostile governments can. The slower those locks get cracked, the safer everyone is.
In August 2026, Anthropic published findings showing that Claude Mythos cryptanalysis has now moved beyond finding coding bugs in security software. It can find flaws in the mathematics underneath. In 60 hours of work, Claude Mythos Preview weakened a leading post-quantum signature candidate called HAWK so significantly that its designers pulled it from the NIST standardization process entirely. The AI also improved the best-known attack on a reduced version of AES, the world's most widely deployed encryption standard, by up to 800 times.
Neither attack threatens anything you use today. But both results have permanently changed how the cryptography community thinks about the role of AI in security research.
Here is what happened, why it matters, and what comes next.
---
What Is Claude Mythos and Why Does Cryptanalysis Matter
Before getting into the attacks themselves, it helps to understand the territory.
Cryptanalysis is the science of finding weaknesses in encryption systems. Think of it like stress-testing a bridge before you let cars drive on it. Researchers try to break cryptographic algorithms on purpose, in a controlled environment, so that real attackers cannot break them first. The more eyes on an algorithm — and the harder those eyes try — the more trustworthy the final standard becomes.
Historically, this work has been done by small teams of highly specialized human mathematicians. Progress is slow. A single improvement in an attack technique might take years to develop and require deep familiarity with a narrow area of math.
Claude Mythos Preview is Anthropic's most capable AI model, and it was already known to find bugs in cryptographic software code before this research. What changed with these new results is the level at which it operates. The model is now finding mathematical weaknesses in the algorithms themselves, not just in the programs that use them.
This is a meaningful step up. Writing code incorrectly is one kind of error. Designing a mathematical scheme with a hidden structural flaw is another kind entirely.
The two attacks described below each target a different type of cryptographic primitive:
- Digital signature schemes: Used to verify that a message or file genuinely came from who it claims to come from. When you visit a secure website, your browser checks a digital signature.
- Symmetric ciphers: Used to encrypt the actual data flowing between you and a server once identity has been confirmed. AES is the cipher used to protect the majority of internet traffic.
Both matter. Both were weakened — in different ways, at different levels of severity.
Sources:
- hawk_key_recovery.pdf
- arxiv.org/html/2607.18538v1
---
The HAWK Attack — A Post-Quantum Signature Scheme Halved
What HAWK Was Trying to Solve
Quantum computers do not yet exist at the scale needed to break today's encryption. But they are getting closer. Experts at Google have noted that the timeline to a cryptographically relevant quantum computer is shrinking, and that shift threatens widely used classical systems like RSA and ECDSA.
In response, the US National Institute of Standards and Technology (NIST) launched a multi-year competition to identify new post-quantum cryptography (PQC) algorithms — systems that would remain secure even against future quantum hardware. HAWK was one of the remaining third-round candidates in NIST's call for additional digital signatures, meaning it had already survived two full rounds of expert human review spanning two years.
HAWK's security rests on the hardness of the Lattice Isomorphism Problem — a mathematical challenge believed to be difficult even for quantum computers.
What Claude Mythos Found
Working semi-autonomously over roughly 60 hours, Claude Mythos Preview discovered a previously unexploited structural property inside the HAWK lattice called a nontrivial automorphism.
Prior academic work (published at the Cryptology ePrint Archive under the reference 2025/928) had already proved that finding such an automorphism would allow an attack. But that work left open the critical question: does such a useful automorphism actually exist in the specific lattice HAWK uses? Mythos answered that question with a yes — and then built the attack.
The automorphism it found allows a faster enumeration attack on HAWK keys. The attack is still exponential in difficulty (meaning it does not make HAWK trivially breakable), but the numbers shift dramatically:
| HAWK Parameter | Previous Attack Cost | Post-Mythos Attack Cost |
|---|---|---|
| HAWK-256 | 2^64 operations | 2^38 operations |
| HAWK-512 | 2^150 operations | 2^108 operations |
| HAWK-1024 | 2^288 operations | 2^182 operations |
To put HAWK-256 in plain terms: the expected cost to break it dropped from a number that would take longer than the age of the universe to compute, to something far more tractable. In practical terms, this effectively cuts the security level of every HAWK key size in half.
To maintain equivalent security, HAWK would need to double its key sizes. But that would eliminate many of the efficiency properties that made HAWK an attractive candidate in the first place.
HAWK's designers withdrew the scheme from the NIST process following the disclosure. Anthropic shared the attack with the HAWK authors in June 2026 before coordinating public disclosure to the NIST mailing list. A formal notice appeared on the NIST PQC forum describing the attack as "HAWK-n Key Recovery Reduces to SVP in Dimension n/2+1."
Importantly, this result is specific to HAWK's mathematical structure. It does not affect other NIST post-quantum signature candidates or lattice-based cryptography schemes like Falcon, which use different underlying constructions.
How the Discovery Happened
Mythos worked inside a multi-agent code harness similar to Claude Code, with multiple worker agents collaborating in a sandboxed environment. They had access to Python, the Sage mathematics system, and published cryptographic literature.
The human supervisor had a background in theoretical computer science but was not a cryptography specialist. Their role was mostly project management — suggesting which libraries to use for verification, helping agents organize ideas. The actual mathematical discovery came from the agents themselves.
In an interesting emergent dynamic, two worker agents began exploring the same idea independently. The first agent concluded it was infeasible and dropped it. The second agent found a way to make it work. The two agents exchanged notes, reached agreement, and produced the attack together.
Total compute cost: approximately $100,000 in API costs.
Sources:
- hawk_key_recovery.pdf
- eprint.iacr.org/2025/928
- NIST PQC forum thread
- postquantum.com/security-pqc/ai-cryptanalysis-hawk-aes/
---
The AES Möbius Bridge — A 200–800× Speed Gain on a Reduced Cipher
Background on AES and Reduced-Round Attacks
The Advanced Encryption Standard (AES) was standardized by NIST in 2001 and has been scrutinized more heavily than almost any other cipher in history. It has held up well. AES-128 — the specific variant in this research — uses 10 rounds of transformations to encrypt data.
Researchers regularly study round-reduced variants of AES, meaning stripped-down versions that run fewer than the full 10 rounds. These reduced versions are not used in production. They serve as research proxies: studying them reveals new attack techniques, tests the security margins of the full cipher, and helps the cryptography community build confidence that the full standard remains solid.
This attack targets 7-round AES-128. It operates under a chosen plaintext model, where an attacker can ask a defender to encrypt arbitrary inputs with a hidden key and observe the outputs. The previous best attack of this type required requesting the encryption of 2^105 chosen plaintexts — completely impractical, but useful as a theoretical benchmark.
What the Möbius Bridge Does
Mythos improved on the previous best meet-in-the-middle attack on 7-round AES. Meet-in-the-middle attacks work by trading computation time for storage space — you pre-compute and store a table of intermediate encryption values, then look up matches from the other direction to recover the key without trying every possibility.
The bottleneck in prior work was a stage where an attacker had to enumerate 256 different possible values and look each one up in a pre-computed table. That 256-way guessing step was expensive.
Mythos developed a new fingerprinting technique it named the Möbius Bridge — a mathematical transform that is invariant to this 256-way guess. In plain terms: you no longer need to make that guess at all. One lookup replaces 256. That alone reduces the work in that stage by a factor of 256.
Computing the Möbius Bridge transform itself is more expensive than the old approach, so Mythos also developed several additional optimization techniques to compensate. The net result: the attack runs 200 to 800 times faster than the previous best method, depending on measurement approach.
Empirical testing confirmed the attack recovered all eight target keys in the experimental setup, with a mean per-structure lookup count of approximately 2^23 and a Bloom filter hit rate of 0.0460.
The Discovery Process Was Almost Entirely Autonomous
This result differed from the HAWK attack in one important way: Mythos found it almost entirely on its own, with almost no human guidance. A researcher at Anthropic built a scaffold that allowed the model to pose hypotheses, run experiments, and self-correct based on results.
The early runs hit a wall. Claude initially refused to engage with the problem, stating that improving AES cryptanalysis was simply impossible. The logs include messages like:
> "If you want a different outcome, the target has to change… AES-128 r5/r6 is just genuinely hard."
The researcher sent one message suggesting Claude stop assuming the problem was unsolvable and actively search for novel approaches. Claude rewrote its own agent harness with that framing — and found new ideas on 6-round AES shortly after.
After being nudged toward the 7-round target, Claude worked almost completely independently for three days. It produced several hundred million tokens of output during that stretch. The research team sent just three brief prompts during that entire period, mostly reminders to aim for publishable-quality findings rather than incremental gains.
Three days in, Mythos developed the Möbius Bridge concept. A few days later, after outputting roughly one billion total tokens, it had fully refined the attack into the form described in the published paper.
Human researchers then spent several hundred hours validating the result — learning enough cryptography to confirm the math was correct and prepare the paper for release. The model found the attack in days. Confirming it took months.
Sources:
- aes_mobius_bridge.pdf
- mlq.ai news article
- news.geobrowser.io story
---
Your Automation Stack Is Probably Costing You More Than You Think
While cryptographers are using AI to do in 60 hours what took humans two years, most businesses are still doing repetitive work by hand. Manually processing data, routing requests, chasing approvals, copying information between tools. These tasks don't disappear on their own.
Flowgrammer builds custom business automation systems that remove manual work from your operations — freeing your team to focus on what actually requires human judgment.
👉 See how automation can scale your operations (how automation can scale your operations)
---
CryptanalysisBench — A Tool for Tracking AI Cryptanalytic Ability
One of the side effects of this research is a new problem that the broader security community now has to deal with: how do you measure how good AI models are at breaking encryption?
To help answer that, Anthropic partnered with academics at ETH Zurich, Tel Aviv University, and TU Berlin to build CryptanalysisBench — a standardized benchmark that packages together multiple cryptographic ciphers and provides a consistent testing environment for evaluating how well large language models perform at cryptanalysis tasks.
The benchmark results published alongside this research show a clear capability gap between models:
- Mythos-class models solved 85.7% of benchmark tasks that had known solutions
- The weakest model tested solved 65.3%
That 20-point gap is significant. It suggests that frontier model capability at cryptanalysis is not a flat field — the best models are meaningfully better, and the spread will likely increase as models improve further.
CryptanalysisBench also serves a longer-term purpose. As AI models get stronger, the cryptography community will need a way to track how much stronger they are getting at finding flaws in encryption. Without a shared benchmark, those comparisons are anecdotal. With it, researchers can make apples-to-apples comparisons across model generations.
Anthropic has stated it plans to continue running CryptanalysisBench experiments to monitor how frontier LLM capabilities evolve in this area over time.
Sources:
- arxiv.org/html/2607.18538v1
- mlq.ai news article
---
Other Ciphers in the Crosshairs — LEA, Serpent, Salsa20
The HAWK and AES results were the headline findings, but Anthropic has disclosed preliminary results on several other algorithms.
Lightweight Encryption Algorithm (LEA)
LEA is an efficient block cipher built for low-power, resource-constrained devices. It is codified in the international standard ISO/IEC 29192-2:2019. The full cipher runs 24 rounds. The previous best attack on 13 rounds required 2^98 plaintext pairs and 2^86 operations.
Claude Mythos Preview developed a practical attack on 13-round LEA that:
- Recovers the key using fewer than 2^30 encrypted plaintexts
- Runs in under one hour on a standard desktop computer
This is a dramatic improvement. Because the attack runs end-to-end (you can choose a random key and watch the attack recover it), Anthropic is highly confident in its correctness. More analysis is still being done on edge cases and extensions to 14 rounds before full public release.
Serpent-128
Serpent was a finalist in the original AES competition and is considered highly conservative and strong. The full cipher uses 32 rounds. Published work attacking 6 rounds requires more than 2^70 plaintext pairs and 2^90 decryptions.
Mythos has identified a practical full key-recovery attack on 6-round Serpent-128 that extends and improves on the published results. Details are pending further analysis.
Salsa20, Poseidon, and SHA-1
Mythos has also found smaller improvements — described by Anthropic as "fairly limited" at less than 10× gains — on the Salsa20 stream cipher, the Poseidon hash function, and the SHA-1 hash function. These are less dramatic, but they show that the AI is producing results across a wide range of cryptographic primitives, not just the two headline cases.
Sources:
- postquantum.com/security-pqc/ai-cryptanalysis-hawk-aes/
- aes_mobius_bridge.pdf
---
What This Means for the Future of Cryptographic Standards
The Verification Bottleneck Is Real
The single most important practical insight from this research is not the attacks themselves. It is the discovery gap.
Mythos found the improved AES attack in roughly one week. Two Anthropic researchers spent nearly one month validating that the attack was correct. For a research team that did not specialize in cryptography, that month involved learning enough of the field from scratch just to check the AI's homework.
This asymmetry is going to get worse before it gets better. As models become more capable, they will produce novel cryptanalytic results faster. Human experts are not scaling at the same rate. The community will need new processes for faster validation — possibly including other AI tools used explicitly for verification.
What It Does and Does Not Change Today
To be absolutely clear on the practical stakes:
What is NOT affected:
- AES-128, AES-256, or any production version of AES in deployed systems
- Any current NIST-standardized post-quantum algorithms (CRYSTALS-Kyber, CRYSTALS-Dilithium, SPHINCS+, Falcon)
- Any encryption protecting your data today
What HAS changed:
- HAWK has been withdrawn from the NIST additional signatures process
- The cryptography community now has confirmed proof that frontier AI can find algorithm-level flaws in schemes that passed multiple rounds of expert human review
- The speed at which attack improvements on reduced-round ciphers can be discovered has increased significantly
A New Role for AI in Standards Work
Anthropic has framed these results as cryptography research working as it should — adversarial review catching problems before deployment. That framing is accurate. NIST's process is specifically designed for this kind of stress-testing.
The broader implication is that AI will become a standard tool in that process. Security teams, standards bodies, and algorithm designers will use AI models to conduct initial red-team reviews before submitting schemes for human scrutiny. The models will not replace human cryptographers, but they will dramatically expand the number of schemes that can receive serious analysis in a given year.
Expert consensus in the security community holds three points firmly:
- The HAWK result justifies withdrawal, but does not cast doubt on other lattice-based schemes with different mathematical foundations.
- The Möbius Bridge is a genuine theoretical advance in meet-in-the-middle techniques, not a practical threat to deployed AES.
- The pattern of rapid AI discovery followed by slow human validation will define the near-term future of cryptography research, and institutions need to prepare for it.
Sources:
- postquantum.com/security-pqc/ai-cryptanalysis-hawk-aes/
- news.geobrowser.io story
- mlq.ai news article
---
FAQ
1. Does the HAWK attack mean my current encrypted data is at risk?
No. HAWK was a candidate scheme under consideration for future standardization. It was never deployed in production systems. No software you use today relies on HAWK for encryption or digital signatures. Your internet traffic, banking data, and communications are not affected.
2. Does the AES Möbius Bridge attack break AES?
No. The attack targets a modified version of AES-128 that runs only 7 of the full 10 rounds. This reduced-round variant is a research tool, not a deployed cipher. The full AES-128 standard remains secure and is not affected by this research.
3. What is a post-quantum cryptographic algorithm and why do we need one?
Post-quantum cryptography (PQC) refers to encryption algorithms designed to stay secure even when large-scale quantum computers exist. Today's widely used public-key systems like RSA and ECDSA would be broken by a sufficiently powerful quantum computer. NIST has been running a multi-year competition to identify and standardize replacement algorithms before that threat materializes.
4. Why was HAWK withdrawn from the NIST process?
HAWK's designers withdrew the scheme after Anthropic disclosed its key-recovery attack. The attack reduces the effective security level of HAWK keys significantly — for example, dropping HAWK-256 from an expected 2^64 attack cost to 2^38. To maintain equivalent security, HAWK would need to double its key sizes, which would eliminate most of its efficiency advantages over competing schemes.
5. Does this attack affect other post-quantum algorithms like Falcon or CRYSTALS-Dilithium?
No. The HAWK attack exploits a specific nontrivial automorphism in the particular lattice structure HAWK uses. Other lattice-based schemes like Falcon rely on different mathematical constructions and are not vulnerable to this attack. Expert consensus is clear that this result is HAWK-specific.
6. How much did it cost Anthropic to discover these attacks?
Approximately $100,000 in API compute costs for each of the two main attacks — roughly $200,000 total for the HAWK and AES research. This is expensive by consumer standards but relatively modest compared to the cost of a traditional research program employing specialist cryptographers for equivalent periods.
7. What is CryptanalysisBench and how can I use it?
CryptanalysisBench is a standardized evaluation benchmark built by Anthropic in partnership with ETH Zurich, Tel Aviv University, and TU Berlin. It packages multiple cryptographic ciphers into a consistent testing environment so researchers can evaluate how well any AI model performs at cryptanalysis tasks. The technical paper is available at https://arxiv.org/abs/2607.18538.
8. How autonomous was Claude Mythos in finding these attacks?
Highly autonomous, especially for the AES result. The HAWK attack involved a human supervisor providing occasional non-technical project management guidance. The AES Möbius Bridge was found almost entirely by the model itself, with just three brief human prompts sent over three days of autonomous operation during which the model produced hundreds of millions of output tokens.
9. If AI can crack post-quantum candidates, how do we know any new algorithm is safe?
The fact that AI can find weaknesses is actually a feature of the standardization process working correctly. NIST's review process is adversarial by design — it wants researchers, both human and AI, to try to break candidates before any of them are deployed. Claude Mythos finding a HAWK weakness during the review process is the system succeeding, not failing. Standards like CRYSTALS-Kyber and Falcon that have already been finalized underwent this kind of rigorous scrutiny.
10. What happens when AI finds a vulnerability in an algorithm that IS already deployed?
This is the question Anthropic raised explicitly at the end of their disclosure. The current attacks do not reach that threshold, but the research community, government bodies, and industry need to develop clear policies for that scenario before it occurs. Anthropic has announced plans to host an academic workshop bringing together researchers from academia, government, and industry to begin those conversations. The disclosure process used for the HAWK attack — sharing with the algorithm's designers and coordinating public release — is one model, but it may need to evolve significantly if AI finds a flaw in something actively protecting billions of users.
Additional Links
Flowgrammer.ca – 💡 Unlock AI-Powered Automation! Let flowgrammer.ca handle complex workflows so you can focus on growing your business.
Flowgrammers.ca – 💡 Join Toronto's Fastest Growing AI and Business Automation Community.
- SRED Funding Solutions – Maximize your R&D tax credits and secure funding for your innovation.
- Silicon Scoop Podcast – Stay Informed, Stay Ahead!
- Startup Talk Podcast
- Flowgrammer Youtube
- Startup Investor Drinks – Join Toronto’s Startup Community and connect with fellow startup enthusiasts and investors.
- TorontoStarts Startup and Entrepreneur Community – Become a part of Toronto’s thriving startup ecosystem.
- Workhaus – Discover flexible workspace solutions for your business needs.
- Work with The Startup Coach – Get expert guidance and mentorship for your startup journey.
- Reach out to Jon Irwin on LinkedIn – Connect with our co-host and technology expert.
Episode transcript
Read the full transcript
Craig: nai spent sixty hours examining a post quantum security candidate that had already survived two years of human review and found a weakness serious enough to help knock it out of the nist competition. it also made a theoretical attack on a weekend version of aes up to 800 times faster. your banking encryption is safe, but cryptographic research may never work the same again. anthropic used quad mythos preview to develop two notable crypt analytic, results... crypt analytic results and improve key recovery attack against hawk, a proposed post quantum signature scheme, and a faster theoretical attack against seven round aes one twenty eight. the hawk work reduced estimated attack cost dramatically and led its designers to withdraw the candidate, while aes technique improved part of a meet in the middle attack by eliminating a 256 way guess. neither affects deployed systems. the real story is frontier ai can now produce original mathematical security research faster than humans can validate it. what do you think about this, john?
Jon: this is scary. i'm not surprised that we're... that ai is getting better and better at this stuff. so like you said, there's two completely different... what makes this story important is less that your bank account is suddenly vulnerable. it isn't. it's more that ai is becoming a new class of essentially a scientific researcher and security adversary. right? because that's... i like that. i like that they're using ai to find zero day vulnerabilities quicker. they're using it to find flaws, and all that. so i i think it's great. it also is scary if it gets into the wrong hands. so the two... like you've... like you said, the first involved hawk, which is a digital signature algorithm rather than an encryption algorithm. and so the way digital signatures work is, they prove things such as this software update really came from microsoft, or this transaction was really authorized by this key. and hawk was designed, like you said, as a potential post quantum signature scheme, something that should remain secure even if powerful quantum computers eventually compromise widely used systems such as rsa and elliptic curve cryptography. so both anthropics work, so before anthropics work, hawk had advanced to the third round, like you said, in nist's, additional digital signatures competition. so then the way hawk works is it partly... it depends partly on presumed difficulty of a mathematical problem involving lattices called the lattice isomorphism problem. so just very roughly, a lattice is a highly structured multidimensional grid. the public information reveals certain properties of the lattice while the private key contains information that is supposed to be computationally computationally infeasible to reconstruct. anthropic says, claude identified a previously unused symmetry, which is a nontrivial automorphism inside hawkes' mathematical structure. and previous research had already suggested that finding such a symmetry could enable an attack. but what had not been shown was that this exploitable symmetry could actually be found efficiently in hawkes' specific instruction. so, again, craziness, where ai, where ai can just advance research and testing and just... and do things. now let's talk about aes because aes is used all over the world. so it's called the events encryption standard. so it's, the symmetric encryption technology, and it protects enormous portions of modern computing. so, aes one twenty eight takes a 128 bit block of information and repeatedly transforms it through 10 rounds of substitutions, permutations, mixing operations, and key additions. whereas, aes one ninety two uses 12 rounds, and aes two fifty six uses 14. now one thing to note, claude did not break any of those production versions. so, claude called the underlying technique the mobius bridge involving mobius transform based way of matching intermediate states meet in the middle cryptanalytic attack. and so meet in the middle attack effectively computes forward from one side of a cipher and backward from another and searches for matching internal states rather than exhaustively testing everything end to end. now the caveat is enormous. like... so if anyone asks, did anthropic break aes, they... no. they improved an academic attack on a seven round version of aes one twenty eight. aes... real aes has 10 rounds, so they didn't break aes one twenty eight yet. but it's getting closer. i think we covered, an article on aes, like, an old version. i think it was, like, 64 or 32 bit that was cracked. right? and
Craig: yeah.
Jon: so we're getting closer and closer. what are your thoughts on this, greg?
Craig: it's faster and faster. we talk about, you know, vic, victor, the ethernet guy. ethernet guy. ethereum person. sorry.
Jon: vitalik?
Craig: buterin. vitalik buterin, and he... how he's hardening ethereum ahead of time and getting there. and we hope that everyone else is doing it as well and fast enough because the window keeps closing. a couple years ago, we had, you know, ten years or thirty year... or thirty years, and it was ten years, and it's five years. it... the window seems to be closing at how quickly we're gonna break aes and these other encryptions. so people need to be moving fast to these post, quantum encryption hardened technologies, and it's great to have tools like this that can challenge our encryption ideas before we do go too far down, implementation. it didn't... it took sixty hours to find the hawk exploit. right? and, you know, versus how many, other people have been looking at it for how long as people. anthropic estimates that it's a $100,000 in api costs, per main result. so it's not, you know, financially feasible for most people to run this kind of stuff. yeah. it says the a... aes work produced roughly 1,000,000,000 output tokens. so, if you're strictly talking api costs, you can look at those $25 per million output tokens or higher and say that's a billion tokens, and that's a lot of money if you're paying that way. for sure. so it depends. it's... i like that we have these tools to start hardening our encryption, and we're using it the right way now. i guess the concern is, you know, when does a hammer stop becoming a tool and start becoming a weapon? mhmm. you know, it's the same thing here. right? this... they stop this after, several rounds or sixty hours or a billion credits depending on which you want to look at it. what if they didn't? what if, for example, a nation state just grabbed it and let it run? how long would it take to... is it... you know, who cares if they say it takes three weeks? right? takes three weeks.
Jon: yeah. it's three weeks. like, it's nothing.
Craig: that's what i mean. like, sixty hours, we find these vulnerabilities. what happens if we keep letting it go? and that's what i mean by, you know, the... i'm glad we have these things, and we need to be putting, you know, some security control, a third party, or whatever who tries to do these things to make... to use ai to break our other ai or other system so that we can find the vulnerabilities and fix them. and, you know, should we be allowing this kind of stuff, to anybody, this level of ai? you know, you think the cat's out of the bag? i think the cat's out of the bag at this level, but doesn't necessarily out of the bag for every other update version moving forward.
Jon: the thing is, though, too, craig, like, this is what they're announcing to the public. right? what i've been not announced is my question. again, conspiracy theorist here. but, like, what... like, they're... like, there's gotta be something more that they're just not seeing that that was actually done, and they're just not announcing it because it's too volatile. that's my opinion, though.
Craig: yeah. and, you know, if you're hard to follow this, think of this like an ai, crash testing two vehicles. one was a prototype still waiting for safety approval, and the other was a laboratory version of a proven car with three of its 10 structural supports removed. so ai found some serious weaknesses in the prototype hawk and a smarter way to break, intentionally the weekend test vehicle, with the seven round aes, but it didn't actually break it. it just weakened it. so, you know, we talk about the risk of these things. we talk about exportation. if you're in the us and you're a us company developing this stuff, are you allowed to export this to canada? we're in canada. are you allowed to export this to australia? like, who... at what point is it, controlled enough and not controlled enough? who has access in those countries that can do stuff and not do stuff? like, that's what i mean by... it's not too late to start putting some regulation in. it's not too late to start putting some security companies in place that do these tests on a regular basis. it's not too late to do a bunch of things. it is too late to stop some of the stuff that's been leaked out already, but it's not too late to put some stuff in place as we move forward. i don't know, if we're moving a 100% in the right direction. we keep hearing we should pause by the biggest leaders, yet they're they're, you know, releasing models faster and faster. so i don't think there's gonna be a pause, and we know that other nation states aren't pausing. so, slowing down could be defense or militarily unadvisable.
Jon: yeah. yeah. but, again, it's scary it's scary where these models are going. and the other thing too that we didn't touch on is how semi autonomous this work was. right? so, like, that's the other scary part to this.
Craig: yeah. and so, basically, your bank account is safe, but the cryptographer's job or workload is not. yeah. claude mythos did not break today's encryption, but it demonstrated that ai can materially accelerate the search for tomorrow's cryptographic weaknesses. the unsettling part is not that ai found one flaw, is that generating discoveries may now be faster than building confidence in them. if an ai discovered a flaw in encryption used by billions of people, who should control when and how that discovery becomes public? let us know your thoughts below. we'd love to hear from you.
More from Silicon Scoop
All episodes
silicon-scoop · November 6, 2026
Spirit AI’s Robot Brain Breakthrough: Moz1, Embodied AI and China’s 2027 Race
The Spirit AI robot brain is one of the biggest bets on fixing that. Spirit AI is a Beijing startup. Its co-founder and chief scientist, Gao Yang,
View episode

silicon-scoop · November 5, 2026
OpenAI IPO Delayed to 2027 as Rogue AI Agents and Safety Failures Reshape the Market
OpenAI IPO delay explained: Sam Altman rules out 2026 as GPT-6 Astra safety tests and a $278B cash gap loom. Learn what founders should take away.
View episode

silicon-scoop · November 4, 2026
Anthropic’s AI Economy Model: 2030 Jobs, Wages, GDP and Market Risks
Anthropic AI economy model forecasts 2030 GDP, jobs and wages, while AI unemployment projections and labor-share risks challenge policymakers.
View episode
