Connect with us

EXCHANGE

CoinDCX Absorbs 15.99 Million USDT From a Retired Wallet

CoinDCX absorbed 15.99 million USDT after crediting deposits into a retired TRON wallet, then calling the October 21 drain a false alarm.

Published

on

CoinDCX said it absorbed a 15.99 million USDT loss after deposits sat in a retired TRON wallet it had already written off. The Mumbai-based platform is India’s largest crypto exchange by trading volume, and it credited those deposits as they arrived.

On October 22 it first said the wallets had no connection with CoinDCX. A thief emptied them on October 21.

A Retired Wallet That Still Took Customer Money

The hole opened because CoinDCX did not treat a retired address as a dead inbox. After the security incident it reported on July 19, 2025, the exchange told users to stop sending coins to the old deposit addresses and to copy fresh ones from its app or website. Some users kept using the old strings anyway.

CoinDCX’s own process then did the generous thing. It credited each of those deposits to the customer’s portfolio the moment the coins hit the retired wallet, so no user sat uncredited. A second service, the sweep, was supposed to pull the coins out of that burned address and into the primary CoinDCX wallet. That second step is the one that failed.

A credited balance is not the same as coins sitting in cold storage. The company booked the liability, left the USDT in an address it already knew had been compromised, and only later found that the sweeper had not moved the pile. Deprecation, on that design, is a label. It is not a lock.

The 88 Deposits That Never Moved

Almost all of the money sat in one place. Address TQKJQ sent 15,819,002 USDT at 15:35 UTC on October 21 to a brand-new TRON address, about 99% of the 15.99 million USDT that left 40 wallets that night. On-chain investigator ZachXBT tied TQKJQ to a liquidity provider.

Blockchain data firm Bitquery read the full TRON record for that address. For months the sweeper had moved each inbound deposit within a minute. Then 88 deposits from a single sender, arriving between January 29 and March 30, 2026, were never moved. Together they match, to the cent, the USDT the thief later took from TQKJQ.

The last successful sweep from that address was May 4, 2026. On March 11 the exchange swept 518 other deposit addresses in six minutes and left TQKJQ, which by then held more than $9 million. When gas top-ups resumed in April, new deposits moved on within a minute. The old pile stayed put until October 21.

CoinDCX says those users were credited even though they paid the retired addresses. If the books match that claim, the theft cost the company, not the customers. If they do not, a liquidity provider sat unpaid for months. Only CoinDCX’s ledger can settle that, and it has not published the entries.

The October 22 admission is the company’s first on-record account of the failed sweep.

Five Minutes Separated the Sweeper From the Thief

Darcy at security firm Salus was first to flag the drain, writing that 15.99 million USDT and 5,783.81 TRX left CoinDCX-linked hot wallets and deposit addresses for TAg6SZ1HhgVVjUaKY1paQoFBUS2JFrg5bT. Bitquery then walked 40 CoinDCX wallets on TRON and tested the claim that they had sat unused since July 2025. The record does not match that claim.

At 12:14 UTC on October 21, CoinDCX’s own system still moved a routine deposit through one of the wallets. At 12:19 UTC a 100 TRX payment hit the new address. That was the thief’s first move, 5 minutes later. Over the next half hour the same fee wallet that had been paying CoinDCX’s gas sent the new address its USDT and TRX. The thief tested with small amounts, emptied 35 deposit addresses, then pulled the 15,819,002 USDT from TQKJQ.

CoinDCX’s sweeper kept running. More than five hours after the drain, it moved a small deposit from a second address into the collecting hot wallet, as it had done all year.

WHAT THE CHAIN SHOWS

  • Recent sweeps: All 35 smaller drained deposit addresses had a deposit moved out by the exchange after September 1, 2026, and nine of them were moved the day before the theft.
  • Fee top-ups: The fee wallet that starts TFLx sent 276 payments of 15 TRX each since August 2026, and each one was followed by a deposit sweep into the collecting wallet.
  • Treasury TRX: CoinDCX-labelled treasury wallets sent 14,519 TRX to that fee wallet between April and August 2026, after Gupta said no current address had funded the flagged wallets.
  • Older births: Of the 40 drained wallets, 26 were in use before 2025, and none was first used in January 2025, the month CoinDCX cited.
  • Older keys: The thief also held keys to a hot wallet that went quiet in October 2023 and to another wallet funded by a CoinDCX cold wallet earlier in 2026, which points to a store of keys rather than one leftover address.

On TRON, a fresh deposit address holds no TRX, so the exchange sends 15 TRX of gas before each sweep. A machine that is still paying that gas is still holding the keys. Bitquery’s reading is that CoinDCX held those keys on the morning of October 21. The public record does not show how the thief obtained a copy.

Gupta’s False Alarm Collapsed the Same Day

Sumit Gupta, CoinDCX’s co-founder and CEO, spent the morning of October 22 telling people the reports were wrong. “Thanks for highlighting but this is incorrect and CoinDCX wallets are not breached,” he wrote, adding that “the hackers seem to be re-using the old wallet addresses and this sounds like a false alarm.”

The official CoinDCX account went further. It called the claims misleading, said the addresses were created in January 2025, compromised in July 2025, and “have not been used by CoinDCX since,” and said the activity “does not have any connection with CoinDCX.” It pointed readers to its public reserve list and said trading was normal.

ZachXBT replied that the TQKJQ deposit address was still sweeping user deposits in 2026, including gas, into CoinDCX’s current public hot wallet as recently as April and May 2026.

CoinDCX deposit address TQKJQ was in use by a LP for 10 months after your July 2025 incident and swept user deposits + received gas as recent as April & May 2026 to your current public hot wallet. Meaning $15.8M in user deposits was unaccounted for by your team.

ZachXBT, on-chain investigator, on X

Gupta answered that the team was aware and investigating. “We assure that no user funds will be at loss,” he wrote. Later that day CoinDCX posted the sweep-failure note, said the break was “identified today morning,” and said it had absorbed the operational losses and credited the affected deposit wallets.

THE OCTOBER 21 TO 25 CLOCK

  1. October 21, 2026: A thief empties 40 TRON wallets tied to CoinDCX and takes 15.99 million USDT, with the 15,819,002 USDT TQKJQ transfer at 15:35 UTC.
  2. October 22, 2026, 05:30 GMT: Darcy flags the outflows to the new address TAg6SZ1HhgVVjUaKY1paQoFBUS2JFrg5bT.
  3. October 22, 2026, 08:14 GMT: CoinDCX says the addresses have not been used since July 2025 and the activity has no connection with the exchange.
  4. October 22, 2026, 08:52 GMT: ZachXBT posts that TQKJQ was still in use by a liquidity provider into April and May 2026.
  5. October 22, 2026, 09:59 GMT: Gupta says the team is investigating and that no user funds will be at loss.
  6. October 22, 2026, 11:47 GMT: CoinDCX says the sweeping process failed for a particular period and that it absorbed the losses.
  7. October 22, 2026, 22:45 UTC: Tether freezes 2,212,850 USDT across nine wallets.
  8. October 25, 2026: CoinDCX publishes its full update on the on-chain activity and puts the absorbed loss at 15.99 million USDT.

The Sunday post is more precise than the Thursday note, and it is also more careful. “This wallet belongs to our old operational wallet infrastructure, which was compromised during the security incident we reported on July 19, 2025, and was deprecated as a result,” CoinDCX wrote. It still does not call the October movement a hack and does not say who signed the transfers. “We could have been more proactive, but we shared this update as soon as we had the complete picture,” it added.

That sequence is why the false alarm stings. The chain was public. The first corporate line was that the wallets were someone else’s problem. The second line, hours later, was that the company would pay.

Where the 15.99 Million USDT Went Next

From the new address the thief split the USDT across six wallets, four of them brand new. Within about 18 hours, about $9.63 million had reached deposit addresses at OKX, Binance and Gate. Exchange deposits carry account records, which is where investigators can still attach a name.

WHERE THE USDT LANDED

Destination USDT
OKX deposit addresses 5,461,300
Binance deposit addresses 2,772,797
Gate 1,392,200

Bitquery also followed about $4.17 million into wallets it could not tie to an exchange, and about $100,000 off TRON through bridges. Those paths are separate from the three exchange totals above. Late on October 22, Tether froze 2,212,850 USDT in nine wallets in one batch, about 14% of the 15.99 million USDT taken, and about 31 hours after the main TQKJQ transfer. Two of the thief’s wallets, holding 29,956 USDT, were left out of that freeze as of 18:55 UTC on October 23.

The freeze is a later status of coins that had not yet reached those three exchanges, not a fourth slice of the same 15.99 million USDT. Most of the money had already moved. CoinDCX has not said whether it has opened cases with OKX, Binance or Gate, or whether it expects any of the frozen USDT back.

July 2025 Already Hit the Same Treasury

This is the second time in 15 months CoinDCX has told customers that a hole in its own stack will be paid from company reserves. On July 19, 2025, Gupta said an internal operational account used only for liquidity on a partner exchange had been compromised in a server breach. The drain was about $44.2 million. Customer assets, he said then as now, sat in segregated cold wallets and were not touched.

CoinDCX isolated the account, said trading and INR withdrawals were still up, and worked with the Indian Computer Emergency Response Team. It absorbed that loss from treasury too. The October wallets, in the company’s telling, belong to the same old operational set that was compromised in that incident and then retired.

Retirement, as the October chain shows, did not mean the addresses stopped taking money, stopped being swept, or stopped receiving gas from a live CoinDCX fee wallet. It meant the company no longer wanted them used, while still honouring deposits that arrived there. That is a customer-service choice. It is also how 15.99 million USDT ended up in a wallet the firm had already declared burned.

ZachXBT put CoinDCX in a line with WazirX and BitBNS. Indian traders who already refuse domestic exchanges did not need a new reason. The new fact is narrower: a deposit address copied last year does not become safe because an exchange marked it deprecated. It stays a live inbox until inbound payments are rejected and the keys are gone.

CoinDCX Still Has Not Named Who Held the Keys

The company says customer balances, current central and user addresses, and trading were not hit, and that it will not pass the 15.99 million USDT on to users. It also says support for retired deposit addresses is temporary and that it will watch older wallet systems more closely. It has not said when the sweeper stopped, how many users paid the old addresses, or how a thief signed transactions from wallets CoinDCX was still sweeping that morning.

WHAT WE KNOW

  • The loss CoinDCX booked: 15.99 million USDT, absorbed by the company, with affected deposit wallets credited.
  • The on-chain take: 15.99 million USDT and 5,783.81 TRX left 40 TRON wallets on October 21, including 15,819,002 USDT from TQKJQ.
  • The freeze: Tether locked 2,212,850 USDT in nine wallets on October 22.
  • Live systems: CoinDCX says segregated cold wallets, active addresses, and trading were not compromised.

WHAT IS UNCONFIRMED

  • The signer: CoinDCX has not said who moved the funds or how they obtained the private keys.
  • The gap: It has not said how long the sweep was down, or why TQKJQ’s 88 deposits were skipped while 518 other addresses were swept on March 11.
  • The books: Bitquery cannot see whether those 88 deposits were credited internally before the coins were taken.
  • The recovery: No public figure has been given for funds returned from OKX, Binance, Gate, or the Tether freeze.

Users who still keep last year’s deposit string in a notepad are the ones this design punishes twice, first with delay, then with a company statement that the address was deprecated all along. CoinDCX paid this bill. It has not yet said who else had the keys.

Disclaimer: This article is news reporting on CoinDCX’s October 2026 wallet incident and is for information only. It is not investment, trading, tax or legal advice, and it does not tell anyone to keep, move or withdraw crypto. Readers who hold an account should consult a qualified financial adviser and read CoinDCX’s own notices before making any decision about funds. Amounts, freeze lists and wallet statuses reflect the company statements and on-chain records cited above as of the dates given, and they can change if more USDT is frozen or if the exchange publishes a fuller incident report.

Harry is the editor of CRYPTO QUILL. He owns the site and runs it independently, covering bitcoin, altcoins, exchanges, DeFi, NFTs and the regulation of blockchain markets. His ten years in journalism began as a reporter and ended up in the editor's chair, with most of that decade spent on digital asset markets. He works from primary material rather than press releases: on-chain records pulled from block explorers, exchange order book and volume data, proof of reserves attestations, token unlock schedules, court dockets, and the enforcement actions and consultations published by financial regulators. Market figures are checked against at least two independent data sources before they appear, and if a number later proves wrong the article is corrected in place under the site's public corrections policy. Harry does not give investment advice; crypto rules differ by jurisdiction and prices can go to zero, so readers should treat every story as information, not a recommendation. Reader mail is answered at support@cryptoquill.com.

Click to comment

Leave a Reply

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

Trending