Unocoin said on November 14 that unauthorized transactions compromised three of its operational hot wallets and caused an estimated cryptocurrency loss of approximately $200,000. The Indian exchange said it would absorb the loss rather than reduce customer balances, but its investigation into the signing-key compromise and possible customer-data exposure remains open.

The update matters because Unocoin had asked BitGo to freeze its enterprise account on November 6. BitGo says that freeze worked as designed: it stopped BitGo from signing or processing transactions through its platform. It did not disable the separate pair of customer-controlled keys that could independently satisfy the wallet’s signature requirement.

A freeze at the provider was not an on-chain lock

Unocoin said it detected suspicious infrastructure activity on November 6 and requested freezes from Fireblocks at 11:24 UTC and BitGo at 11:29 UTC. It later suspended all platform services after finding further unauthorized activity on November 9.

The November 14 disclosure revised the exchange’s earlier assessment that no cryptocurrency had been lost. Unocoin said three of more than 20 wallets used for operations, including withdrawals, were compromised. Its approximately $200,000 estimate covers the incident as understood on November 14; the company did not publish a transaction-by-transaction reconciliation, identify the amount it said had been frozen through industry partners or provide a completed recovery total.

BitGo’s November 13 review explains the control boundary. The examined Ethereum wallet used a two-of-three multisignature arrangement: Unocoin controlled a user key and a backup key, while BitGo controlled the third. Normal withdrawals used the user and BitGo keys. The unauthorized Ethereum transfers instead used Unocoin’s user and backup keys and were broadcast without BitGo’s platform or key, according to BitGo.

That means “frozen” described BitGo’s participation, not the wallet contract itself. A party controlling the other two keys could still produce a valid transaction. BitGo said transaction-building requests submitted through its platform on November 9 were blocked, while separate on-chain transfers proceeded outside it.

The backup path became the incident path

Unocoin said the encrypted backup keys had been generated about eight years earlier, printed and placed in physical storage. It now says those keys were compromised, but it has not established how they were accessed or how the sequence unfolded. The exchange also said the affected transactions were signed with Unocoin-controlled keys and that its analysis found no compromise of BitGo’s infrastructure.

BitGo identified transfers involving ERC-20 tokens on Ethereum, XRP, HBAR and EOS. Its detailed public signing analysis covered the Ethereum wallet, where it matched the two signing addresses to Unocoin’s user and backup key records. That supports the signing route, but it does not identify the person who controlled the keys during the transfers.

An attributable Bitquery reconstruction independently traced 98 Ethereum payouts between November 9 and November 11 from one wallet that BitGo linked to the incident. Bitquery valued 96 transferred assets at $182,270 using its price for each token when it moved, while excluding 34 tokens without prices and warning that three thinly traded tokens might not have realized their displayed values. Its Ethereum dataset ended at 08:37 UTC on November 13 and did not cover every wallet or chain in Unocoin’s companywide estimate.

Customer impact is still partly unverified

Unocoin said the estimated loss was significantly less than 1% of cryptocurrency held for customers and promised to fund it from company resources. Those are company assertions, not proof that every customer balance or withdrawal claim has been reconciled.

The exchange also listed email addresses, residential addresses, encrypted passwords, know-your-customer information and token balances as potentially exposed. It said it had found no evidence that KYC documents were accessed, while emphasizing that the investigation was continuing.

The defensible conclusion on November 15 is therefore narrower than a completed postmortem: Unocoin has acknowledged an estimated $200,000 loss across three hot wallets, and public signing evidence shows how two customer-controlled keys could move assets despite a provider-level freeze. The root cause, final loss, data-access scope, frozen amount and service-restoration status still require follow-up.

Primary sourceUnocoin security incident update — November 14, 2026 ↗

The complete source packet and revision history are retained with the newsroom record.

Automated desk disclosure

Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.

Financial-risk note

This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.