Exchange Watch / CoinDCXUpdated 13 Nov 2026; incident review 29 Oct 2026
CoinDCX:regulatory and wallet updates.
A new government notice concerns alleged FEMA contraventions. The earlier wallet-loss disclosure, researcher freeze report and deposit-address warning remain separate issues with their own dates and verification limits.
Wallet incident reviewed 29 October; regulatory update checked 13 November
What is established—and by whom
- Company acknowledgement: In its 25 October post, CoinDCX states a loss of 15.99 million USDT, which it says it absorbed. It attributes this to deprecated infrastructure and a failed sweeping service.
- Researcher update: Bitquery reports 2,212,850 USDT frozen across nine wallets late on 22 October. Its revised balances were measured at 18:55 UTC on 23 October; they are not a current balance or proof of returned funds.
- Verification limit: The company’s stated amount is not an independent audit. Customer ledger credits and private-key control are not established by wallet labels or public transfers alone. We have not audited CoinDCX’s books or tested account withdrawals.
How the explanation developed
On 22 October, CoinDCX initially attributed the flagged transactions to addresses it said had been compromised in July 2025 and retired. ZachXBT disputed the account, citing subsequent activity involving the TQKJQ deposit address and alleging approximately $15.8 million in unaccounted deposits. Sumit Gupta then said the matter was being investigated further.
CoinDCX’s later clarification acknowledged continued deposits to deprecated addresses and a failed collection process. Those statements need to be read together, rather than treating the first denial as the complete explanation. Its assurance about customer balances remains a company statement.
25 October: company states the loss amount
CoinDCX’s fuller account is dated 25 October, although its title refers to the 21 October activity. It says unusual activity was detected on 21 October and irregular movements were identified the next day.
It describes portfolio crediting and wallet sweeping as separate processes. According to the company, deposits were credited on arrival even when collection failed. It says active systems and deposit balances were unaffected and promises stronger monitoring of residual infrastructure. These remain company assertions, not independently verified customer-account results.
What the Bitquery investigation adds
Bitquery’s revised report still challenges the original unused-wallet explanation using post-July deposit movements. It reports a Tether freeze at 22:45 UTC on 22 October; its updated snapshot replaces the earlier unfrozen-balance account.
Its balances are a snapshot at 18:55 UTC on 23 October, not current balances. Freezing tokens restricts movement; it does not establish recovery, reimbursement or funds returned to CoinDCX. Some passages still omit the company’s credited-deposit explanation. The 25 October company account explicitly makes that claim. Wallet attribution and transaction interpretation may also be revised.
Why a sweeping failure matters
A sweeper collects funds from deposit addresses into an exchange’s operating wallets. An address can be removed from the deposit interface while still receiving transfers from people using saved details. Retiring an address does not prevent someone from sending funds to it on the blockchain.
Whether the exchange credited a deposit, retained control of the keys, recovered funds or covered a shortfall requires additional evidence. A public transaction cannot answer all four questions.
Questions that remain unanswered
- What independent evidence reconciles the company’s stated loss with its books and the researchers’ transaction trail?
- When did collection fail, what detected it, and how was the failure corrected?
- How does CoinDCX reconcile post-July activity with its original description of unused addresses?
- What independent evidence supports the credited-deposit and loss-absorption claims?
The latest detailed company account reviewed for this 29 October update is the 25 October blog post. Its statement about uninterrupted withdrawals over the preceding 72 hours describes that period, not access for every account today. We are not asserting a confirmed breach of current active wallets, a final customer-loss total, insolvency or wrongdoing.
Practical checks for account holders
Before any new deposit, retrieve the receiving address and supported network from the official app or website. Do not reuse saved addresses without checking. Preserve statements, transaction hashes and support-ticket references; raise missing credits through official support.
Do not send extra money to unlock a withdrawal or share an OTP, password, private key or recovery phrase with a caller or recovery agent. An available trading screen or a company assurance does not prove that every account can withdraw. Check the current conditions for your own account.
Read the original record