CoinDCX confirmed a loss of 15.99 million USDT, about $16 million, from old operational wallet infrastructure that was compromised in its July 2025 security incident and deprecated afterward. Some users kept depositing to the retired addresses. CoinDCX credited those deposits to their accounts immediately, but the automated service meant to sweep the funds into its secure wallets failed for a period, so value built up in addresses the attacker could still reach.

The outflow was first flagged on-chain by independent investigators, who traced the funds to a single Tron address before they were split toward several exchanges. CoinDCX's CEO initially described the reports as a false alarm, and on-chain investigator ZachXBT noted that one of the addresses had swept user deposits to CoinDCX's current hot wallet as recently as April and May 2026. CoinDCX later confirmed the loss, said it had absorbed it, and acknowledged it could have disclosed the incident sooner. It says active wallets, trading, deposits and withdrawals were unaffected.

The weakness is operational rather than protocol-level. A compromised wallet that still receives deposits is not retired; it is a standing liability that depends on a background job to stay empty. When that job fails silently, an attacker who already holds the keys only needs to wait.

Defenses come down to wallet lifecycle management. Compromised addresses should be fully decommissioned, users warned repeatedly and deposit paths blocked where possible, and any residual sweeping designed to fail closed with immediate alerts. Continuous balance reconciliation on deprecated addresses would have surfaced this accumulation long before it was drained.