Lighter

2026

Cryptocurrency

TRON

Greed

<p><strong>Blockchain investigators are disputing CoinDCX's explanation for approximately $16 million in suspicious movements from wallet addresses linked to the Indian crypto exchange, alleging the exchange's public account of events does not match on-chain data. CoinDCX, which suffered a separate $44.3 million hack in July 2025 per Halborn's security analysis, says the flagged addresses were already compromised and deprecated before the latest movements occurred.</strong></p>
<h2 id="what-to-know-about-the-coindcx-16m-hack-dispute">What to Know About the CoinDCX $16M Hack Dispute</h2>
<p>On October 22, 2026, blockchain investigator Darcy flagged suspicious on-chain movements totalling approximately <a href="https://protos.com/crypto-exchange-coindcx-lying-about-16m-hack-say-blockchain-investigators/" rel="noopener noreferrer nofollow">$16 million</a> from addresses suspected to be associated with CoinDCX, reporting roughly 15.99 million USDT and 5,783.81 TRX in the flagged flows. The assets moved on the TRON network, with the TQKJQ deposit address identified as the focal point of investigator scrutiny. For related coverage, see <a href="https://www.marketbit.net/blockchain-trading-account-adds-options-trading/" rel="noopener noreferrer nofollow">Blockchain Trading Account Adds Options Trading: What to Know</a>.</p>
<figure style="margin:24px 0;padding:24px;border:1px solid #d8dee9;border-left:5px solid #d97706;border-radius:8px;background:#fffaf0;color:#172033;font-family:Arial,Helvetica,sans-serif;">
 <div style="font-size:12px;font-weight:700;letter-spacing:0.08em;text-transform:uppercase;color:#8a4b08;margin:0 0 10px;">
  Investigator-reported suspicious movements
 </div>
 <div style="font-size:42px;line-height:1.05;font-weight:800;letter-spacing:-0.03em;margin:0 0 10px;">
  $16 million
 </div>
 <figcaption style="font-size:14px;line-height:1.5;color:#4b5563;">
  Amount reported by investigators; CoinDCX says the affected addresses were already compromised and deprecated.
 </figcaption>
</figure>
<p>Three key claims frame the dispute. First, investigators assert the addresses remained operationally active long after the July 2025 incident CoinDCX cited as the point of compromise. Second, CoinDCX says the wallets in question were created in January 2025, compromised in July 2025, and formally deprecated following that security event. Third, the exchange states that user deposit balances were fully credited and that neither active central wallets nor live user addresses were affected. For related coverage, see <a href="https://www.marketbit.net/best-crypto-casinos-for-halloween-2026-live-events-spooky-slots-and-real-bonuses/" rel="noopener noreferrer nofollow">Best Crypto Casinos for Halloween 2026: Live Events, Spooky Slots, and Real Bonuses</a>.</p>
<p>The $16 million figure is an investigator-reported amount, not a number CoinDCX has independently confirmed as a discrete loss total. The exchange's <a href="https://x.com/CoinDCX/status/2113235810988531883" rel="noopener noreferrer nofollow">public statement</a> characterizes any shortfall as an operational loss it absorbed internally, not a fresh external hack. For related coverage, see <a href="https://www.marketbit.net/lighter-review-2026/" rel="noopener noreferrer nofollow">Lighter Review 2026: What the Trading Experience Actually Feels Like</a>.</p>
<h2 id="why-investigators-say-coindcx-s-account-does-not-match-the-blockchain-data">Why Investigators Say CoinDCX's Account Does Not Match the Blockchain Data</h2>
<p>ZachXBT, the pseudonymous blockchain investigator, alleged that the TQKJQ deposit address remained in active use by a liquidity provider for 10 months after the July 2025 incident, placing <a href="https://x.com/zachxbt/status/2113191832561778974" rel="noopener noreferrer nofollow">$15.8 million in user deposits</a> as unaccounted for in CoinDCX's public reconciliation. That allegation is an investigator claim, not a finding confirmed by CoinDCX or an independent forensic audit.</p>
<p>The core analytical discrepancy centers on the timeline: if a wallet was deprecated in July 2025, continued deposits and outflows through late 2026 would indicate either the deprecation was incomplete, the address was re-used, or a third party retained access. CoinDCX's statement acknowledges that deposits continued reaching deprecated addresses and that its regular sweeping process for those post-deprecation deposits failed for a period, resulting in operational losses the exchange absorbed.</p>
<p>On-chain evidence on TRON is publicly verifiable, but attributing wallet control to a specific exchange requires more than address association. No block-explorer transaction hash list or independent forensic report reconciling the TQKJQ wallet's full transaction history was included in CoinDCX's public statement, leaving the specific $16 million attribution unresolved at the wallet level.</p>
<p>The July 2025 incident that preceded this dispute was itself significant. Halborn's security analysis placed that hack at $44.3 million, describing a server and private-key compromise that drained a hot wallet before assets moved to Solana addresses and were subsequently bridged to Ethereum. That prior incident gives context for why the TQKJQ addresses were flagged as compromised in the first place, but it does not independently resolve whether those addresses were fully decommissioned afterward. Notably, <a href="https://www.marketbit.net/coinbase-coindcx-investment-regulatory-approval/" rel="noopener noreferrer nofollow">Coinbase holds a pending investment stake in CoinDCX</a>, a relationship that adds regulatory and reputational dimensions to the exchange's handling of successive security incidents.</p>
<h2 id="coindcx-s-response-and-what-happens-next">CoinDCX's Response and What Happens Next</h2>
<p>CoinDCX's official position, posted publicly on X, rests on four assertions: the flagged addresses were compromised in July 2025 and deprecated; deposits continued to arrive at those deprecated addresses after the fact; the sweep process that would have recovered those later deposits failed temporarily; and the resulting operational losses were absorbed by CoinDCX, with affected user deposit wallets credited in full.</p>
<p>The exchange explicitly stated that active central and user addresses were not impacted, framing the incident as an internal operational gap rather than a new external breach. CoinDCX did not publish the dollar value of operational losses it absorbed, nor a transaction-level reconciliation for the TQKJQ wallet, which is the central gap investigators are highlighting.</p>
<p>Broader market context at the time of the dispute shows Bitcoin trading at <a href="https://www.coingecko.com/" rel="noopener noreferrer nofollow">$81,424</a>, down 3.6% in 24 hours, with the <a href="https://alternative.me/crypto/fear-and-greed-index/" rel="noopener noreferrer nofollow">Fear &amp; Greed Index</a> at 68, indicating a Greed-dominant sentiment environment. Exchange security incidents historically trigger deposit outflows at affected platforms regardless of sentiment conditions, making CoinDCX's transparent reconciliation more consequential than under neutral market conditions.</p>
<p>The unresolved factual questions are specific. CoinDCX has not published the transaction hashes for the TQKJQ wallet's post-deprecation activity, the exact date the sweeping process failed and was restored, or the total dollar value of deposits that arrived at deprecated addresses between July 2025 and the October 2026 flagging. Until wallet-level reconciliation is published, the gap between the $15.8 million investigators cite and CoinDCX's unquantified "operational losses" figure remains open. Investors monitoring broader exchange infrastructure developments, including <a href="https://www.marketbit.net/binance-us-blockchain-com-cftc-prediction-markets/" rel="noopener noreferrer nofollow">regulatory approvals affecting competing platforms</a>, will be watching whether CoinDCX provides a detailed post-mortem or allows the dispute to persist without on-chain corroboration.</p>
<p>No regulatory filing, enforcement action, or law-enforcement disclosure tied to the October 2026 wallet-loss disclosure has been confirmed. Per the research record, the visible response to the incident is concentrated among blockchain investigators rather than regulators. According to unconfirmed investigator reports, the characterization that CoinDCX deliberately misrepresented the address usage remains a disputed allegation; the exchange's own account offers a different operational explanation that has not yet been refuted with a published transaction-level audit.</p>
<p style="font-size:13px;color:#888;border-top:1px solid #333;padding-top:12px;margin-top:30px;">Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.</p><a href="https://www.marketbit.net/?p=18807" rel="noopener noreferrer nofollow">Read original article on marketbit.net</a>

CoinDCX $16M Hack Claims Challenged by Blockchain Investigators

Table of Contents

Marketbit

Other articles published on Oct 22, 2026

Join our free newsletter for daily crypto updates!