CoinDCX Loss $16M ⚠️ Wallet Security: Retired Custody Explained
CoinDCX loss: $15.99M traced to crypto deposit sweeping. Learn what happened, what’s unclear, and retired crypto wallet custody controls for users.

CoinDCX's $16 Million Loss Was a Wallet Process Failure. Here's What That Means
A crypto wallet address doesn't "turn off" just because an exchange stops using it. Blockchains keep recording transfers. If a customer sends funds to an old deposit address, those tokens still arrive on-chain - and the exchange has to have a working process to spot them and move them where they belong.
That's the crux of CoinDCX's disclosure about a $15.99 million loss. The Indian exchange says customers continued depositing into addresses it had retired after a security breach in 2025. CoinDCX credited those users' accounts, but a secondary "sweeping" step - meant to consolidate the funds into its main wallet - didn't work for a stretch. The company says it absorbed the shortfall.
The episode also flagged a separate problem: CoinDCX first pushed back on reports of suspicious outflows, then later tied the activity to its older wallet infrastructure. The exchange says customer balances and active systems were not affected, but it hasn't publicly explained who moved the funds or exactly how the irregular transfers happened.
This article looks at what CoinDCX has said, what still isn't clear, how deposit sweeping works, and what exchanges and users can take from the incident.
What happened to CoinDCX's retired wallet?
CoinDCX says it took a loss of 15.99 million USDT after an internal process failed to move deposits out of a deprecated wallet. The exchange linked that wallet infrastructure to the security incident it reported on July 19, 2025, which it said cost about $44 million. Afterward, CoinDCX says it retired the affected infrastructure.
The story gained attention when on-chain observers flagged roughly $16 million in suspicious outflows connected to wallets tied to CoinDCX. Initially, CoinDCX said the activity didn't relate to its current operations. CEO Sumit Gupta called the reports a false alarm, and a company spokesperson said the addresses hadn't been used since the 2025 breach.
On-chain investigator ZachXBT disputed that, saying at least one address - identified as TQKJQ - had been used by a liquidity provider and swept user deposits to CoinDCX's current public hot wallet as recently as April and May 2026. CoinDCX later published a more detailed explanation of the wallet activity and acknowledged a loss connected to the old infrastructure.
The sequence CoinDCX described
CoinDCX's account can be summarized like this:
- CoinDCX retired wallet infrastructure after the 2025 security incident.
- Some users kept sending deposits to addresses tied to that old infrastructure.
- CoinDCX says it credited those users when the deposits landed.
- A secondary service - what the exchange calls "sweeping" - was supposed to transfer the funds to its primary wallet.
- The sweeping process failed for a period, so funds accumulated at the deprecated address.
- CoinDCX says the loss totaled 15.99 million USDT and that it absorbed it.
The claim centers on a failure involving old infrastructure and a failed transfer step. It doesn't, by itself, prove a second hack, identify who carried out the outflows, or spell out exactly how the funds left the wallet. CoinDCX's explanation also doesn't use the word "hack."
That detail matters. "A compromised wallet," "an unauthorized transfer," and "a failed deposit-sweeping process" are not the same thing. Based on CoinDCX's own description, the public facts support the last interpretation - but key questions about the outflow mechanism remain unanswered.
How can a retired wallet still receive deposits?
An exchange can't treat a wallet address like a bank account that it can simply close. On most public blockchains, an address remains capable of receiving tokens even if the business that created it has stopped supporting it. The chain records the transfer. Then it's the exchange's job to determine whether it recognizes that deposit and whether it can credit the customer and move the funds.
That's where the mismatch can happen: an exchange can "retire" an address in its own systems while the address itself still functions on-chain. CoinDCX may stop showing the address, generate a new one for future deposits, and label the old one deprecated - but a customer who saved the old address (or who follows an older transaction record) can still send funds there.
Why exchanges use sweeping
Exchanges need to monitor deposit addresses and consolidate assets into wallets used for custody or day-to-day liquidity. A sweeping process can detect incoming funds at a deposit address and then move them to a designated wallet.
In CoinDCX's account, this secondary step was meant to transfer funds from the deprecated address into the primary wallet. The reason it matters is that customer account records and on-chain custody aren't the same system. A deposit can be detected and credited, while a later transfer meant to consolidate the funds fails. When that happens, the exchange's internal books and its actual wallet holdings can drift apart.
That's exactly the kind of issue reconciliation is supposed to catch. A solid process should compare customer credits, on-chain deposits, transfer status, and wallet balances - and raise an alert when records don't match. Even a correct-looking customer credit doesn't guarantee that every custody step downstream actually succeeded.
What "retired" should mean in practice
Retirement needs to be a controlled transition, not just a label. In practice, that means warning users, updating deposit instructions wherever possible, monitoring old addresses, limiting access to legacy signing systems, and defining what happens if deposits arrive after deprecation.
There's a trade-off either way. Keeping old addresses under watch lowers the chance of missed deposits, but it also means the exchange must maintain oversight for longer. Fully abandoning old addresses reduces operational burden, but it increases the risk of user confusion and deposits that go nowhere. The right approach depends on the chain, the custody model, and how customers behave. Either way, retirement still requires clear controls.
What is known - and still unclear - about the loss?
CoinDCX's public account is narrower than the headline number might imply. The exchange says the loss was 15.99 million USDT, that it was tied to old operational wallet infrastructure, and that a sweeping process failed for a period. It also says it absorbed the loss and that customer balances, active wallets, and trading systems were unaffected.
Those statements are important, but they aren't the same as an independently verified incident report. In its explanation, CoinDCX didn't identify who was behind the irregular movement of funds, describe the technical path by which the funds left the wallet, or say whether the retired addresses were compromised again. The source account also doesn't point to a public forensic report that resolves those points.
What the loss does - and does not - say about customer funds
CoinDCX says customers' portfolios were credited when deposits reached the deprecated addresses and that the company took the financial hit. It also reiterates that user funds remain in segregated cold wallets protected by layered custody controls. Cold wallets are designed to stay offline, which generally reduces exposure to systems that touch the internet.
What the statements don't prove is that every part of the custody setup was reviewed end-to-end, or that there's a complete breakdown of what happened to each affected address. For users, though, the practical takeaway is straightforward: CoinDCX says balances and active systems weren't impacted, while the incident shows that a legacy deposit workflow didn't operate as intended.
When a company absorbs a loss, it can prevent immediate balance damage - but it doesn't erase the operational failure. The ongoing questions are whether controls now stop similar deposits from accumulating and whether the legacy infrastructure has been fully reviewed. Users also need a dependable way to confirm what deposit instructions are valid.
The communication gap
CoinDCX initially described the outflows as unrelated to its current operations. Later, after reviewing the deprecated infrastructure, it connected the activity to the older wallet system and disclosed the loss. The company said the review took time and admitted it could have been more proactive, saying it shared an update once it had a complete picture.
There's a real tension here. An exchange shouldn't treat an unverified on-chain allegation as settled fact. But when observers point to large outflows tied to exchange-related addresses, dismissing the reports too broadly can damage trust - especially if the explanation changes later. A better incident update usually separates what's confirmed, what's under investigation, and when the next update will come.
What should exchanges and users take from this incident?
For exchanges, the core lesson is blunt: retiring a wallet isn't "done" just because the address stops being displayed. As long as customers can still send assets to it - or as long as the exchange retains access through its keys - the exchange still has an operational responsibility. Deprecation is a lifecycle change, not a database status.
A practical control framework should cover the full path from customer deposit to final custody:
- Address lifecycle: Track when addresses are created, active, deprecated, and no longer monitored. Assign an owner and document the retirement process.
- Customer warnings: Clearly label old addresses as unsupported, provide replacement instructions, and keep warnings easy to find in the areas customers use to get deposit details.
- Deposit monitoring: Keep watching legacy addresses for incoming transfers, with alerts for activity that doesn't match expected patterns.
- Transfer verification: Treat sweeping as a monitored workflow. Confirm that transfers are signed, broadcast, and finalized rather than assuming the service completed the job.
- Reconciliation: Compare on-chain balances with customer credits and internal ledgers. Escalate mismatches quickly - especially when customers were credited but assets show up in an unexpected wallet.
- Legacy access controls: Review which people, services, and keys can interact with deprecated infrastructure. Limit access and document any exceptions.
- Incident communication: Say what's known, what's uncertain, what's being done to protect users, and when the next update will be available.
None of this guarantees zero losses. It just makes failures easier to detect and shortens the time between something going wrong and a response. In a high-volume exchange, the real question isn't whether a workflow worked in one controlled test. It's whether it holds up across many addresses, different customer behaviors, multiple chains, and real-world service disruptions.
What users can do
Customers can't fully audit an exchange's internal wallet processes, but they can cut down on avoidable deposit mistakes. Before sending funds, pull the deposit address from the exchange's current interface - not an old screenshot, a saved note, or a transaction from months ago. Double-check the network and token details too. An address that looks correct can still fail if it's on the wrong network.
If an exchange says an address is deprecated, don't assume it will "recover" a deposit automatically. Contact support before transferring, and if you've already sent funds, save the transaction ID and any other transfer details. Whether an exchange can recover funds depends on what access it still has to the address, which network the transfer used, and what internal procedures it can run.
These steps don't shift responsibility onto users. They're just safeguards for the specific risk that old deposit instructions can keep circulating after an address changes status.
Conclusion
CoinDCX's disclosure is a reminder that wallet security isn't only about keeping active keys safe. It also depends on the unglamorous work of retiring infrastructure, monitoring old addresses, and reconciling customer credits against what's actually sitting on-chain. A process can fail outside the main trading system and still cause real losses.
CoinDCX says it absorbed the 15.99 million USDT shortfall and that customer balances were unaffected. But its public account leaves important questions about the movement of funds unanswered. And the shift from an initial dismissal to a later acknowledgment raises a separate trust issue.
For exchanges, the takeaway is simple: treat wallet retirement as a managed lifecycle, not a one-time switch. For users: verify deposit instructions before sending funds. And when you evaluate an exchange's response, look carefully for clear lines between confirmed facts, open questions, and the controls it says it put in place afterward.