GPT-6 Astra Breaks an Old Enigma Message

This is pretty amazing:

However, the most astonishing thing about this break is that the GPT­6 Astra did it entirely on its own. Carter Leffer only directed GPT­6 Astra to see if it could break any of the unbroken Enigma messages published on the Crypto Cellar Research web page. After analysing the unbroken messages on the website, it decided that the most promising message was Nr. 172, MVUEH and it also quickly suspected that the plaintext of Nr. 173, SIPVX, might be related to the plaintext of the unbroken MVUEH message. After trying many different approaches, GPT­6 Astra focused on using the repeated place name ROSENOW ROSENOW as a crib. After developing the necessary Python and C++ software for an Enigma simulator and an Enigma Bombe, GPT­6 Astra started a thorough break with the ROSENOW crib, which in the end resulted in the correct key and plaintext for the MVUEH message being found.

We are still analysing the GPT­6 Astra logs to see exactly how it executed the break. And we are discovering amazing details.

More details at the link.

Posted on September 22, 2026 at 7:02 AM • 11 Comments

Comments

Michael Donnelly • September 22, 2026 9:47 AM

“The file references GPT–6 Astra mentions…are correct, but they are not available on the Crypto Cellar Research website. GPT–6 Astra mentions a private collection, but it is not clear what this is, whether it has succeeded in accessing the Bundesarchiv’s digitised collections or whether it has found these files elsewhere.”

How is it that they can’t figure out where it got the file references? That seems like something that would be in the logs. At least the Bundesarchiv’s digitised collections, so accessing them there wouldn’t involve hacking into anything.

Frode Weierud • September 22, 2026 10:40 AM

It is doubtful that the Bundesarchiv files were important to the MVUEH break; however, I found it interesting to see how far GPT-6 went in acquiring information from primary sources. I do not have access to all the logs from the break; only Carter Leffen has that information. That’s why I don’t know exactly where GPT-6 found the two files RS 3-3/20a and RS 3-3/63b. It is possible that it registered a researcher account with the Bundesarchiv and got access that way. However, I am not sure chatbots are allowed access to the Bundesarchiv.

Yesterday, I learned that the MVUEH break inspired another attack on one of our unbroken Enigma messages. On 20 September 2026, the 63-letter-long Enigma message Nr. 205 NF / Nr. 285 FMNGI of 31 July 1941 was successfully broken with the help of Anthropic Claude Opus 5. This attack also used a crib, or known plaintext, to break it. In this case, the crib was XHARTJENSTEINX, a very frequently occurring signature.

Zsolt • September 22, 2026 1:41 PM

The Veritasium YT channel came out with a video on Enigma just the other day. 🙂

They dared viewers to decrypt a message that has not yet been deciphered to this day:

“Can you decrypt this unbroken Naval Enigma message? Let us know in the comments!
JCRSAJTGSJEYEXYKKZZSHVUOCTRFRCRPFVYPLKPPLGRHVVBBTBRSXSWXGGTYTVKQNGSCHVGF”

DBA • September 22, 2026 2:21 PM

That’s so cool! The fact that it created a Bombe to help with the decrypt blows my mind and harkens back a few decades for me. I read a book about the work that went into saving the Polish Bombe equipment and researchers when Germany began advancing against Poland, them providing the foundations for Turing’s later success in breaking Enigma.

I wish I knew what book that was, it’s long gone from my collection.

Dan • September 29, 2026 8:05 AM

@Frode Weierud,

“and the break revealed that the Enigma’s left-hand wheel makes a turnover at the 72nd letter. A turnover of the Enigma’s left-hand wheel, which rarely occurs, is known to complicate a break.”

What do you mean here exactly? Leftmost wheel turnover isn’t rare, it depends on wheel selection and position.

smells like a hoax • October 1, 2026 8:29 AM

I don’t believe that GPT-6 did all this by itself.
OpenAI plans an IPO, all those stories serve that goal and that goal only.

It is more plausible that human guided that research process and log was later constructed by AI itself. Claiming that “our AI did all this by itself” serves only one purpose, to raise the company value. Capitalism, remember?

Sami Liedes • October 2, 2026 1:11 PM

I stared a bit at the NEUEM message from 25.7.1941. I believe I have a solution.

There’s a claimed break of a shorter message, CPUDN, from the same day. NEUEM can be decrypted with the same key after some corrections.

Cryptocellar does not seem to publish anything but claims of something being broken, which annoys me. The CPUDN key, if it indeed was broken, would have been quite helpful here.

Cryptocellar gives the message as

NEUEM RWKKD ENLAT NYYBU
OOHVE OAAST ZTPRO ZCKIV
CFDYZ VUPCB XBSVB XSLTR
LVDMY RCFDA YALE

Though I believe we have

NYYBU -> NYRBU
ZCKIV -> ZCKIW

In addition, I suspect there’s a missing group in the middle, and the last group is not part of the message, making the length correct again:

NEUEM RWKKD ENLAT NYRBU
OOHVE OAAST ZTPRO ZCKIW
—– CFDYZ VUPCB XBSVB
XSLTR LVDMY RCFD

Given the key

EFQCV PBOWG
LHOAT RLUZI
KRIDZ EVNFA
XNYUM KSMXY
SPGWB DTCHQ

this message decodes as

KOLONNEFUERKORPSNACSQUBWIRDIMLAUFEVNSNAQ——INMADSQGESETZTXHARTIIENSAPIN

which I would read as

Kolonne für Korps Nachschub wird im Laufe des Nach… in Marsch gesetzt. Hartjenstein.

or

The corps supply column will be dispatched during… (the afternoon?). Hartjenstein.

(I’m trying to fit “Laufe des Nachmittags” there, but it’s one letter too long.)

All the typo fixes I propose, apart from the group shift, are one-letter cryptogram changes.

Given the same key, they CPUDN message decrypts as:

STANDORTXLGXXNISYXNXEYXMATKIATTX

which I read probably as

Standort ?? Nisy. Mattiatt.

An one-letter change to the cryptogram would allow “STANDORT X LNK X”, which would make sense as Luftnachrichten-Kompanie = Air force signal company.

Sami Liedes • October 2, 2026 2:07 PM

To be clear, that’s one of the Truppenschlüssel messages, not one of the Enigma ones. It’s a hand cipher, a kind of double Playfair, but an easier version than what you often see because the letters are not reordered in any way before encrypting. You encrypt each digram separately, so it becomes a monoalphabetic substitution for 625 digrams. I’ve been looking into the unbroken TS messages, but the rest still defy me. I have some ideas and, to be honest, I’m running a bit out of steam after staring at this for a few days:

  • A lot of the messages repeat place names and similar. If they repeat at an even offset, we just get repeated ciphertext. If they repeat at an odd offset, we get a digram relationship:

BI RM IN GH AM XB IR MI NG HA M?

Assume a ciphertext contains that text. Furthermore, assume we have a candidate plaintext that we want to score. I think we have here an underexplored metric: Index of coincidence between the plaintext digrams starting at even positions and the plaintext digrams starting at odd positions. This attacks the structure without taking a position on the actual letter identities.

  • In all messages encrypted with the same (usually daily) key, we see similar digrams because the German plaintext is not random and because the digrams encrypt identically. This actually makes it quite easy to determine which ciphertexts share a key. If you look at, for example, the July 8 messages, other than the unbroken VHRNE, in the broken messages a lot of the ciphertext digrams appear in other messages of the day, whereas for the unbroken VHRNE it’s much less (intact or after shifting by one letter), close to random. This I think is pretty strong evidence it’s not encrypted with the same key (or cipher). The same is visible in leave-one-out cosine similarity to the remaining pool.
  • This can also be used to detect likely one-letter insertions/deletions in ciphertexts.
  • There are also statistics that the ciphertexts share even when the key differs. Consider, for example, the sorted histogram of the 625 digram frequencies (throwing away the digram identities). For correctly encrypted messages, they’re exactly identical regardless of the key, and also the exactly identical to that of the plaintext. I would expect Enigma messages, for example, to look much more random.
  • As a wild idea, you could use the frequencies, and the frequencies of transitions between (unlabeled) digrams (i.e. a Markov process). Labeling the digrams with their plaintext digrams, ignoring for now the extra constraints to digram substitution that Truppenschlüssel gives us, is a noisy weighted graph-matching problem. This is akin to humans looking at repetitions and other structure in the ciphertext and making guesses.

Leave a comment

Blog moderation policy

Login

Allowed HTML <a href="URL"> • <em> <cite> <i> • <strong> <b> • <sub> <sup> • <ul> <ol> <li> • <blockquote> <pre> Markdown Extra syntax via https://michelf.ca/projects/php-markdown/extra/

Sidebar photo of Bruce Schneier by Joe MacInnis.