T
iTokenly

Unocoin BitGo wallet (November 2026) hack — November 2026

Verified — 5 sourcesLast checked November 18, 2026

Incident facts

Date of incident
Publicly disclosedNovember 12, 2026
Target typeCentralised exchange
Loss$224,970Price at time of incident
MethodPrivate key compromiseAfter intruders reached Unocoin's servers, an Ethereum BitGo multisig wallet was emptied with transactions signed by the user key and the backup key held by Unocoin; BitGo's own key, frozen since 6 November, was not needed for a 2-of-3 signature
ChainsEthereum, XRP Ledger
OutcomeUnresolved

What happened

Unocoin, an Indian crypto exchange founded in 2013, detected unauthorised activity on 6 November 2026 and asked its custody providers Fireblocks and BitGo to freeze its enterprise accounts. After further unauthorised activity on 9 November it suspended all services, found that its infrastructure had been compromised, and began rebuilding its servers. On 12 November it disclosed outgoing transactions it could not trace from one of its Ethereum addresses in BitGo, used to fund ERC-20 tokens. BitGo told Unchained the transaction was signed with the user and backup keys held by Unocoin and broadcast without BitGo, whose freeze worked as intended and whose systems were not breached.

Unocoin has not given an amount, and on 13 November it still said no crypto funds had been lost while describing the backup mechanism as exploited. BitGo's own post of 13 November names the two addresses that signed the Ethereum transfers, Unocoin's backup and user keys, and says Unocoin has confirmed them; they match the wallet Bitquery identified, a BitGo wallet opened in May 2018. Between 9 and 11 November the backup key emptied it of ETH and 95 tokens worth $182,270 at the time of each transfer; the first transfer came six minutes after Unocoin posted that no funds were lost. A second Unocoin account on the XRP Ledger lost 39,167 XRP, about $42,700, four minutes after the Ethereum theft began, bringing the traced total to about $225,000 (the figure here). Without three thinly traded tokens (FUN, MTL, QRL) the total is about $198,700, the low end. BitGo says HBAR and EOS also moved; those are not traced or counted.

Most of the Ethereum money was swapped to ETH and sent through no-account swap services within hours. Unocoin says more than 90% of customer crypto is in cold storage and has not said whether any user balances were affected.

Sources

  1. Unocoin on X: update of 13 November 2026Primary · retrieved 2026-11-13
  2. Unocoin on X: update of 9 November 2026Primary · retrieved 2026-11-13
  3. Unchained (12 November 2026, updated 13 November with BitGo's statement)Secondary · retrieved 2026-11-13
  4. Bitquery investigation (13 November 2026)Secondary · retrieved 2026-11-13
  5. BitGo: Unocoin security incident (13 November 2026)Primary · retrieved 2026-11-18

Changes to this entry

  • Added as reported at Bitquery's $182,270 (96 assets priced at each transfer; low $156k excludes FUN, MTL, QRL). The wallet match is Bitquery's and is not confirmed by Unocoin, which still says no crypto funds were lost. Promote once Unocoin or BitGo confirms the address or a loss figure.
  • Reported → verified. BitGo's 13 Nov post names the signing addresses (Unocoin's backup and user keys, which Unocoin has confirmed) — the same keys Bitquery found on the emptied wallet. Amount $182,270 → $224,970: Bitquery's updated report adds 39,167 XRP (~$42,700) taken from a second Unocoin account on the XRP Ledger; low $156k → $198.7k. HBAR and EOS also moved per BitGo but are not traced or counted.

Cite this

This data is published under CC BY 4.0. You may reuse it, including commercially, as long as you credit iTokenly and link back.

iTokenly Hack Registry, "Unocoin BitGo wallet (November 2026) hack — November 2026", iTokenly, accessed 2026-11-18, https://itokenly.com/hacks/unocoin-bitgo-wallet-november-2026
https://itokenly.com/hacks/unocoin-bitgo-wallet-november-2026

Permalinks never change. If an entry is renamed, the old address keeps working.

Spotted an error? Write to [email protected]. Corrections to published figures are logged on this page. See the methodology for how entries are checked.