CoinDCX Co-Founder Denies New Hack After $16 Million Wallet Alert
- Published
- Updated
- Since then
- 32 new reports
CoinDCX first rejected claims of a fresh breach after suspicious outflows were flagged from wallets tied to the exchange. Days later, it confirmed a 15.99 million USDT loss from retired wallet infrastructure linked to its July 2025 incident and said customer balances were unaffected.
Key claims & sources
What it means
CoinDCX's July 2025 breach drained roughly $44 million from its hot wallets, pushing the exchange to retire the compromised deposit addresses and issue new ones to customers. The October alert concerned exactly those decommissioned wallets, not new infrastructure. Indian exchanges operate under FIU registration but no binding on-chain proof-of-reserves rule, so the first line of detection came from independent researchers like ZachXBT and Salus's Darcy rather than mandatory company disclosure.
Some customers kept sending USDT to the old deposit addresses months after migration, and the automated sweep meant to forward those funds to cold storage failed, letting a balance build until it was drained. CoinDCX says it will cover the full 15.99 million USDT from its own balance sheet, so account holders see no shortfall on their dashboards. Anyone who saved the pre-2025 deposit address or QR code now needs to delete it entirely.
The dispute over CoinDCX's management is really about the three-day gap between Sumit Gupta calling the reports a 'false alarm' and the exchange confirming the loss, not just about dead wallets receiving live funds. ZachXBT's call for users to withdraw everything treats that gap as a trust failure: an exchange unable to immediately say which of its own addresses are retired is asking depositors to take its word on custody.
Watch whether CoinDCX publishes a full technical audit of every retired wallet from the 2025 incident, since its combined disclosed losses across both episodes now approach $60 million. A public accounting of which addresses were truly decommissioned versus still reachable would settle whether this was an isolated sweep failure or a sign that other legacy infrastructure remains exposed.
Market reaction i
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Thefts of a similar size
| When | What happened | Figure |
|---|---|---|
| 2.6 years ago | Curio · Delegatecall Hijack incident | $16M |
| 2.9 years ago | FloorProtocol · Business logic flaw incident | $16M |
| 5.1 years ago | Indexed Finance · Price manipulation incident | $16M |
| 6.2 years ago | Electrum · Fake software update incident | $16M |
| 7.8 years ago | Cryptopia · Hot Wallet Key Compromised incident | $16M |
4280 incidents stored · 255 were as large as this one or larger ($16M)