CoinDCX Confirms $16M Crypto Loss From Retired Wallets After Breach Denial

 

India's market is facing scrutiny after CoinDCX confirmed a $15.99 million USDT loss linked to old wallet infrastructure. The disclosure came days after the exchange rejected reports of a new security breach, saying the wallets had been compromised during a July 2025 incident and later retired. The explanation points to a failed automated process that left deposits exposed.

 

The incident centers on roughly 15.99 million USDT that left about 40 CoinDCX-linked wallets on the TRON network on October 21. Blockchain data firm Bitquery said the funds moved to a new address before being distributed across multiple wallets. Amounts reached other exchanges, while Tether froze about $2.21 million that remained traceable.

The company said an automated sweeping mechanism designed to move those deposits into secure wallets stopped working for a period. Funds accumulated in vulnerable addresses. CoinDCX said it absorbed the loss and credited affected users, while active trading and wallet infrastructure continued operating normally.

CoinDCX's explanation describes the issue as an operational failure rather than a compromise of its current customer-fund infrastructure. The exchange said active wallets were not breached and user funds remained protected in segregated cold wallets. That distinction is important, although it does not eliminate questions about the controls surrounding legacy addresses.

 

Exchanges generate deposit addresses and rely on internal systems to monitor incoming funds. If an address has been compromised, continuing to receive deposits can create serious operational risk even when current hot and cold wallets remain secure.

However, blockchain investigators have challenged parts of the timeline. It is reported that CoinDCX-linked systems appeared to be moving funds through some addresses shortly before the October 21 drain. Its investigation said one wallet accounted for approximately $15.82 million of the total and had received numerous deposits that remained unmoved for months.

Those findings do not by themselves establish a completely new CoinDCX hack. They do raise questions about how effectively the exchange's deprecated-address system was enforced.

 

The controversy grew because of CoinDCX's initial response. When reports of suspicious transfers emerged, co-founder and CEO Sumit Gupta said the claims appeared to be a false alarm and argued that the flagged addresses belonged to older infrastructure.

That position was followed by a fuller acknowledgment that $15.99 million in USDT had been lost. The difference between the initial response and subsequent disclosure matters because crypto users value transparent communication during security incidents.

CoinDCX maintains that the incident did not affect customer balances or active trading systems. It has also said the company itself absorbed the loss, meaning affected users were not left responsible for the missing funds.

The episode demonstrates why on-chain investigations can complicate an exchange's public explanation. Blockchain transactions are permanently recorded, allowing researchers to examine wallet activity independently and compare those records with company statements.

 

CoinDCX's confirmation of a $15.99 million USDT loss brings clarity to a confusing series of reports, while leaving questions about its retired-wallet controls. The exchange says the loss originated from compromised legacy infrastructure and a failed sweeping process, not a new breach of active systems. Independent blockchain analysis has raised questions about whether some wallets remained operational longer than expected.

The incident reinforces a broader point for crypto: strong security requires continuous management, not just secure storage. As exchanges handle large amounts of customer assets, outdated wallet infrastructure can become a financial and reputational liability. For users, this highlights why exchange security depends on both technical safeguards and effective operational oversight.