ZachXBT Alleges $15.8M in Unaccounted CoinDCX Deposits, Questions Indian Exchange Trust

ZachXBT Alleges $15.8M in Unaccounted CoinDCX Deposits, Questions Indian Exchange Trust


On October 22, 2026, on-chain investigator ZachXBT publicly challenged a statement from Indian cryptocurrency exchange CoinDCX regarding the status of certain wallet addresses linked to a July 2025 security incident. 

In a post on X, ZachXBT asserted that a deposit address identified as TQKJQ continued to process user deposits for approximately 10 months after the incident and swept funds to CoinDCX’s current public hot wallet as recently as April and May 2026. 

Compromised July 2025 deposit address was reused by a liquidity provider, sweeping $15.8 million in user deposits through 2026.

CoinDCX claims the address was inactive after the hack, but on-chain data shows transfers to its hot wallets months later.

Lack of transparent reconciliation between internal records and blockchain activity fuels doubts about Indian exchanges’ custodial practices.

The investigator stated that this activity meant $15.8 million in user deposits remained unaccounted for by the exchange’s team. Alongside, ZachXBT also questioned the reliability of Indian centralized exchanges, referencing prior issues at WazirX and BitBNS. 

The exchange of statements followed CoinDCX’s earlier announcement on X that users’ funds are safe and that circulating claims about specific wallet addresses and transactions were misleading. The platform said the addresses in question were created in January 2025, compromised during the July 2025 incident, and had not been used by CoinDCX since that time. Trading and investing continued as usual, the post added, directing users to official channels for updates. 

On-Chain Analysis Highlights Continued Activity on Compromised Address 

ZachXBT’s analysis focused on blockchain records showing inflows and outflows involving the TQKJQ deposit address. The accompanying screenshot displayed multiple transfers, including a 15.819 million USDT movement on October 21, 2026, from the deposit address to another wallet, along with smaller USDT and TRX transactions in May 2026 connecting the address to CoinDCX hot wallets labeled TU7Bb and others. The investigator described the address as having been used by a liquidity provider to sweep user deposits and receive gas fees well after the July 2025 event.

This claim builds on ZachXBT’s prior identification of the July 2025 incident, in which approximately $44 million was drained from an internal operational account used for liquidity provisioning on a partner exchange. At the time, CoinDCX co-founder Sumit Gupta stated that customer funds were segregated and unaffected, with the loss absorbed by the exchange’s treasury reserves. The current allegation centers not on a new breach of customer wallets but on whether deposits routed through the previously compromised address were properly reconciled and accounted for in the months that followed.

Blockchain data of this type is publicly verifiable, allowing independent review of address activity, timestamps, and token amounts. However, matching specific on-chain movements to individual user deposit records requires internal exchange data that is not fully public. 

CoinDCX has previously published proof-of-reserves information and monthly transparency reports detailing assets under management, a Crypto Investor Protection Fund, and related metrics. As of September 2026, the platform reported assets under management of 624.79 million USDT and a protection fund of ₹57.07 crore, according to a post by Gupta.

CoinDCX Maintains User Funds Remain Secure 

In a reply on X earlier the same day, Gupta addressed similar tagging of addresses by analytics platforms such as Arkham. He wrote that the addresses belonged to CoinDCX before the July 2025 hack, were generated in January 2025, and were compromised in that incident. Gupta stated that hackers appeared to be reusing the old addresses and that the exchange had checked all current central and user addresses, finding that none had sent funds to the flagged addresses. He added that CoinDCX wallets were not breached and that all company addresses remain public on the platform’s proof-of-reserves page.

CoinDCX’s official post reinforced this position, emphasizing that the reported activity related to old addresses with no connection to current operations. The exchange has undertaken several security-related initiatives since the 2025 incident and subsequent events involving its founders. 

In March 2026, following a brief detention of co-founders Sumit Gupta and Neeraj Khandelwal in a separate fraud complaint that resulted in bail, the company announced a ₹100 crore Digital Suraksha Network focused on fraud prevention, including a helpline, intelligence tools, and awareness programs, as covered in prior reporting on the initiative. The platform has also collaborated with Indian government bodies on cyber safety campaigns.

These measures form part of a broader effort to address trust and compliance questions in India’s crypto sector. CoinDCX reports more than 20 million registered users and continues to publish regular transparency updates. The exchange has maintained that customer assets are held separately and that operational losses from the 2025 event were covered internally.

Recurring Challenges for Indian Crypto Exchanges

ZachXBT’s post placed the CoinDCX matter in the context of earlier difficulties at other Indian platforms. WazirX, once the country’s largest exchange by market share, suffered a roughly $230 million hack in 2024. After restructuring, users received approximately 85 percent of holdings, with the remaining portion converted into recovery tokens. The platform’s market share has since declined significantly, with recent coverage noting that 15% of user funds remain locked as leadership pursues new product initiatives.

BitBNS has faced prolonged withdrawal restrictions for some users dating back several years, along with legal disputes. A Delhi High Court ruling in early 2026 rejected certain pleas seeking broader investigation, treating the matter as a private commercial dispute, according to analysis of the case. These episodes have contributed to ongoing discussion about custody practices, disclosure timelines, and user protection mechanisms across Indian centralized exchanges.

The latest exchange between ZachXBT and CoinDCX underscores the role of independent on-chain monitoring in raising questions about address reuse and fund tracking after security incidents. While the exchange asserts that no current user funds are affected and that prior compromised addresses are no longer in use, the investigator’s transaction data points to activity into 2026. Resolving the discrepancy would require CoinDCX to provide a detailed reconciliation of deposits that passed through the TQKJQ address against its internal records and published reserves.

The episode adds to a series of events that have tested confidence in Indian crypto platforms and highlighted the importance of clear, timely accounting between on-chain activity and exchange-reported liabilities.

This is a developing story and more information will be added as the event unfolds. The Crypto Times has reached out to CoinDCX for comments.

Also read: Railway Security Flaw Puts Customer Funds in Crypto at Risk, Deployments Halted


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *