# eMudhra (a business run by 1 family), passed two audits by BDO after an integrity incident. Is the internet chain of trust broken? — retained record

> Retained reddit record from reddit:cybersecurity.

Canonical: https://highsignal.app/data/records/5fbcc67f69a5f349

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:cybersecurity)  published 2026-10-23 12:25 ingested 2026-10-24 02:36

[original source ↗](https://www.reddit.com/r/cybersecurity/comments/1xdcl4v/emudhra_a_business_run_by_1_family_passed_two/)

## retained text



```
The more I look into the eMudhra incident, the more concerned I am about the auditors and the governance behind this company. We’ve spent plenty of time talking about the fact that one of their intermediate CA private keys was literally the number 4, which is fucking dumb. But I think there’s a much bigger issue here. How did this survive two independent WebTrust audit cycles, including one where *the auditors were already aware of an incident involving the exact same intermediate CAs*?

For anyone who hasn’t followed this, eMudhra generated eight intermediate CA keys in April 2025 that were trivially recoverable. Six were for TLS and two for code signing. The private keys were effectively just single-byte integers. Anyone with the corresponding public keys could recover them in milliseconds. These intermediates remained in the public trust ecosystem for roughly 18 months before an external researcher raised the alarm.

Now let’s look at the audit history.

BDO Consulting conducted the 2024–25 WebTrust audit, covering the period in which these keys were generated. BDO PLT, another Malaysian firm in the BDO network, conducted the 2025/26 audit. The affected TLS intermediates were included in the audit scope.

June 2025: eMudhra had already been reported to Mozilla because certificate revocation lists for six of these intermediates had invalid signatures. The CRLs had been signed using the wrong private keys. We now know why: eMudhra had generated the intended keys, accidentally generated a second set of catastrophically weak keys, and then issued the intermediate certificates using that second set. When the CRL signatures didn’t verify, they switched to signing with the weak keys.

Think about that for a moment. You discover that the private key being used to sign a CRL doesn’t match the public key in the intermediate CA certificate. Surely that should trigger a serious investigation into the key generation ceremony and the integrity of the keys themselves?

Apparently, that wasn’t enough to further investigate and uncover this absolute dumbfuckery.

BDO’s August 2026 audit report explicitly acknowledges the earlier incident involving those six intermediates. It says BDO considered the disclosed root cause and the proposed corrective controls. It also stated the audit involved testing the operating effectiveness of controls, including controls intended to protect the integrity of CA keys throughout their lifecycle.

BDO still issued an unmodified opinion. Bizarre.

I’d really like to know what testing was actually performed here. Did anyone independently verify that the keys generated during the ceremony matched the keys in the issued CA certificates? Did anyone review the HSM records, the key generation scripts or the unexplained existence of multiple key pairs? What evidence gave BDO sufficient confidence to sign off on key lifecycle integrity after a known signing-key mismatch?

I understand WebTrust audits use sampling and provide reasonable assurance. Nobody expects an auditor to find every possible problem. But this wasn’t some obscure attack technique or previously unknown cryptographic weakness. These were intermediate CA keys with virtually no entropy, and there had already been a publicly documented integrity issue involving the very same certificates.

Then there’s the corporate governance side of this.

eMudhra’s founder and Executive Chairman is Venkatraman Srinivasan. His son Kaushik Srinivasan is a co-founder, Executive Vice President responsible for product development and engineering, including CA solutions, and a Whole-Time Director. His other son, Arvind Srinivasan, is an Executive Vice President responsible for international business and is also a Director. Both sons joined the board in April 2026.

So the founder and both his sons now occupy three seats on a nine-member board, while the sons also hold senior operational roles. The board has five independent directors, but that raises the obvious question of how effectively independent oversight works in practice.

Family relationships don’t automatically mean someone is unqualified, and I’m not suggesting any of these individuals personally caused the key generation failure. But there are obvious potential conflicts when the people responsible for running parts of a business are also closely related to its chairman and sit on the board that’s meant to hold management accountable.

Who was challenging the engineering decisions? Who was reviewing the incident reports? Who was responsible for making sure corrective actions were independently validated? And who was overseeing the relationship with BDO?

These questions matter even more given the chairman’s response to the incident, which included pointing out that SSL/TLS certificates account for only around 1% of eMudhra’s revenue and suggesting the scrutiny was disproportionate.

That’s a pretty extraordinarily dumb response from the chairman of a company operating a publicly trusted certificate authority. The internet doesn’t care what percentage of your revenue TLS represents. Your certificates are trusted because the ecosystem accepts your claims about how securely you operate.

And that brings me back to BDO.

The whole point of independent assurance is that relying parties shouldn’t have to take the CA’s word for it. If an organisation can have a publicly documented key integrity problem, receive an unmodified audit opinion, and then have the underlying catastrophic failure discovered months later by an external researcher, what exactly did that assurance establish?

I think BDO should publicly explain what work was performed around the 2025 incident, why the key generation process didn’t receive sufficient scrutiny to reveal this issue, and whether the conclusions of those audit reports remain supportable. An independent review of the audit work seems entirely reasonable.

eMudhra is responsible for generating and protecting its keys. The board is responsible for oversight. But the auditors are part of this trust model too, and their role deserves serious examination.

The mathematics behind certificate chains hasn’t broken. What concerns me is the system of governance we’re reliant on to trust this seems ineffective or completely broken.

If something this fundamental can survive two audit cycles, including one conducted after a known integrity incident involving the same keys, I think we need to ask some uncomfortable questions about what WebTrust assurance actually means.
```



document fetched 2026-10-24 10:26 · canonical https://reddit.com/r/cybersecurity/comments/1xdcl4v/emudhra_a_business_run_by_1_family_passed_two
