CoinDCX's $16 Million Loss: Why Old Exchange Deposit Addresses Can Still Cost Money
India's CoinDCX says a failed internal sweep left user deposits sitting in retired, compromised wallets. What happened and how to deposit to an exchange safely.
Not financial advice. This article is for general information and education only. It is not a recommendation to buy, sell or hold any asset. Crypto assets are volatile and you can lose money; do your own research.
CoinDCX, one of India's best-known crypto exchanges, says it has covered a loss of about 15.99 million USDT — roughly $16 million — after money piled up in wallet addresses it had stopped using more than a year ago. The exchange says customer balances were never touched because it paid for the loss itself. Still, the episode is a useful lesson for anyone who sends crypto to an exchange: the deposit address you saved last year may not be the one you should use today. This article walks through what happened, why the explanation changed during the week, and simple habits that keep your own deposits safe.
What happened, step by step
The story began on Tuesday, October 21, when coins started leaving addresses linked to CoinDCX on the Tron network. According to The Block, an on-chain analyst flagged the outflows early the next morning: around 15.99 million USDT, plus a smaller amount of TRX, moved to a single Tron address and was then split up and sent on to deposit addresses at several large exchanges.
CoinDCX's first public response was a denial. Chief executive Sumit Gupta replied on X that the addresses had been compromised in the company's July 2025 hack and that the alert sounded like "a false alarm." The company's account added that the addresses had not been used since that incident.
Independent investigator ZachXBT disputed that. As reported by both The Block and CoinDesk, he pointed to on-chain records suggesting that at least one of the old addresses had still been collecting customer deposits and passing them along to the exchange's live hot wallet in April and May of this year. In other words, the "retired" address was still part of the money flow.
On Sunday, October 25, CoinDCX published a blog update that confirmed the loss and explained the mechanism.
The exchange's explanation: a sweep that stopped sweeping
To understand CoinDCX's account, it helps to know how many exchanges handle deposits.
When you deposit crypto, you usually send it to an address the exchange shows in its app. Behind the scenes, the exchange does two separate things:
- It credits your account. Your balance goes up as soon as the deposit is confirmed on the blockchain, so you can trade right away.
- It "sweeps" the coins. A background service later moves the coins from the many individual deposit addresses into the exchange's main wallets, where they are easier to manage and protect.
CoinDCX says it stopped using its old wallet setup after the July 2025 attack, which cost the company about $44 million. But some customers kept sending money to the old deposit addresses anyway — perhaps from saved address books, old screenshots or withdrawal "whitelists" at other platforms. Rather than leave those users stranded, CoinDCX kept crediting their accounts and relied on the sweep service to pull the coins into safer wallets.
According to the company, that sweep service failed for a period of time. Deposits built up in an address whose security was already known to be weak, and someone drained it. The blog post does not call the event a hack, does not say who moved the funds and does not say how long the sweep was broken. CoinDesk reported that CoinDCX acknowledged it could have disclosed the problem faster.
Were customers affected?
CoinDCX says no customer lost money. Because it had already credited the deposits to users' accounts, the shortfall sat on the company's books, and the company says it absorbed it. It also says trading, deposits and withdrawals kept working throughout and that customer funds are held in segregated cold wallets.
Those statements come from the exchange itself, and outsiders cannot fully verify an exchange's internal accounts. ZachXBT went further and publicly advised people to withdraw their funds, accusing the founders of misleading users in their first replies. The Block also noted that he helped freeze part of the stolen money. Readers can weigh both sides; the useful point for everyone is that a company's first statement during an incident is not always its last.
Why "old address" problems happen at all
Blockchains do not have a concept of a closed account. An address that has been abandoned by a company can still receive coins from anyone, forever. If the private key behind that address has leaked — as CoinDCX says happened in 2025 — anything sent there can be taken by whoever holds the key.
That creates an awkward choice for exchanges:
- Ignore deposits to old addresses, which protects the company but can leave customers who made a mistake without their money.
- Keep accepting them, which is friendlier to customers but means the company must move those coins out quickly and reliably, every time.
CoinDCX chose the second path, and the weak spot turned out to be the automation behind it. Other exchanges handle the problem differently, for example by warning users loudly in the app, rejecting deposits to retired addresses or, on networks like the XRP Ledger, using one shared address plus a customer tag instead of many separate addresses.
How to deposit to any exchange safely
You do not need to understand wallet infrastructure to avoid most deposit problems. A few habits go a long way:
- Copy a fresh deposit address every time. Open the exchange's official app or website, choose the coin and network, and copy the address shown there. Do not reuse an address from an old message, spreadsheet or screenshot.
- Match the network exactly. USDT exists on several blockchains, including Tron, Ethereum and others. Sending on the wrong network is one of the most common ways people lose stablecoins.
- Check for memos or tags. Some coins, such as XRP, require a destination tag or memo. Leaving it out can delay or lose a deposit.
- Update your withdrawal whitelists. If another platform has a saved "trusted" address for your exchange account, delete it and add the current one when the exchange changes its addresses.
- Send a small test first. For larger amounts, send a small transaction, confirm it arrives, then send the rest.
- Read exchange security notices. After any incident, exchanges usually tell customers which addresses are no longer valid. Treat those emails seriously — but open the app yourself rather than clicking links, because scammers copy these notices too.
- Don't leave more than you need on an exchange. Money you are not actively trading can be moved to a wallet you control. Our wallets guide and exchanges guide explain the trade-offs.
A wider pattern in 2026
The CoinDCX case joins a run of incidents this year in which the weak link was not a blockchain, but the systems around it: payment processors, shop databases and internal automation. We covered a similar theme in our look at why bridges keep getting hacked and in our guide to the Keystone data breach. The common thread is that "the code was audited" or "the wallet is safe" rarely covers every moving part of a business.
India is also a large and fast-growing crypto market, so trust in its exchanges matters well beyond one company. CoinDesk describes CoinDCX as the country's largest exchange by trading volume, and The Block notes that Coinbase invested in it in 2025. How the company handles follow-up questions from users and regulators will be watched closely.
The bottom line
According to CoinDCX, a background process that should have moved customer deposits out of an old, compromised address stopped working, and about $16 million was taken before anyone caught it. The company says it covered the loss, so user balances were not affected. For ordinary users, the practical lesson is simple: always copy a fresh deposit address from the official app, double-check the network and any memo, and update saved addresses whenever an exchange tells you they have changed. This article is for education only and is not financial advice.
Sources: CoinDCX blog, Oct. 25, 2026; The Block, Oct. 25, 2026; CoinDesk, Oct. 26, 2026; XRP Ledger docs: destination tags.
#coindcx#india#exchanges#deposit address#usdt#tron#security
