India's largest crypto exchange says it will absorb the loss itself after Tether froze a portion of the stolen funds.
CoinDCX, widely described as India's largest cryptocurrency exchange, has confirmed a loss of $15.99 million connected to a compromised wallet. The admission came just days after the company publicly denied reports that it had suffered a hack.
According to reporting from crypto.news, the exchange's reversal followed closer scrutiny of on-chain activity that pointed to unauthorized movement of funds. TronWeekly reported that the incident involved a USDT wallet and that Tether, the issuer of the stablecoin, moved to freeze a portion of the implicated funds once the activity was flagged.
CoinTurk News reported that Tether froze approximately $2.2 million of the total amount, leaving the bulk of the loss unrecovered. BitKE characterized the affected wallet as a retired one, meaning it was not part of CoinDCX's active operational infrastructure at the time funds were drained.
The gap between CoinDCX's initial denial and its later admission raises questions about how exchanges communicate with users during active security incidents. Crypto platforms often face pressure to reassure customers quickly, but premature denials can undermine trust if facts later shift. CoinDCX has not detailed, according to the available reporting, exactly how the wallet was compromised or how attackers gained access.
CoinDCX has stated it will absorb the loss rather than pass costs onto customers, according to the cited reports. This approach mirrors responses from other major exchanges following past security breaches, where operators used corporate reserves to make affected users whole and avoid eroding confidence in the platform.
The freezing of funds by Tether highlights the role stablecoin issuers can play in limiting damage from exchange hacks. Tether has intervened in prior incidents across the industry by blacklisting addresses tied to illicit transfers, though such action typically recovers only a fraction of stolen assets.
Further details about the attack vector, the timeline of the breach, and any law enforcement involvement were not included in the available reporting. CoinDCX's standing as a leading exchange in the Indian market means the incident is likely to draw attention from regulators overseeing the country's digital asset sector.
Market Impact
The incident is likely to intensify scrutiny of custody practices at major exchanges, particularly around wallets that are no longer in active use but still hold residual balances. CoinDCX's decision to absorb the loss rather than shift it to users may help contain reputational damage in the near term.
The partial freeze by Tether demonstrates how stablecoin issuers can act as a backstop in security incidents, though the recovery of roughly $2.2 million against a nearly $16 million loss illustrates the limits of that mechanism. Indian regulators and users may press CoinDCX for more transparency on the cause of the breach and its remediation steps.
CoinDCX's admission closes the gap between its earlier denials and the confirmed scale of the loss, but questions about the breach's origin and full recovery prospects remain open.
Frequently Asked Questions
What happened to CoinDCX?
CoinDCX confirmed a $15.99 million loss tied to a compromised wallet, after initially denying reports that it had been hacked.
How much of the stolen funds were recovered?
Tether froze approximately $2.2 million of the USDT involved, according to reporting, leaving the majority of the loss unrecovered.
Will CoinDCX users bear the cost of the loss?
According to the reports cited, CoinDCX said it would absorb the loss itself rather than pass costs on to customers.
What was the 'retired wallet' mentioned in reports?
Reports described the compromised wallet as one no longer part of CoinDCX's active operational infrastructure at the time of the breach.
Why did CoinDCX initially deny the hack?
The exchange's early denial preceded confirmation of the loss, though the specific reasoning behind the initial statement was not detailed in available reporting.