Blog
Miniature diorama of an open crypto vault with glowing keys, one missing, illustrating the Unocoin breach

November 15, 20265 min readАдминистратор

Unocoin breach: how a multisig backup key became the weak spot

India's oldest crypto exchange Unocoin froze its custody accounts, yet funds still moved: BitGo says the transactions were signed with keys Unocoin held itself. What the Unocoin breach means for PSPs and trader teams that settle in crypto.

For many payment teams in India, crypto is not an investment — it is plumbing. P2P trader teams, PSPs and aggregators move collateral, settle with merchants and rebalance liquidity in USDT, often through local exchanges and institutional custody wallets. So when one of India's oldest exchanges goes dark for a week, the question is not "what happens to Bitcoin" but "what happens to my settlement float".

That is why the Unocoin breach deserves a close look. The exchange did the textbook thing — it froze its custody accounts within minutes — and funds still moved. According to its custodian, the outgoing transactions were signed with keys Unocoin held itself. This is a breakdown based on public statements by Unocoin, BitGo and on-chain analysts. The investigation is ongoing, the final loss has not been disclosed, and some details may change.

What happened

Bengaluru-based Unocoin, founded in 2013, says it detected unauthorised activity on 6 November 2026. Within minutes it asked its two institutional custody providers to freeze its enterprise accounts: Fireblocks at 11:24 UTC and BitGo at 11:29 UTC. Both confirmed the freezes, and at that point no loss of funds had been identified.

On 9 November the exchange detected further unauthorised activity, concluded that its infrastructure had been compromised and suspended all services, including customer logins, trading and withdrawals. Unocoin decided to rebuild its servers from scratch, a process it estimated at four to five working days.

On 12 November Unocoin reported outgoing transactions from an Ethereum address in its BitGo wallet setup that had been used to fund ERC-20 tokens. The same day, an on-chain monitoring account pointed out that Arkham Intelligence showed roughly 81,000 Unocoin-attributed addresses with a zero balance, which quickly turned into headlines about 81,000 drained wallets.

That headline needs care. Arkham's attribution does not cover an exchange's full custody setup, and Bitcoin.com News noted that those addresses had held only hundreds of dollars in total over the previous month, with a three-month peak just above $250,000. A zero balance on labelled addresses is not proof that 81,000 customer accounts were emptied. Unocoin, for its part, says more than 90% of customer crypto sits in cold storage.

How it works: the multisig backup path

The key detail came on 13 November. BitGo stated that its systems were not breached and that the freeze worked as intended. Its wallets use a 2-of-3 multisignature model: one key held by the client, one backup key and one key held by BitGo. The custodian said the disputed transactions were signed with the user and backup keys held by Unocoin and broadcast directly on-chain, without passing through BitGo's platform.

In other words, freezing the custodian's dashboard did not freeze the wallet. The backup path — designed so a client can recover funds if the custodian ever disappears — gave anyone holding two keys full control. Unocoin itself acknowledged that this backup mechanism appears to have been exploited. If both client-side keys were reachable from compromised infrastructure, the custodian's freeze was only a partial control.

This is the second warning from Indian exchanges in a month. In October 2026 CoinDCX confirmed a loss of about 15.99 million USDT from deprecated deposit wallets on Tron that kept receiving funds after an earlier breach, bringing its security losses since mid-2025 to roughly $60 million.

Why this matters for the payments market

  • Settlement float is exposed. Teams that park USDT on an exchange to settle with merchants or traders can lose access to working capital for days, even if no customer funds are ultimately lost.
  • "Institutional custody" is not a guarantee. Multisig only protects you if the keys are genuinely separated. Two keys on one compromised server equals a single key.
  • On-chain dashboards mislead both ways. Empty labelled addresses can look like a hack; healthy-looking balances can hide unlabelled outflows. Neither replaces a reconciled statement from the counterparty.
  • Outages ripple into fiat rails. When an exchange freezes, traders cannot convert, payouts stall and P2P collateral cannot be topped up — the shock hits UPI and IMPS flows downstream.

Checklist: protecting crypto settlement

  1. 1.Cap exposure per venue. Keep no more on any single exchange than you can afford to have locked for one to two weeks.
  2. 2.Ask how keys are split. For any custodian or exchange you rely on, ask who holds each multisig key and whether backup keys are stored offline, in separate locations, under separate access.
  3. 3.Treat a freeze as step one. Make sure your own incident plan covers moving or locking funds at the key level, not only in a vendor dashboard.
  4. 4.Retire old deposit addresses properly. Sweep them, monitor them and tell counterparties in writing to stop using them.
  5. 5.Reconcile daily, not weekly. Match exchange statements with your ledger and on-chain data so gaps surface early.
  6. 6.Keep a second off-ramp ready. Pre-verified accounts on at least one alternative venue shorten downtime if your main exchange halts.
  7. 7.Put SLAs in writing. Agree on notification times and withdrawal timelines in contracts with exchanges and liquidity providers.

If you are reviewing partners for India, start with the PSP catalogue for India and the UPI method page, or post what you need on the requests board. Related reading: what to do in the first hours of a payment freeze, how to vet a P2P processor before serious volume and FATF on how fraud money moves.

FAQ

Were 81,000 Unocoin customer wallets drained? Not proven. Arkham shows about 81,000 attributed addresses at zero balance, but those addresses held relatively small sums historically, and attribution does not cover the full custody setup. Unocoin has not disclosed a final loss figure.

Was BitGo hacked? BitGo says no. It states that its freeze worked and that the transactions were signed with two keys held by Unocoin and broadcast outside its platform.

Why didn't freezing the custody accounts stop the transfers? In a 2-of-3 multisig, the client's own key plus the backup key are enough to sign. Freezing the custodian's side blocks only the custodian's key, not a client who controls the other two.

What should trader teams do right now? Check how much of your float sits on any single exchange, confirm how your custody keys are separated, and make sure you have a tested alternative off-ramp before you need it.

Sources

  1. 1.Unocoin — Security Incident Update (12–13 Nov 2026)
  2. 2.Bitcoin.com News — Unocoin confirms server breach as Arkham shows 81K empty wallets
  3. 3.Arkham Intelligence — Unocoin entity
  4. 4.Bitcoin.com News — CoinDCX admits $16M hit from deprecated wallets
  5. 5.Платежки и хай риск — Индия: 81 000 кошельков Unocoin

Comments · 0

No comments yet — be the first.

Log in · log in to leave a comment.