CoinDCX $16M Outflows: What Happened12 min read2,484 words

CoinDCX $16M Outflows: What Happened

CoinDCX says $16 million in outflows involved retired addresses, not active wallets. Read what the dispute reveals about deposit sweeps and exchange risk.

CoinDCX $16 million outflowsCoinDCX wallet incidentcrypto exchange securitycrypto deposit addressesblockchain transaction tracing
CoinDCX $16M Outflows: What Happened

CoinDCX's $16 Million Outflow Dispute Is About More Than a Hack Claim

A big crypto outflow is tempting to read one way: money leaves an exchange-linked wallet, investigators call out the transactions, and users immediately wonder whether the exchange has been hit again. CoinDCX's case doesn't fit that neat story.

CoinDCX says the roughly $16 million in USDT and TRX transfers involve wallet addresses that were compromised in a July 2025 attack and were no longer used by the company afterward. On-chain investigator ZachXBT pushes back, arguing that at least one address still appears to have been used, with deposits and transfers continuing into 2026.

There's another problem in the mix. CoinDCX says some customers kept sending funds to retired deposit addresses, and that a temporary breakdown in its sweeping process meant those deposits weren't handled the way they should have been. The exchange says it credited affected users and insists its active wallets and customer assets weren't compromised. That doesn't answer every question about where the $16 million ended up - but it does move the discussion away from a simple "hack or not" headline and toward deposit address handling and day-to-day controls.

What happened in the CoinDCX outflow dispute

On October 21, 2026, an X user identified as Darcy flagged transactions involving addresses linked to CoinDCX. The reported outflows totaled about $16 million in USDT and TRX. According to ZachXBT, the funds went to a single Tron address and were then distributed to multiple other wallets.

The attention makes sense because CoinDCX had suffered a major exploit in July 2025, with reported losses of about $44 million. When new large transactions show up tied to an exchange's addresses, people naturally connect the dots to the last incident. Still, a transaction linked to an exchange doesn't automatically prove the exchange's systems were breached again.

CoinDCX's account is that the involved addresses were created in January 2025, compromised in July 2025, and not used by the company after that attack. The exchange says its current central and user addresses weren't affected and that no funds from active wallets were compromised. CEO Sumit Gupta also described the renewed activity as hackers reusing old addresses, not as evidence that CoinDCX's active wallets had been newly compromised.

This distinction matters because blockchain records don't "turn off" when an exchange stops using an address. Transaction history stays visible, and someone can still interact with an address that remains on-chain. So the real question isn't just whether the addresses once belonged to CoinDCX. It's whether those addresses were truly retired in practice - and whether deposits or transfers involving them still connect back to CoinDCX's current operational infrastructure.

CoinDCX also acknowledged an operational issue: for a period, its process for sweeping deposits from deprecated addresses didn't work properly. The company says some users continued sending funds to old addresses even after notices went out. CoinDCX says it credited every affected user, covered the resulting operational losses, and kept trading running normally while customer assets stayed in cold wallets.

Those points should be separated from the $16 million transaction total. What's available doesn't show that the full amount equals a brand-new loss for CoinDCX, a loss for customers, or funds pulled from active wallets. CoinDCX's explanation and ZachXBT's challenge focus on different parts of the story: the status of old addresses, what happened later with transfers, and how reliable CoinDCX's deposit-handling process was during that period.

Why the old-address explanation is being challenged

ZachXBT questioned CoinDCX's claim that the addresses hadn't been used since the July 2025 incident. He says at least one address - identified as TQKJQ - was still in use by a liquidity provider for about ten months after the incident. He also claims it received gas as recently as April and May 2026 and that deposits were swept to CoinDCX's current public hot wallet.

If that's accurate, it complicates the idea that the address was simply abandoned. An address can be marked deprecated inside an exchange system while still receiving deposits from customers who saved it earlier. People can also copy old details into wallets, spreadsheets, emails, or contact lists. But if the address continued to receive funds and those funds were routed into CoinDCX's current wallet setup, then the operational relationship between the old address and the exchange needs a closer look.

This disagreement isn't automatically settled by pointing at one transaction trace. Public blockchains show transfers between addresses, but they don't tell observers who controlled each address, why a transfer happened, or what happened inside an exchange's deposit records. Investigator labels can help, but they aren't the same thing as an independent audit of custody and internal controls. Likewise, an exchange saying an address was retired doesn't make the observable on-chain activity disappear.

A careful read comes down to separating three claims:

  • The reported on-chain activity: investigators point to about $16 million in outflows from addresses they associate with CoinDCX.
  • CoinDCX's account: those addresses were tied to the 2025 incident, not CoinDCX's active wallets, and the exchange says its current addresses weren't affected.
  • The operational question that isn't fully nailed down: whether the old addresses still received or routed funds in a way that remained connected to CoinDCX after they were described as deprecated.

The third point is where the missing detail matters most. What would help is a clear timeline showing when the addresses were disabled for new deposits, how customers were notified, when the sweeping process failed, and how CoinDCX reconciled deposits that arrived at deprecated addresses. The reporting so far doesn't provide that full operational timeline or an independently verified accounting of the $16 million.

None of this proves CoinDCX's explanation is wrong. It does, however, show that "not an active-wallet hack" and "no operational failure" are different claims. CoinDCX has acknowledged a limited operational problem - specifically a temporary sweeping failure and losses it says it absorbed. The exchange can be right that active wallets weren't compromised while still leaving real questions about what happened when deposits went to old addresses.

How deposit addresses and sweeping create operational risk

Most crypto exchanges assign a unique deposit address to a customer for a specific asset or network. The customer sends funds there, and then the exchange moves those deposits - often called a "sweep" - into wallets it manages centrally. Some funds sit in hot wallets for day-to-day withdrawals, while others are kept in cold storage with tighter access.

This approach is efficient at scale. It helps exchanges manage balances and keep routine liquidity separate from longer-term custody. It also creates dependencies. The exchange has to generate addresses correctly, link them to customer accounts, watch for incoming transfers, sweep funds when it should, and update the deposit instructions customers see when addresses change.

A retired address is a messy edge case. The exchange might stop issuing it to new customers, but a customer can still have it saved from an earlier deposit. Unlike a bank account number that can be closed or rerouted through centralized systems, a blockchain address can still receive transfers even after it's marked deprecated. If someone sends assets to it, reversing that transaction typically depends on whoever controls the receiving keys - and on whether the exchange can cooperate internally to recover or reconcile the situation.

That's why address changes shouldn't be treated like a simple database tweak. A safer retirement process needs both technical controls and customer communication. Depending on how the exchange operates, controls can include stopping address generation, monitoring legacy addresses, using clear deposit warnings, and setting up a defined recovery or reconciliation procedure. Each option has trade-offs. Monitoring every legacy address forever adds operational complexity, while removing support too quickly can strand customers with funds they can't recover and make support a nightmare.

The CoinDCX dispute shows the gap between policy and working control. The exchange says users were told not to deposit to compromised, deprecated addresses. It also says the sweep process was supposed to catch those deposits and did not do so reliably for a time. But a notice alone can't stop transfers - people can still send funds to the wrong address. And if the sweep process isn't actually catching late deposits, the system needs monitoring and escalation when it starts failing.

For exchanges, the control questions are fairly consistent:

  • Can the system reliably identify deposits sent to retired or flagged addresses?
  • Are failed or delayed sweeps visible to operations staff quickly enough to reduce exposure?
  • Can the company tell a customer deposit apart from activity driven by an attacker?
  • Is there a documented process for reconciling balances and crediting affected users?
  • Are customers given clear, current deposit instructions, or are they still relying on saved details?

These questions apply beyond CoinDCX. Exchange security isn't only about private keys and preventing signatures from unauthorized parties. It also includes the less visible work of maintaining address lists, handling exceptions, and matching what the blockchain shows to what's in customer account records.

What users and exchanges should take from the incident

For users, the takeaway is straightforward: before you send crypto, double-check the deposit address and network using the exchange's current instructions. Don't assume a previously working address is still valid. If you have saved deposit details, check the exchange account again - especially after a security incident or when the exchange says addresses have changed.

If a deposit goes to a deprecated address, contact support using the exchange's official channels. Keep the transaction ID, asset, network, amount, and timestamp. Don't share seed phrases or private keys with anyone offering "recovery." A blockchain transfer may be public, but recovery still depends on control of the receiving address and what the exchange can verify internally.

For exchanges, the lesson is that retirement is a lifecycle, not a one-time admin task. It starts with preventing new use and notifying customers, but it also has to include monitoring for residual deposits, defined handling for exceptions, and a way to demonstrate that old addresses aren't still part of active flows. If the system works for the normal case but fails silently for legacy deposits, that's still an operational risk.

There's also a communication lesson. When investigators publish transaction traces, an exchange's quick denial can address the headline without answering the bigger questions. A useful update should separate active wallets from deprecated or compromised addresses, say whether customer deposits were affected, explain what the company has reconciled or reimbursed, and clarify what's still under review. That's the kind of detail users need to make decisions without turning speculation into certainty.

For readers sorting through the claims, avoid two shortcuts. First, don't treat every large exchange-linked outflow as proof of a fresh hack. Second, don't treat a statement that "active wallets were not compromised" as proof that every related control worked perfectly. Both can be true at once: no new breach of active wallets, alongside an operational failure tied to old addresses.

The available facts support a limited conclusion. CoinDCX denies its active wallets were hacked in connection with the reported outflows. The exchange says it experienced a temporary failure handling deposits to deprecated addresses and says it credited affected users. ZachXBT disputes the claim that at least one address was out of use, pointing to activity he says continued into 2026. What the on-chain traces mean for the exchange's internal records - and exactly how the $16 million relates to custody and processing - still needs clearer documentation.

Conclusion

The CoinDCX dispute isn't resolved by choosing between "hack" and "no hack." CoinDCX says its active wallets were unaffected. An investigator questions whether at least one supposedly retired address stayed connected to customer deposits and current wallets. Separately, CoinDCX says its deposit-sweeping process failed temporarily and that it made affected users whole.

For users, the practical step is to verify addresses before every transfer. For exchanges, handling legacy addresses needs the same operational care as the more obvious parts of security. For the public, the next useful step is a transparent timeline that connects the on-chain activity to the exchange's internal account of what happened.

Read the original CoinDesk report for the source reporting, and follow official exchange updates before making decisions about your assets.

Frequently Asked Questions

CoinDCX denied that its active wallets were compromised in connection with the reported outflows. The exchange attributed the activity to addresses it says were compromised in July 2025 and later deprecated. An investigator disputed whether at least one address was truly out of use. The available information does not independently establish a new active-wallet breach.
The figure refers to reported outflows involving USDT and TRX from addresses linked by investigators to CoinDCX. It should not automatically be read as a confirmed new loss to the exchange or its customers. CoinDCX says the transactions involved old addresses, while the full accounting and relationship to its internal records were not provided in the source reporting.
A deprecated address is one an exchange no longer intends customers to use. It may still be capable of receiving blockchain transfers, particularly if customers have saved the address from an earlier deposit. That is why exchanges need clear notices and a process for monitoring or handling funds sent to old addresses.
A sweep is the movement of funds from customer deposit addresses into wallets managed by an exchange. Exchanges use sweeps to consolidate deposits and manage custody. The process needs monitoring and exception handling, because delayed or failed sweeps can leave deposits outside the expected flow.
Check the current deposit address and network in the official CoinDCX account interface each time, rather than relying on a saved address. If you have already sent funds to an old address, contact official support with the transaction details. Never share your recovery phrase or private keys with someone offering to retrieve the transfer.

Related articles