eMudhra shares fall 34% in three sessions after private key compromise
eMudhra shares extend losses for a third day as CERT-In issues an urgent advisory over a compromise of private keys. Source: TradingView.
- published on Newsmetry
- original source published
the public page opens no earlier than 15 minutes after we detect the story. approved stories may reach the api sooner. connect the api →
what happened
Shares of India's eMudhra kept falling on Thursday, October 22, hitting an intraday low of ₹368.75, down 14.6%. The stock had dropped 20% the previous session and 33.7% over three sessions. According to TradingView, the shares are down 42.1% over the past month and 33% so far in 2026, and sit about 1% above their 52-week low of ₹364.55.
The selloff followed a security incident in which the company reported a compromise of private keys for eight immediate Certificate Authority certificates. The Indian Computer Emergency Response Team (CERT-In) issued an urgent advisory, and the Ministry of Electronics and Information Technology (MeitY) formed a special team to probe the matter. Government sources told CNBC-TV18 that the impact on Indian websites and applications was limited and short-lived, and that Digital Signature Certificates and eSign services were unaffected. Management called the incident a 'one-off on a bad day.'
why it matters
For investors, the key point is that the incident concerns the international part of eMudhra's business, which operates under global standards and is not overseen by MeitY. It remains unclear how long the pressure on the shares will last and how the incident will affect the company's clients.
market impact
eMudhra shares: the security incident and client risk weigh on the company's stock price
tags
instruments
sources
- Stock Crash: eMudhra shares down 34% in three sessions; Management says 'one-off incident on a bad day' — TradingView, 22 October 2026 at 06:04 UTC
prepared by the newsmetry newsroom with ai assistance from the sources listed below. not investment advice.
the public page opens no earlier than 15 minutes after we detect the story. approved stories may reach the api sooner.
get stories in real time ↗