← Back to Blog
Online Trust Explained Simply India

The Password Was "4": How India's Biggest Digital Signature Company Left the Door Open

eMudhra is one of the companies that vouch for websites, so your browser knows a site is real. This month we found out that eight of its secret keys were so small that anyone could work them out in under a second. I've tried to explain what went wrong in plain language, with pictures, and what you should actually do about it.

Krishna Muduli, CISSP Cybersecurity Lead Engineer October 25, 2026 12 min read
eMudhra Certificate Authority Private Key Compromise: Secret key was 4 in high-security HSM vault

I read a lot of breach reports. Almost always, someone breaks in and steals something. This one is different. Nobody broke in and nothing was stolen. The secret was just too easy to guess, and it stayed that way for about 18 months before anyone noticed.

4
The smallest of the secret keys
< 1 sec
To work out all eight on a laptop
8
Weak keys, made in April 2025
~30,000
Website certificates that now need replacing
⚠️

This story is still moving. Browser makers are still asking eMudhra questions, and a few details are disputed. I've written this with what was known on 25 October 2026 and I'll update it if anything important changes.

The short version

Who
eMudhraIndia's biggest digital signature company
What went wrong
8 weak secret keysTiny numbers instead of huge random ones
Were they stolen?
NoThey were made wrongly in April 2025
Who found it
An outside researcherReported on 17 October 2026
Any real harm?
None confirmedAs of 21 October, per CERT-In
ITR, GST, Aadhaar eSign
Not affectedThey run on a separate system

First, what does eMudhra actually do?

When you open your bank's website, your browser shows a small padlock. Before it does that, it checks the website's ID card, which is called a certificate. A certificate is only accepted if a trusted company has stamped it. These companies are called Certificate Authorities, and you can think of them as the internet's passport office.

eMudhra is one of them. In India it is the biggest, and it also handles the digital signatures many of us use for income tax returns and company filings.

A detail that matters for this story: these companies don't use their main stamp every day. They lock it away and use helper stamps for routine work. Your browser trusts the helper stamp because the main stamp vouched for it. It was eight of these helper stamps that went wrong.

A professional viewing an authenticated banking portal with secure green SSL padlock and cascading digital certificate trust seals

Figure 1: The Invisible Chain of Internet Trust. When you visit a secure portal, your browser silently verifies a cryptographic chain leading back to a trusted Certificate Authority (Root CA). If any intermediate helper stamp is compromised, the green padlock can vouch for a counterfeit destination without warning.

How your browser decides to trust a website

Anyone holding a helper stamp's secret key can stamp a fake ID card for any website

MAIN STAMP eMudhra's root built into your phone and computer HELPER STAMP one of eight secret key = 4 anyone can work it out REAL ID CARD shop.example.in asked for properly ✓ padlock criminal uses key 4 FAKE ID CARD yourbank.com bank never asked ✓ padlock anyway What the browser checks Is every stamp genuine, all the way up to the main stamp? It can't tell who used the stamp.

Where the number 4 comes in

Each stamp is protected by a secret key. The key is just a number, a bit like the combination of a lock. The difference is the size. A proper key for these stamps is a random number about 116 digits long.

There is also a public part, printed on every certificate. It is made from the secret key using maths that only works in one direction. Think of mixing two paints: easy to mix, impossible to separate again. So everyone can see the public part, and nobody can work backwards to the secret.

That only holds if the secret is too big to guess. eMudhra's weren't.

A proper secret key, and the one eMudhra used

On paper, both count as the same strong type of key

What a proper key looks like (a random example)
15353124019583485789644065193272070237940033605886008641414640413100860782551841243333330280571964062611491206894155
What one of eMudhra's keys actually was
4the other seven were 56, 66, 115, 155, 156, 230 and 237
How much guessing it takes, drawn to scale
Proper key384 bits
eMudhra's biggest (237)8 bits
The key "4"3 bits
NeverGuessing a proper key would outlast every computer on Earth
255 triesEnough to check every number below 256
< 1 secondTime it took a researcher on a normal laptop

"Bits" is how security people measure guessing effort. Each extra bit doubles the work. The example key above was made for this post and isn't used anywhere.

The odd part is that from the outside, nothing looked wrong. I made a test certificate with the secret key set to 4 and opened it with the standard tool. It reported a full-strength 384-bit key, the same as a healthy one. The type of lock was right. The combination was terrible, and the certificate gives you no way to tell.

How did a tiny number end up there?

Creating new keys at a company like this is a formal event called a key ceremony. People meet in a secure room, follow a written script, and the keys are made inside a tamper-proof hardware box. Based on what eMudhra has told Mozilla, this is roughly how it went wrong:

High-security cryptographic key ceremony in an air-gapped facility with hardware security module and dual-control security auditors

Figure 2: Inside a Cryptographic Key Ceremony. Generating institutional root and intermediate signing keys requires air-gapped vaults, dual-custody smart cards, and Hardware Security Modules (HSMs). The hardware flawlessly protected the generated keys—it simply protected an erroneous second set of single-digit test keys due to a procedure mix-up.

From the key ceremony to the discovery

Green went to plan, amber was risky, red is where it went wrong

01
30 April 2025
Strong keys are madefine
eMudhra holds a key ceremony to create 24 new helper keys inside a high-security hardware box. The keys come out strong, as they should.
02
Same day
An extra test is addedrisky
These keys were meant to be exported, so the team adds a step that isn't in its usual script, to test packing the keys up and unpacking them again.
03
Same day
A bug makes a second, weak setwrong
A mistake in the test code creates another batch of keys, and these are tiny numbers. Exactly how that happened is still being questioned.
04
Same day
The wrong keys get pickedwrong
The weak keys had names very similar to the strong ones. The weak ones were used by mistake, and nobody checked the keys themselves, only the names.
05
April to May 2025
Eight weak stamps go livewrong
Six are for websites and two are for signing software. Another big company, Sectigo, also vouches for all eight in May, which spreads the trust even wider.
06
June 2025
A clue is missedmissed
Some files signed with the "strong" keys didn't match the certificates, which was a hint that the wrong keys were in use. The files were re-signed with the weak keys and everyone moved on.
07
17 October 2026
A researcher noticesfound
A researcher known as "Wayne" works out all eight keys and reports it to Mozilla, the company behind Firefox. To prove it, he signs a message with each one.

What stays with me is that the expensive security box did its job. It kept the keys perfectly safe. It just kept the wrong keys safe. No hardware protects you from a mistake in the steps people follow.

How easy was it to guess?

Very. You don't need any hacking skill. You take the public part from the certificate, which anyone can download, and try the secret numbers one by one: is it 1? 2? 3? Each try takes a fraction of a millisecond.

Guessing the key by counting

Try each number until the result matches what's printed on the certificate

try 1 try 2 try 3 try 4 ✓ a proper key would hide somewhere on a 116-digit-long circle The certificate Helper stamp: EM OV TLS Public part: (printed) Anyone can download it → matches on try 4
Try 1✗ no match
Try 2✗ no match
Try 3✗ no match
Try 4✓ key found

The biggest of the eight keys was 237, so 237 tries was the worst case.

Scott Helme, a well-known security researcher, was one of several people who tried it once the news broke. He wrote:

"One of eMudhra's certificate authority private keys is the number 4. Not a number that starts with 4… just, 4. […] I recovered all of them from their public certificates on my laptop just now, and it took less than a second."

Scott Helme, security researcher

So what could a criminal do with it?

The keys don't unlock anyone's data by themselves. What they let you do is pretend to be any website. A criminal could make a fake ID card for your bank, your email or a government portal, and your browser would accept it.

To use it, they would also need to sit between you and the internet, for example on a fake public Wi-Fi network or a hacked home router. Then it looks like this:

Public airport Wi-Fi network traffic interception console showing forged SSL banking certificate displaying fake valid padlock

Figure 3: Man-in-the-Middle Interception at Transit Hubs. On untrusted public Wi-Fi (such as airports or cafes), an attacker possessing intermediate signing keys could silently forge an authentic-looking certificate for any domain. The victim's browser displays a reassuring padlock while credentials and session tokens are captured in transit.

A criminal in the middle, with a fake but "valid" ID card

You still see the padlock the whole time

YOU phone or laptop 🔒 yourbank.com fake card CRIMINAL fake Wi-Fi or hacked router fake ID card for yourbank.com reads everything, passes it along real card REAL BANK thinks it's talking to you Passwords, OTPs and login sessions all pass through the criminal
🎭
Fake any websiteBanks, email, shopping sites, government portals. The padlock would still show.
🔑
Steal logins and OTPsEverything you type passes through the criminal before it reaches the real site.
📦
Make malware look officialTwo of the keys were for signing software, so a harmful app could look like it came from a real company.

Did anyone actually misuse it?

As far as anyone knows, no. CERT-In, India's cyber security agency, said on 21 October that it had seen no attacks. That fits with how fast the browsers moved, which I cover next.

People did show how easy it was, though. Within days of the news, more than 100,000 test certificates made with the leaked keys appeared in public logs, most of them pretending to be google.com. They were proofs that it worked, not attacks. Still, it tells you that once a key like this is known, anyone can use it.

What happened once it was found

One week in October 2026

17 OCT · EVENING
Reported to Mozilla
The researcher shares proof that all eight keys can be worked out.
17 OCT · LESS THAN 3 HOURS LATER
Firefox blocks the eight stamps
Chrome does the same that day, according to reports.
18 OCT
eMudhra cancels them
The company says it did this within 14 hours of finding out.
19 – 20 OCT
Apple and Microsoft follow
Sectigo also withdraws its backing for the eight stamps.
20 OCT
Mozilla stops trusting the main stamp too
Not just the eight helpers. Google says Chrome will do the same on 27 October.
21 OCT
The Indian government responds
CERT-In issues a high-severity advisory. MeitY says digital signatures and eSign are not affected and sets up a team to look into it.
22 OCT
eMudhra quits the website certificate business
It says this was about 1% of its revenue. Its other services carry on.

The browsers moved quickly, which is reassuring. The part I'd underline is 20 October. Mozilla went further than blocking the eight bad stamps. It stopped trusting eMudhra's main stamp for this whole family of certificates. When the problem is how a company works, and not one unlucky leak, browser makers stop giving it the benefit of the doubt.

Am I affected?

Who needs to worry, and who doesn't

The risk is in anything that doesn't update itself

Your browser
Chrome, Firefox, Safari and Edge on an updated phone or computer already block the bad stamps.
Safe
ITR, GST, Aadhaar eSign
These use a separate Indian system run under the government's Controller of Certifying Authorities. The government says they are not affected.
Not affected
Websites using eMudhra
About 30,000 website certificates have to be replaced. eMudhra says it is doing this free of charge.
Must replace
Old apps and devices
Office software, smart TVs, cameras, routers and older apps that never get updates may still trust the bad stamps.
At risk

A lot of people in India asked me the same thing: is my tax filing or Aadhaar eSign safe? Yes. eMudhra runs two separate businesses on two separate trust systems, and only the website one broke.

Chartered accountant in Bengaluru using Aadhaar biometric scanner and USB ePass token to verify ITR filing under CCA India

Figure 4: Indian Sovereign Digital Signatures Remain Uncompromised. Everyday citizen compliance—including Income Tax Returns (ITR), MCA filings, and Aadhaar eSign—operates under India's Controller of Certifying Authorities (CCA) root hierarchy, entirely insulated from the affected global SSL/TLS website certificate pool.

Same company, two separate systems

The problem stayed on one side

Website certificates
This is where it broke
Trusted by browsers worldwideGoogle, Mozilla, Apple, Microsoft
▼
eMudhra's main stampno longer trusted
▼
8 helper stamps with tiny keys
Used for: the padlock on websites, and signing software.
Indian digital signatures
Not affected
Controller of Certifying Authoritiesunder MeitY
▼
Root Certifying Authority of India
▼
Licensed companies, including eMudhra
Used for: signing ITR, GST and company filings, and Aadhaar eSign.

That doesn't mean everyone is satisfied. The tech news site MediaNama argued that leaving the business isn't the same as being held accountable, and the Internet Freedom Foundation said it was writing to MeitY, the CCA and CERT-In. I think those are fair questions to ask of a company that also handles signatures for the country's tax filings.

This has happened before

In 2011 a Dutch company called DigiNotar, which did the same job, was hacked. The attackers made fake certificates for Google and used them to spy on people in Iran. Putting the two side by side is useful:

DigiNotar in 2011, eMudhra in 2026

DigiNotar · 2011eMudhra · 2026
What went wrongHackers broke into its systemsWeak keys were made by mistake
Fake certificates531, including for GoogleNone by eMudhra; test ones by others after the news
People harmedAbout 300,000 Gmail users in Iran were spied onNone confirmed so far
What happened nextRemoved from all browsers and went bankrupt within weeksMain stamp distrusted; left the website certificate business

The common thread: a company like this sells trust. Once browsers withdraw it, that business is finished.

What you should do

For most people, this is short.

🔄
Update your phone and browserThat's how the block on the bad stamps reached you. If you've been putting off an update, do it today.
🔒
Don't treat the padlock as a promiseIt means your connection is encrypted. It doesn't mean the site is honest. Scam sites have padlocks too.
📶
Be careful on public Wi-FiAttacks like this need someone between you and the internet. Use mobile data for banking when you're out.

If you look after websites, servers or company IT

Your job is a bit longer. Browsers are protected, but plenty of business software keeps its own list of trusted stamps and only updates it when someone tells it to.

What IT teams should do, in order

Start at the top

Today
Update every trusted-certificate list
The operating system, plus Java, Python and Node apps, Docker images and anything that carries its own list. Restart services afterwards so the change takes effect.
Today
Check whether you use eMudhra certificates
Look at your public websites, servers behind a CDN, and partner connections. If you do, take the free replacement and install it.
This week
Watch for certificates issued in your name
Public "certificate transparency" logs show every certificate issued for your domain. Free monitoring tools can alert you to ones you didn't ask for.
If you make keys
Check the keys, not just their names
Choose keys by their fingerprint, test new keys for weakness, and treat any "wrong key" error as a real incident.
Commands: check a website's certificate chain

This lists every certificate a site sends and flags the affected eMudhra ones. Replace example.com with your domain.

openssl
# save every certificate the server sends
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null 2>/dev/null \
  | awk '/BEGIN CERT/,/END CERT/' > chain.pem

# show who issued each one, and flag the affected eMudhra stamps
openssl crl2pkcs7 -nocrl -certfile chain.pem | openssl pkcs7 -print_certs -noout \
  | grep -E "EM (DV|OV|EV) TLS CA - G3[BC]|emSign ECC Root CA - G3" \
  && echo "AFFECTED CHAIN" || echo "no affected eMudhra certificate in this chain"
Commands: update trusted-certificate lists
linux, python, java
# Debian / Ubuntu
sudo apt update && sudo apt install --only-upgrade ca-certificates
# RHEL / Alma / Rocky
sudo dnf update ca-certificates
# Python apps
pip install --upgrade certifi

# is the distrusted eMudhra root still in the Linux list?
awk -v cmd='openssl x509 -noout -subject' '/BEGIN/{close(cmd)};{print | cmd}' \
  /etc/ssl/certs/ca-certificates.crt | grep -i "emSign ECC Root CA - G3"

# Java
keytool -list -v -cacerts -storepass changeit | grep -i "emSign ECC Root CA - G3"

If it still shows up, your vendor may not have shipped the update yet, so check their advisory. eMudhra's older emSign Root CA - G1 is not being removed, so search for the exact name above and not just "emsign".

Script: test whether one of your own keys is tiny

For teams that create their own keys. It tries every secret key from 1 to 4,095 against a certificate. On my test certificate with key 4 it answered in about a tenth of a second. Passing this doesn't prove a key is good. Failing it proves the key is broken.

weak_key_check.py · pip install cryptography
# usage: python weak_key_check.py cert.pem
import sys
from cryptography import x509
from cryptography.hazmat.primitives.asymmetric import ec

cert = x509.load_pem_x509_certificate(open(sys.argv[1], "rb").read())
pub = cert.public_key()
if not isinstance(pub, ec.EllipticCurvePublicKey):
    sys.exit("Not an EC key, nothing to check")

target = pub.public_numbers()
for d in range(1, 1 << 12):          # every private key from 1 to 4,095
    if ec.derive_private_key(d, pub.curve).public_key().public_numbers() == target:
        print(f"WEAK: private key is {d}")
        break
else:
    print("No tiny private key found")

Your quick checklist

Update your phone, computer and browser

And the devices of parents or kids you help with tech.

Use mobile data for banking outside home

Not café, hotel or airport Wi-Fi.

Never click past a certificate warning

If your browser says a connection isn't private, close the tab.

IT teams: update trusted-certificate lists everywhere

Servers, containers, Java and Python apps, then restart.

Website owners: replace any eMudhra certificate

Before browsers stop accepting it.

What I take away from this

Nothing was stolen here, and I keep coming back to that. All the expensive hardware and audits were in place, and a naming mix-up during one meeting still got through. Security comes down to the boring steps, like checking that the key you're about to use is the one you meant to make.

The clue in June 2025 bothers me too. Something didn't match, it got patched over, and the real problem sat there for another 16 months. If a "small" error doesn't make sense, it's worth stopping to find out why.

And for the rest of us, the advice is boring but it works. Keep your devices updated, because that's how the fix reached millions of people within days.

Sources


Share With Family and Friends

LinkedIn WhatsApp