India's Largest Crypto Exchange Absorbs $16 Million Loss After Internal Wallet Failure

The Mumbai-based exchange initially dismissed reports of suspicious outflows as a false alarm, but now confirms it lost $16 million through an internal process failure tied to a retired wallet and will cover the loss from its own reserves.

India's largest cryptocurrency exchange has confirmed it lost $16 million in customer funds due to an internal operational failure involving a retired wallet, reversing its earlier dismissal of reports as unfounded alarm. The Mumbai-based platform announced it will absorb the entire loss from its own capital reserves rather than passing costs to customers, a decision that preserves user balances but raises questions about internal controls at a major market player.

The loss stems from what the exchange describes as a 'process failure' related to a wallet that had been taken out of active service. Blockchain observers first flagged suspicious outflows from addresses associated with the platform several days before the official confirmation, prompting the exchange to initially issue a statement characterizing the concerns as a 'false alarm' with no actual loss of funds.

That initial denial has now been retracted. The exchange's updated statement acknowledges the $16 million shortfall and commits to making customers whole from company reserves, effectively treating the incident as an operational cost rather than a customer liability. The decision mirrors the approach taken by some Western exchanges after security incidents, where platforms with strong balance sheets choose to absorb losses to maintain user trust.

Internal process failures differ from external hacks in that they typically involve human error, misconfigured systems, or gaps in operational procedures rather than malicious third-party attacks. In this case, the involvement of a 'retired' wallet suggests the funds may have been moved through outdated or improperly secured infrastructure, though the exchange has not disclosed technical details of how the loss occurred or whether any individuals have been held accountable.

The incident arrives as India's crypto regulatory framework remains in flux. While the country has imposed a 30% tax on crypto gains and a 1% tax deducted at source on transactions, comprehensive licensing and custody standards for exchanges are still under development. The lack of mandatory insurance or reserve requirements means that an exchange's decision to cover a loss from its own funds is voluntary rather than legally mandated.

For Indian crypto users, the episode underscores the importance of platform selection and the risks inherent in custodial services, where exchanges hold private keys on behalf of customers. While the exchange's decision to cover the loss protects affected users in this instance, customers at platforms with weaker balance sheets might not receive the same treatment in similar circumstances. Industry observers note that transparent disclosure of reserve audits and insurance coverage remains rare among Indian exchanges, leaving users with limited information to assess counterparty risk.

The exchange has not announced changes to its security or operational procedures in response to the incident, nor has it clarified whether the loss was the result of a single event or discovered through a broader audit. As Indian regulators work toward a more comprehensive licensing regime for digital asset platforms, incidents like this are likely to inform discussions around minimum capital requirements, custody standards, and mandatory insurance for customer funds.