JC
James Crawford
October 23, 2026 · 3 min read
News

CoinDCX Users Hit by Faulty Wallet Sweep, Potential Losses Reported

CoinDCX Users Hit by Faulty Wallet Sweep, Potential Losses Reported

Technical Glitch Behind the Sweep Failure

CoinDCX, a major Indian cryptocurrency exchange, disclosed that a malfunction in sweeping deposits from outdated wallet addresses led to financial losses it has absorbed. The issue affected users who had funds in the deprecated wallets, and the exchange says it has credited the impacted accounts. Independent analyst ZachXBT claims that $15.8 million in user deposits may be missing, a figure the exchange has not confirmed.

Breaking news

Dogecoin Bounces Back After Brutal 65% Year-Long SlideDogecoin Bounces Back After Brutal 65% Year-Long SlideBitcoin Miners Face Hardware Shortage as AI Boom Strains Chip SupplyBitcoin Miners Face Hardware Shortage as AI Boom Strains Chip SupplyClaude AI Forecasts Chainlink Plunge in 2027Claude AI Forecasts Chainlink Plunge in 2027XRP Crashes to $0.87 as ETF Assets Fall Below $1 BillionXRP Crashes to $0.87 as ETF Assets Fall Below $1 Billion

The problem arose when CoinDCX attempted to consolidate funds from old wallet addresses into newer ones, a routine process meant to streamline operations. A technical failure prevented the sweep from completing, leaving a sizable amount of USDT stranded. CoinDCX says it identified the error, covered the shortfall internally, and restored the balances for affected customers. ZachXBT, a well‑known crypto researcher, pointed to a blockchain transaction of 15,819,002 USDT as evidence that a large token movement occurred, though he cautioned that the transaction alone does not prove loss of user funds.

CoinDCX explained that the sweep script malfunctioned due to a mismatch in address formats after a recent system upgrade. The exchange’s engineering team halted the process once the discrepancy was detected, but not before a batch of deposits remained in the old wallets. Internal audits revealed that the missing USDT amounted to millions of dollars, prompting the exchange to allocate emergency reserves to cover the gap. „We take full responsibility and have taken steps to ensure this does not happen again,” a CoinDCX spokesperson said. The company also announced tighter monitoring of wallet migrations and a review of its internal controls.

Did Users Actually Lose Money, or Was It a Misunderstanding?

ZachXBT’s allegation that $15.8 million vanished stems from the same blockchain trace that shows a massive USDT transfer. However, CoinDCX maintains that the transfer was part of the sweep attempt and that all user balances were restored after the error was discovered. The exchange has not provided a public audit confirming the exact amount recovered, leaving some users skeptical. „We are waiting for an independent verification,” one affected trader told a crypto forum. The lack of transparent proof fuels ongoing debate about the true scale of the incident.

The episode underscores the risks inherent in centralized exchanges handling large volumes of digital assets. While CoinDCX’s decision to absorb the loss may reassure some customers, the episode could erode trust among others and invite regulatory scrutiny. Industry observers expect tighter oversight of wallet management practices, especially as exchanges expand their user bases.

Frequently Asked Questions

What caused the deposit sweep to fail? A software error during a system upgrade misaligned address formats, preventing the automatic transfer of funds from old wallets to new ones.

Has CoinDCX reimbursed all affected users? The exchange says it has credited the accounts of those impacted, but it has not released an independent audit confirming the total amount restored.

Will this incident affect future regulations for crypto exchanges in India? Regulators are likely to examine the case closely, potentially leading to stricter guidelines on wallet management and user fund protection.

More stories:

Share:

Leave a comment

All comments are reviewed first. Yours will appear once approved. Maximum 2 comments per hour.