CoinDCX Confirms $16M Loss as Tether Freezes $2.2M

CoinDCX confirms the loss from failed deposit sweeps

An exchange can report a company loss while maintaining customer account balances. Crediting a deposit creates a liability to the customer. Protecting the actual tokens requires the collection and custody process to work as well.

Retiring an address in an application does not disable it on a public blockchain. Someone using a saved address can still send funds there, leaving the operator with a residual monitoring problem after a migration.

The disclosure does not provide the failure’s duration, a detailed cause or an independently audited reconciliation. It also supplies no affected-customer count, limiting what can be concluded about the breadth of exposure.

In its on-chain investigation, Bitquery identified 40 drained wallets and attributed about 15.82 million USDT to a single address holding 88 deposits. These are wallet and transaction counts, not a tally of unique victims.

Bitquery also reported that the exchange’s systems continued moving deposits through the address set before the theft. Its tracing challenges a simple reading of the wallets as unused, although on-chain activity alone cannot reveal every customer’s account credit or the exchange’s internal books.

Tether freeze covers about 14% of CoinDCX’s loss

AMLBot’s October 23 update reported roughly $2.2 million frozen and traced funds moving one additional hop before the intervention. One approximately $720,000 balance split into roughly $401,000 and $319,000 at two subsequent addresses, the firm said.

Arisk separately reported approximately 2,212,900 USDT frozen across nine addresses. It dated their simultaneous addition to Tether’s blacklist to October 22 at 22:45:39 UTC.

BlockintAI’s detailed review lists 2,212,850.29 USDT held by those nine addresses, with balances and blacklist status checked October 23 at about 12:05 UTC. Its report links the addresses to the initial receiving wallet through subsequent transfers.

As of this article’s October 26, 09:00 UTC evidence review, that dated snapshot was the best-supported precise freeze figure identified. It represents about 13.8% of CoinDCX’s rounded 15.99 million-USDT loss. It is not a live balance claim or an independently verified repayment total.

The difference is consequential. Blacklisting immobilizes tokens at specified addresses. It does not establish that control or ownership has passed back to the exchange, and subtracting the frozen amount from the loss would prematurely label the remainder as final net damage.

Tether’s published terms describe its ability to freeze tokens and blacklist addresses in specified circumstances. That issuer control can interrupt a transfer trail; a separate return or recovery process is needed to demonstrate restitution.

CoinDCX recovery still needs a final reconciliation

Bitquery traced about $9.63 million to addresses it associated with OKX, Binance and Gate within 18 hours of the main transfer. Those destination labels are the analytics provider’s attribution. They do not establish wrongdoing by the receiving exchanges or prove that the associated accounts were frozen.

Amounts passing through different stages of the trail also cannot be added together as separate losses. An initial transfer, a later exchange deposit and an immobilized balance may describe the same tokens at different times.

The Tectonic rollback’s final accounting showed how an incident’s gross activity, reversed funds and unrecovered amount can diverge. CoinDCX still lacks an equivalent public reconciliation establishing what was returned and what remains outstanding.

The practical customer instruction remains to verify the current deposit address in CoinDCX’s official app before each transfer. The exchange says maintenance of deprecated addresses is time-limited. Its decision to absorb this loss does not establish an indefinite guarantee for future deposits to retired addresses.

Alternative.me’s Bitcoin Fear & Greed Index read 50, or Neutral, on October 26, against 54 a day earlier. It measures broader sentiment, rather than the security or financial condition of CoinDCX.

The next useful disclosures are a verified return of funds, the number of affected customers and an explanation of the failed sweep. Until then, the supported figures remain a company-confirmed loss and a separately reported freeze, with no newly established attack wave or final recovery total.