News

Claude helped explain the origin of the ECDSA parameter, without breaking the encryption

Anthropic says an internal research model traced the origins of cryptographic curve parameters. It stresses that no encryption was broken and some questions remain open.

A glittering curve passing through transparent crystals next to a conceptual clock.
Illustration: A glittering curve passing through transparent crystals next to a conceptual clock

Anthropic reported on October 16 that Claude's internal research model helped investigate how the parameters of the curves used in the ECDSA digital signature standard were generated. According to the company, the finding explains part of the parameter creation process that has been unclear for years. It emphasizes that this is not an encryption breach, a new attack or a vulnerability discovered in the curves, and there is no need to change the use of systems because of this result.

The company says the model identified the origins of the seeds for 5 NIST curves over prime fields in less than half an hour. Among the curves is P-256, alongside P-192, P-224, P-384 and P-521. The explanation refers to how to create public parameters. It does not provide a way to extract a private key from a public key, and does not make another person's signature something that can be forged via chat.

The historical question behind the parameters

ECDSA is a digital signature mechanism based on the mathematics of elliptic curves. To use it, you have to agree on parameters that define the curve. Some of these values were previously published with initialisation values, called seeds, without a full explanation of their origins. Because the selection came through the NSA, the lack of explanation raised questions in the cryptographic community about the selection process and its reliability.

Such a seed is neither a user password nor a private key. It's part of the information used to define shared and public parameters. This distinction is important for understanding the find: an explanation of how a standard number is created can shed light on the design history, without compromising the secrecy on which a particular signature relies. The disclosure of the source of a public parameter is not equivalent to the disclosure of a secret key.

According to Anthropic, earlier experiments with its employees focused on the possibility that values were created from textual expression. The model examined another direction related to software from the time of standardization. The company published the explanation and the means to reproduce the match. The important point is that the claim goes beyond a verbal model response: it identifies a mathematical relationship that can be tested against previously published values.

What's found, what's not yet explained.

According to the company, the seeds studied are linked to an old pseudorandom generator called lrand48, initialised using timestamps. The explanation provides a way to recover the relevant parameters. The details of the mechanism do not make it a recommendation for creating secrets today: its function here is to explain a historical choice of public values. This does not imply that generating private keys using a clock will be a secure method.

The study also leaves open questions. Anthropic identifies 1 unexplained binary-curve seed and base points of several curves whose origins have not yet been reconstructed. In addition, some runs skipped possible candidates for reasons that remain unknown. Therefore, it is correct to talk about a meaningful explanation of some of the parameters, not a full reproduction of every decision made when creating the standards.

The company estimates that the findings reinforce the assurance that the curves were not selected to include deliberate weakness. This is the researchers' conclusion based on the explanation they provided, and not proof that any system using ECDSA is protected from any problem. The security of an application also depends on how keys are stored, signatures are constructed, and permissions are handled. The study of the source of the parameters is not a security check for any software that implements the standard.

How to understand Claude's role

Anthropic describes the use of an internal research model. There is no notice that this particular ability is equally available to every Claude subscriber, or that every user will get the same result in a short question. What is described is a research process around a defined problem, with public values that can be compared to. The product name alone is not sufficient to determine what the result will be in any other usage environment.

The example is interesting because it connects proposing hypotheses with testing them. A model can suggest a relationship between details that are difficult to identify at first glance, but scientific value is created when it can be tested to see if the relationship actually explains the data. There are precise target values here. Matching them is a different question than whether the explanation sounds convincing to the reader. Even a very eloquent text can present a false assumption.

For researchers and developers, this is a reminder to plan a verification method in advance. Before assigning a technical question to a model, it's good to know which results would support the proposition and which would discredit it. If the answer requires a mathematical test or experiment, a verbal description of the model will not replace them. The use of AI can assist in the search, without transferring to it the authority to determine that the search was successful.

What security managers and users should do

The immediate response to the announcement should be to keep it in perspective. Anthropic itself says there's no need to change because of the find. There is no reason to reset passwords, replace certificates or stop using signatures simply because a headline mentions AI and cryptography. Such decisions should be based on relevant warnings, supplier guidance, and the state of the particular system, not on a mixture of the two types of research.

Professional teams should distinguish between the source of standard parameters, their mathematical strength, and their implementation accuracy. When assessing an organisational system, teams should continue the updates, access controls and key protection that it requires. These are general operational recommendations, not a fix to a new vulnerability discovered in the current release. The finding does not provide a basis for changing the urgency of treatment for another problem.

A calming result, with clear boundaries.

The question being investigated is not whether Claude can break into any signature system. The question is whether it is possible to explain how public numbers were chosen when parts of their history were not clearly documented. According to Anthropic, the answer for a significant number of them is yes. The explanation reduces historical uncertainty, while at the same time detailing where gaps remain. Both parts are necessary to understand the result.

For readers in Israel and elsewhere, the practical significance is a research finding and an example of using AI alongside precise verification. There is no warning about the loss of protection in a particular service or the compromise of accounts. When the proposition is kept within its boundaries, one can see the contribution without exaggerating it: understanding the origin of parameters, with findings that can be tested, and with questions left open for further work.