25-Year Mystery Solved: NIST Elliptic Curve Seeds Came from lrand48 and Unix Timestamps
For 25 years the cryptographic community wondered about the provenance of the SEED values published alongside the NIST elliptic curves in the FIPS 186-2 standard. These seeds determine the curve coefficient b through a hash function, yet the NSA provided them without any explanation of their origin.
Early speculation suggested that long-time NSA employee Jerry Solinas had produced the seeds by hashing humorous internal phrases such as “Give Bob and Jerry a raise.” That theory remained unverified after Solinas’s death in 2023.
Claude identifies the true source
Engineers at Anthropic asked the internal research model Claude to investigate without supplying the old rumor. Within minutes the model recognized that the published seeds matched output from the lrand48 generator in the C standard library, initialized with Unix timestamps.
The generation process worked as follows: the generator was seeded with a Unix time t, then 20-byte candidates were extracted every 20 calls. The published seed for NIST P-256 corresponds to the 1842nd candidate produced on 16 August 1997 at 01:52:34 UTC. Similar timestamps between May 1997 and April 1998 account for all five prime-field curves.
Base points also traced
Base points for six curves created in May 1997, including P-192 and several ANSI X9.62 examples, were generated by the random routine inside FreeLIP, Arjen Lenstra’s long-integer package. The starting seeds for that generator (20000, 20420, etc.) have now been recovered and reproduce the published points exactly.
Implications for trust
The discovery shows that the curves were chosen by a weak, publicly reproducible process rather than by any sophisticated backdoor insertion. While a few valid candidate curves were skipped and one binary-field seed remains unexplained, the overall methodology leaves far less room for hidden weaknesses than previously feared.
The full reproduction code, written in Python, has been released under CC0 and confirms every recovered seed and base point.
Related articles
Peter Levashov Accused of FBI Collaboration and Running XSS Honeypot Forum After Kelihos Sentence
Russian spammer and botnet operator Petr Levashov, known online as Petr Severa, was arrested in Barcelona in 2017 and later pleaded guilty to running the Storm, Waledac and Kelihos botnets. He received a lenient sentence of under three years despite prosecutors seeking 14.5 years, which experts attribute to possible cooperation with the FBI. After release, Levashov remained in the United States while remaining wanted in Russia. Forum users bratva and stallman on XSS.mx and Exploit.in have been linked to Levashov through stylistic analysis and shared references to the Telegram channel Dark News admin nicknamed golub. Stallman, identified as the final administrator of the RAMP4u forum, openly purchased access to U.S. critical infrastructure including power grids, water systems and hospitals while moderators allegedly suppressed competing posts. Observers including researcher Olga Kuprina suggest these accounts operated under agreements with U.S. authorities, allowing forums to function as intelligence-gathering platforms rather than purely criminal marketplaces.
Russian Cybersecurity Market Set to Hit 455 Billion Rubles by 2026 as Talent Shortage Persists
MWS Cloud forecasts that the Russian information security market will grow 20.8 percent to reach 455.4 billion rubles in 2026. The largest segment will be software at 216.5 billion rubles, followed by services at 167 billion and hardware at 71.9 billion rubles. Demand is increasingly driven by sophisticated attacks, regulatory requirements and fines rather than import substitution alone. BI.ZONE offers a more conservative estimate of 10-15 percent annual growth. Managed security services such as monitoring, incident response and vulnerability management are leading the services segment because few organizations can maintain 24/7 in-house teams. Director Artem Gribkov of Angara MTDR estimates the personnel deficit at approximately 40 percent, especially at middle and senior levels.
Russian Internet Users Report Growing Access Restrictions as Certificate Revocations Affect 39 Percent of Respondents
A recent telephone survey conducted by Russian Field between September 23 and 30, 2026, among 1,600 participants representative by gender, age, federal districts, and settlement types shows that 39 percent of Russian internet users have noticed restrictions or complications when trying to access websites. When sites fail to open due to certificate problems, 26 percent of respondents said they would simply stop visiting the resource. The findings, published by Kod.ru, also indicate that 57 percent of users are aware that Russian websites may not load in certain browsers because of revoked foreign certificates. In response to certificate errors, 55 percent would switch browsers, 22 percent would install the required certificates, and 21 percent would try accessing the site from a mobile device. Younger users are more inclined to use VPNs or proxies, while older respondents more often choose to abandon the site. Overall, 77 percent of those surveyed expect further changes to the Russian internet segment, with only 9 percent believing it will remain unchanged.
CISA and NSA Urge Shift to Memory-Safe Languages Like Rust to Eliminate Memory Vulnerabilities
Official reports from CISA, NSA, FBI and partners highlight that decades of safe coding practices and code analysis tools have failed to resolve memory safety issues in languages such as C and C++. Government documents cite statistics showing that 70-75% of exploited vulnerabilities and zero-days stem from memory errors, including data from Microsoft, Google Chromium, Mozilla and Project Zero. Google reports that Rust adoption in Android reduced memory-related vulnerabilities below 20% in 2025, with a 1000-fold lower vulnerability density compared to C++. The analysis details Rust's ownership, borrowing and move semantics that provide compile-time guarantees unavailable in C++, enabling stronger compiler optimizations. Reports also acknowledge migration challenges including learning curves, interop issues and ecosystem gaps, while noting ongoing C++ safety improvements targeted for C++26 and C++29. Major organizations including Microsoft, Amazon and Google are already committing to Rust for critical new code.