- Eight private keys belonging to Indian certificate authority eMudhra were compromised, potentially allowing attackers to forge certificates and impersonate trusted websites.
- Major browser makers quickly blocked the certificates, and no attacks have been reported, but some nonbrowser software may remain vulnerable because it does not check whether certificates have been revoked.
- Researchers said eMudhra used easily guessed integers as private keys, enabling all eight to be recovered from public certificates in under a second.
The internet has been scrambling to patch a hole in the system that tells your browser which websites are real. The risk is general and falls mostly on people running outdated softwares, crypto users included.
It started on Oct. 17, when a researcher told browser makers that eight secret keys at eMudhra, an Indian company that vouches for websites, have been compromised.
A researcher named Wayne reported the security flaw and to prove the vulnerability, he used all eight compromised keys to digitally sign his warning message: "We have a problem here – Wayne."
When a user visits a website, their browser checks a digital certificate to confirm the site is real. Companies called certificate authorities issue those certificates, and eMudhra is one of them. It has issued more than 60 million certificates, according to The Register.
Each certificate authority signs its certificates with a private key. Think of it as a master stamp. If someone steals or cracks that stamp, they can forge authentic-looking certificates for any website.
Crypto users could also be affected, though mainly outside the browser. Exchange bots, trading scripts and wallet backends often run on Python, Node or Go, and a forged certificate for an exchange’s API could in theory let an attacker on the same network read or alter a bot’s traffic. No crypto attacks have been reported so far.
But according to Mudit Gupta, chief technology officer at Polygon Labs, the bigger concern is not crypto itself, it is outdated software.
“This is not a crypto-specific issue,” Gupta told CoinDesk. “It is a generic issue that can be exploited for man-in-the-middle attacks, particularly against users running older or unpatched software. Crypto users who keep their wallets, trading tools and devices updated face lower risk, but the broader software ecosystem remains a concern,”
CoinDesk contacted eMudhra for comment.
Emergency fixes
Browser makers and software developers have pushed out emergency fixes. Mozilla got the report just on Oct. 17 after 8 p.m. UTC and had a block in place about three hours later. Chrome blocked the certificates the same day. Apple followed on Oct. 19 and Microsoft on Oct. 20. eMudhra has also revoked them.
Mozilla browser warned that network interceptors could use these fraudulent certificates to impersonate trusted sites, allowing them to read or alter the user's data.
How the keys got out is still unclear.
"According to researchers, eMudhra used tiny integers like 4, 56, and 237 as private keys instead of strong 384-bit random numbers," Cyber Security News said on X.
Security researcher Scott Helme went further.
"One of eMudhra's certificate authority private keys is the number 4," he wrote. "Another one is 56, and another is 115."
A proper key is a huge random number that no one could guess. Helme says he recovered all eight from public certificates in under a second, and that the keys have been exposed since April 2025.
The exact mechanics of how this disaster happened were laid bare in Mozilla's Official Security Bulletin. Helme's reading of a Mozilla bug ticket says eMudhra blamed a bug in its key-setup script.
The real worry lies outside the browser. Many programs never check whether a certificate has been revoked. "So the fact that eMudhra and Sectigo have revoked these intermediates doesn't help them at all," Helme wrote.
He says his tests showed tools like curl, Python, Node, Go and Java accepted a forged certificate for Stripe's API. Fixes are out for Go, Python's certifi package and Rust's webpki-roots. Node.js was still pending when last checked.
