Contents
Initial Outflows and Exchange Response
On October 21, 2026, blockchain monitoring entities flagged unauthorized outflows totaling approximately $16 million from addresses linked to Mumbai-based exchange CoinDCX 23. An X user named Darcy and the Arkham tracking service observed transfers on the Tron network involving tether (USDT) and TRX tokens 23. The largest individual movement executed was 15,819,002 USDT, which was routed into a single Tron address before being distributed across multiple secondary wallets 2.
In standard exchange architecture, unique user deposit addresses collect incoming assets before automated routines transfer funds into centralized storage 2. Hot wallets manage internet-connected daily trading withdrawals, whereas cold wallets store funds offline 2. Following the flagged activity, CoinDCX co-founder and chief executive officer Sumit Gupta characterized the report as a false alarm on the social platform X 123.
A spokesperson for the exchange stated on October 23, 2026, that the flagged transactions involved old addresses created in January 2025 12. The company asserted that those addresses were compromised during a previous security incident on July 19, 2025, and were subsequently abandoned 123. CoinDCX initially maintained that no active hot or central wallets were impacted and that current user balances were unaffected 12.
Internal Sweeping Process Failure
On October 26, 2026, CoinDCX issued an official update confirming that it absorbed a corporate loss of 15.99 million USDT due to an internal technical failure 13. The exchange clarified that the compromised funds resided on a retired operational wallet address that formed part of its legacy infrastructure 1. Following the July 19, 2025 exploit—which cost the firm roughly $44 million—the exchange had instructed users to cease sending funds to those specific deposit addresses 123.
Despite earlier notifications, a subset of customers continued sending asset deposits to the deprecated addresses 12. CoinDCX credited these users' account balances instantaneously upon receipt of the transfers 12. To manage these residual deposits, CoinDCX operated a secondary automated process designated as sweeping, which was designed to forward funds from deprecated addresses into primary exchange wallets 123. However, this sweeping pipeline failed over an unspecified duration 1. The breakdown allowed user deposits to accumulate inside the deprecated address rather than being transferred into primary storage 1.
Discrepancies in Infrastructure Deprecation
The exchange's initial timeline faced scrutiny from independent on-chain researchers 123. On-chain investigator ZachXBT publicly contested CoinDCX’s initial assertion that the legacy infrastructure had remained completely dormant since July 2025 123. ZachXBT pointed to a specific deposit address labeled TQKJQ, noting that a liquidity provider had utilized it for 10 months following the 2025 breach 2.
On-chain records cited by ZachXBT showed that address TQKJQ regularly swept customer deposits and received gas fees as recently as April 2026 and May 2026 to fund transfers to CoinDCX’s active public hot wallet 12. ZachXBT cautioned users regarding exchange operations and urged asset withdrawals, alleging that management provided misleading public statements regarding the incident 3.
Following these findings, CoinDCX acknowledged that its initial review of the deprecated infrastructure required additional time to establish the complete sequence of events 1. The exchange admitted it could have been more proactive in its communication prior to releasing its October 26 statement 1.
Cumulative Loss Exposure and Security Posture
The 15.99 million USDT loss brings CoinDCX's cumulative losses from wallet security failures to nearly $60 million across two major incidents 13. The prior breach on July 19, 2025, resulted in a $44 million loss attributed to a server compromise, which later led to police investigations and the arrest of an employee 3. In addition to security vulnerabilities, the exchange experienced operational challenges in 2026, including law enforcement inquiries regarding impersonation scams and public denials by its founder regarding potential acquisition talks with Coinbase 3.
CoinDCX stated that its current user funds remain segregated in offline cold wallets protected by multi-layer custody controls 12. The company confirmed that trading operations continue without interruption while internal investigations proceed 23.
What is not yet established
- The identity of the entity or individual behind the unauthorized 15.99 million USDT transfer 1.
- The specific technical vulnerability or method used to extract funds from the deprecated operational wallet 1.
- Whether the retired wallet private keys were re-compromised or continuously accessed by third parties following the July 2025 breach 1.
Frequently asked questions
Why were funds accumulating in a retired wallet address?
Users continued making deposits to deprecated addresses created in January 2025, and an internal sweeping system failed to clear those funds into primary exchange wallets 12.
Sources
- CoinDesk — India's largest crypto exchange absorbs $16 million loss from internal process failure tied to retired wallet (2026-10-26) https://www.coindesk.com/markets/2026/10/26/coindcx-absorbs-usd16-million-loss-from-internal-process-failure-tied-to-retired-wallet
- CoinDesk — India's largest exchange denies hack after sleuths pointed to $16 million in suspicious outflows (2026-10-23) https://www.coindesk.com/markets/2026/10/23/india-s-largest-exchange-denies-hack-after-blockchain-sleuths-pointed-to-usd16-million-in-suspicious-outflows
- Decrypt — India’s CoinDCX Confirms $16 Million Loss Days After CEO Called It a ‘False Alarm’ (2026-10-26) https://decrypt.co/381834/india-coindcx-confirms-16-million-loss-ceo-called-false-alarm
Revision history
Published