In brief

  • What happened: On October 16, 2026, Anthropic said an internal research model worked out how NIST’s curve seeds were generated.
  • The answer: Not a hashed phrase, but lrand48 seeded with the computer clock in 1997 and 1998.
  • The risk: None. Anthropic says it is not a break; it matters most to security people and developers.

For almost three decades, nobody could explain where a handful of long numbers handed from the NSA to NIST came from. According to Anthropic, Claude cracked it in under half an hour.

AI Desk · Published October 17, 2026
First look: this story is based on Anthropic’s official post. Maitz ran the published code and got the P-256 seed back out of it, but did not check the rest of the findings.

What was the mystery behind ECDSA curve seeds?

ECDSA is a digital signature standard built on elliptic curves. NIST adopted it in 2000 in FIPS 186-2, along with a list of ready-made curves. Each curve came with a published “seed”: a 160-bit value that one of the curve’s parameters is derived from.

The NSA supplied those seeds and never said how it picked them. That left room for an old suspicion: maybe they were chosen on purpose to hide a backdoor. The best-known explanation was that Jerry Solinas at the NSA had hashed a joke phrase, something like “Give Bob and Jerry a raise.” Solinas died in 2023, nobody ever recovered the phrase, and the question was open enough that someone put a cash bounty on it.

What did Claude find?

Anthropic says several of its employees had already chased the joke-phrase lead and gotten nowhere. This month, another employee asked an internal research model to figure out how the seeds were made, without mentioning the rumor. In less than 30 minutes it had the answer for P-192, P-224, P-256, P-384 and P-521.

None of the seeds came from a hash. They were raw output from lrand48, a pseudorandom number generator that shipped with 1990s C libraries, started from a Unix timestamp. The program pulled 20 bytes at a time, and each batch was a candidate seed. The P-256 seed in the standard is candidate number 1,842.

How it got there is the fun part. Claude guessed the original software leaned on an old, weak generator whose output can be recognized. It wrote a scanner and tested 34 combinations of generators and output slices. Then it spotted something odd: in four of the ten seeds, the top bit of every one of the 20 words was zero. The odds of that happening by chance are about 1 in 5,810. That pattern is a fingerprint of lrand48.

From there it rebuilt the generator’s internal state, using the LLL lattice algorithm for some of the curves, and ran it backwards to the moment it was started. Every timestamp for those curves landed between May 1997 and April 1998.

DetailPer Anthropic
Seeds explainedP-192, P-224, P-256, P-384, P-521, five example curves from ANSI X9.62, and four binary curves (with a caveat)
Time to answerUnder half an hour
Where the seeds came fromlrand48, seeded with a Unix timestamp
DatesMay 1997 to April 1998
Still openThe B-163 seed, and the base points of P-224, P-256, P-384 and P-521
Bounty$36,864, to be donated to ISRG

So is the crypto broken?

No. Anthropic is blunt about it: this is not a break, not a new attack and not a flaw in the curves. If anything, the company says, it makes a backdoor less plausible. A plain generator seeded from the clock, which anyone can now reproduce, leaves very little room for anyone to steer the result.

There was a bonus, too. Claude also explained the base points of six curves from 1997, including P-192. Anthropic says they came from the random-number generator in FreeLIP, a library written by cryptographer Arjen Lenstra. As far as the company knows, no NIST base point had ever been explained before.

What we still don’t know

  • Why some valid candidates were skipped. For P-256, candidate 876 would also have produced a suitable curve, and it’s unclear why 1,842 won. Anthropic says the number of skips is too small to suggest someone hunted for a weak curve.
  • How many times the program was run. The numbers alone can’t tell you.
  • Where the B-163 seed and the base points of the larger curves came from.
  • Which model did the work. Anthropic only calls it “an internal research model.”
  • Any response from NIST or the bounty organizer. The post doesn’t include one.

What it means for you

  • Everyday users: Nothing to do. Your sites and apps don’t need any changes, and Anthropic says no action is required.
  • Security folks and developers: The post includes a few lines of Python that regenerate the seeds. We ran it, and it produced the P-256 seed exactly as it appears in the standard.
  • The bigger picture: AI models are starting to close real open questions, not just write code. For more on Anthropic’s security work, read about Cyber Mission, and look up terms like hash and PRNG in the Maitz glossary.

Sources

  • Anthropic: Claude reveals ECDSA curve origins, anthropic.com/research/ecdsa-curve-origins, October 16, 2026
  • Verified: October 17, 2026