Independent DeFi security desk · Status: operationalMethodology & corrections · Submit an incident
DDeFi Safety ToolsNEWS · DATA · PRACTICAL SAFETYGet the briefing
DeFi Safety · Fact checked

CoinDCX admits ‘operational losses’ after $16M wallet transfers draw scrutiny

CoinDCX said it covered losses caused by a failed transfer process involving compromised wallets and credited all affected user accounts.

By DeFi Tools Guide Editorial Team · Published Oct 22, 2026, 8:18 AM UTC · Updated 2026-10-22 · Risk level: medium
Sources checked: Oct 22, 2026, 2:48 PM UTC

This article may contain affiliate links. Commercial relationships are disclosed in the affiliate policy.

DeFi Safety — illustration keyed to this article's identifier. Source documents are listed under Sources and are not reproduced here.

What happened

CoinDCX said it covered losses caused by a failed transfer process involving compromised wallets and credited all affected user accounts.

Reported details

  • CoinDCX has denied claims of a fresh security breach after on-chain researcher Darcy flagged roughly $15.99 million in USDT and 5,783.81 TRX moving from addresses described as linked to the Indian crypto exchange. The transfers were consolidated into a TRON address before being split across multiple wallets. The alert raised concerns over a possible new … Read more
  • Indian cryptocurrency exchange CoinDCX has denied allegations of a new security breach involving nearly $16 million in cryptocurrency transfers, although blockchain investigator ZachXBT has challenged the company’s explanation of the suspicious wallet activity. CoinDCX said in an October 22 statement…
  • Sumit Gupta says the flagged addresses were compromised in July 2025 and that no funds from CoinDCX’s current wallets were affected.

Why this matters

Whether CoinDCX admits operational losses’ reaches the custody and settlement layer depends on what it actually names. If it points at a custodian, a redemption term or a withdrawal rule, that is the layer where exposure lives, and the name and its timing are the parts worth checking. If it names none of those, this angle simply does not apply here, and reading custody risk into it would be an assumption rather than a finding.

Evidence boundary

On CoinDCX, the scope is limited to what the linked 4 reports state, and where they diverge both positions are recorded without either being picked in advance; the headline figure is what to check first.

What to verify

If CoinDCX admits operational losses’ names a custodian or a redemption term, check that name and its timing against the operator’s own documentation; if it names neither, there is nothing here to verify on that layer.

Sources and editorial check time

This information is educational and is not financial, legal, or tax advice.

Sources