Google and Mozilla scrambled over the weekend to block eight compromised security certificates issued by the authority eMudhra. If they had not stepped in quickly, anyone on the internet could have used these flawed certificates to impersonate real websites and spy on your browser traffic.

This whole ordeal started on Saturday when a security researcher named Wayne noticed that the private keys for eight intermediate certificates were generated with weak randomness.

One researcher on an IFIN threat intel thread even pointed out that the private key for at least one of these certificates was literally just the number 4.

Because the math behind the keys was so weak, anyone could figure them out directly from the public certificates. To prove it, Wayne used the cracked keys to sign a casual message reading “We have a problem here” and sent it straight to the browser teams.

wayne-emudhra-issue

Google’s Chrome security team verified the report and pushed out an emergency block in less than two hours. Because the block was handled remotely through Chrome’s background revocation system, desktop users were protected right away without restarting their browsers.

Android users and Chromebooks got the same fix through Google Play Services later on Monday. If you want to force that update on your phone right now, simply restarting your device will do the trick. This development comes as Google enlists AI to sniff out fake antivirus warnings and phishing traps in Chrome, keeping folks safe on another front.

Over at Mozilla, engineers rolled out a remote block through their OneCRL system in under three hours. They also pushed out the Firefox 158.0.1 update on Tuesday to make sure people with custom network settings are covered too.

“An attacker who could intercept a user’s connection could use those certificates to impersonate websites and potentially read or modify traffic,” the Mozilla security team explained in their write-up.

Both browser makers are now stripping the main eMudhra root certificate out of their trust stores completely. Google noted that “to avoid breakage, website operators with certificates chaining to emSign ECC Root CA – G3 must immediately acquire and install a new TLS certificate” before Tuesday, October 27.

That said, while most netizens like us are now safe, developers and sysadmins still have some work to do. Cloudflare had to rush out patches for its WARP client and backend tools, and anyone curious about the deeper technical weeds or looking to test their own setup can check out Dennis Jackson’s tracking site.

 
✦
PiunikaWeb’s Take

Honestly, browsers dodged a massive bullet here mostly because both Google and Mozilla have remote kill switches that can squash bad certs before anyone notices.

That said, the headache is all those backend servers, developer tools, and Linux setups that don’t pull automatic updates and have been trusting these broken keys since early last year. When a certificate authority messes up key generation this badly, cleaning up the rest of the software world takes months. If you are just browsing on your phone or PC, you are totally fine, but we’d still suggest rebooting your Android phone.

We stand out from the tech-media crowd because we break news stories; we mainly bring you stuff that you won’t find anywhere in the mainstream tech media. Our stories have been picked up by some of the world’s most popular websites and media outlets—more info is available here.

Dwayne Cubbins
3134 Posts

I cover fast-moving stories across apps, online platforms, and everyday tech — phones, wearables, consoles, and whatever else people are fighting with this week. Bugs, rollouts, scams, policy enforcement, and the occasional internet-culture rabbit hole are all fair game. My goal is simple — make confusing tech news readable. When I'm not working, I'm working out or chilling with my dog. Got a tip? You can find me on X @dcubbins.