← Back to all guides

Security

Unocoin Admits $200,000 Crypto Theft: An India Guide

9 min readCrypto Beginner Editorial Team15 Nov 2026
Unocoin Admits $200,000 Crypto Theft: An India Guide

Unocoin has confirmed that about $200,000 in cryptocurrency was stolen from its hot wallets — reversing the assurance it gave Indian users five days earlier that no funds had been lost. The admission, published on 14 November 2026, is the first time the exchange has put a number on the security incident that has kept its services suspended since 9 November, and it comes with a second warning: customer data, including email addresses, home addresses, encrypted passwords, balances and KYC information, may also have been exposed. This guide explains what Unocoin said, how the theft worked, what the independent on-chain evidence shows, and what Indian users should do now — without speculating about anything the investigation has not established.

> Educational content only. This is not financial advice. Crypto markets are volatile — never invest money you can't afford to lose. This guide explains a security incident; it does not recommend buying, selling or holding any asset.

What Happened: The Facts at a Glance

The facts, as reported on 14–15 November 2026 by Bitcoin.com News, Dave Finances and CryptoGuru, and corroborated by BitGo's own technical blog and Bitquery's on-chain investigation, are:

  • About $200,000 stolen. Unocoin confirmed on Saturday 14 November that attackers stole approximately $200,000 in cryptocurrency from three of its more than 20 operational hot wallets. At roughly ₹94 to the dollar, that is about ₹1.88 crore. The exchange says the loss is significantly less than 1% of the cryptocurrency it holds for customers, and that it will cover the loss from its own resources rather than deducting funds from customer balances.
  • A reversal of the earlier assurance. On 9 November, when Unocoin suspended services and disabled customer logins, it told users that no cryptocurrency funds had been lost. The 14 November disclosure reverses that: funds were lost, and the exchange's own statement now acknowledges it. The reversal matters because users spent five days believing their funds were untouched.
  • Old backup keys were the weak point. Investigators determined that the attackers compromised Unocoin's backup signing keys — encrypted keys generated approximately eight years ago, printed on paper and placed in secure physical storage. A decryption passphrase for those printed backups existed inside Unocoin's compromised infrastructure. How the attackers obtained usable signing credentials has not been established, and the investigation is still running.
  • The theft bypassed the freeze. Unocoin froze its BitGo enterprise account on 6 November, and BitGo confirms the freeze worked as intended. But the attackers signed transfers with Unocoin's own two keys and broadcast them directly to the blockchain, outside BitGo's platform — so the freeze could not stop them.
  • Customer data may be exposed. Unocoin warned that registered email addresses, residential addresses, encrypted passwords, account balances and KYC-related information may have been exposed through the compromised infrastructure. It says investigators have found no evidence that identity-verification documents were accessed, and it has not confirmed whether the exposed information was actually extracted by the attackers.
  • Services are still suspended. Unocoin has suspended all deposits and withdrawals since 9 November, with no confirmed resumption date at the time of writing, though Indian media reports have pointed to a 17 November target. The exchange is rebuilding its server infrastructure, a process it estimated on 12 November would take four to five working days.

The Reversal: From "No Funds Lost" to $200,000

The most important part of this story is not the size of the loss. Two hundred thousand dollars is small next to the billions stolen in the Binance hack a fortnight earlier, and Unocoin says it is less than 1% of customer assets. What matters is the reversal — and what it tells Indian users about how to read exchange statements during a live incident.

The timeline, as established by Unocoin's own updates and the reporting that followed, runs like this. On 6 November, Unocoin detected suspicious activity in its infrastructure and requested freezes on its enterprise accounts with Fireblocks at 11:24 UTC and BitGo at 11:29 UTC. Both custody providers confirmed the restrictions. At that stage, no losses had been identified — the freezes were precautionary, taken while the exchange investigated the extent of the compromise.

Three days later, on 9 November, additional suspicious activity prompted Unocoin to publish an update, suspend all services and disable customer logins. The company acknowledged that its infrastructure had been compromised, but it reiterated that no cryptocurrency funds had been lost. That statement held for five days. On 12 November, a further security update described unauthorised server access, outgoing transactions from a BitGo-held Ethereum wallet, and a server rebuild estimated at four to five working days — but still no loss figure.

On 13 November, BitGo published its own technical investigation. It established that the unauthorised Ethereum transfers had been signed using two keys controlled by Unocoin, that BitGo's own signing key was not involved, and that the transactions had been broadcast directly to the blockchain outside BitGo's platform. BitGo said its infrastructure had not been breached and other customers were unaffected.

On 14 November, Unocoin published its update confirming the approximately $200,000 loss across three hot wallets, the compromised backup keys, and the possible customer-data exposure. The sequence is a textbook example of why early incident statements should be read as provisional: on 9 November, Unocoin genuinely appears not to have known funds were missing — the outgoing transfers were only identified as the investigation progressed. But for users, the practical lesson is the same either way: an exchange saying "no funds lost" in the first days of an incident is a statement about what it has found so far, not a guarantee about what it will find next.

How the Theft Worked: Two Keys and a Frozen Third

To understand how funds could leave a wallet whose custodian account was frozen, it helps to understand how Unocoin's wallet was set up. The affected Ethereum wallet used a two-of-three multisignature arrangement — a common security design in which three keys exist and any two of them together can authorise a transfer. Unocoin controlled two of the keys, the user key and the backup key. BitGo controlled the third.

In normal operation, a withdrawal from this wallet used the user key and BitGo's key, with BitGo applying its security checks and any configured policies before signing. The backup key existed for emergencies: in a self-custody arrangement, the backup key lets the customer move funds independently if the custodian becomes unavailable — for example, if BitGo's systems go down. That design is a feature, not a flaw, when the backup key is properly protected. It becomes the vulnerability when the backup key itself is compromised.

That is what happened here. BitGo's technical analysis matched the signing addresses in the unauthorised transactions to the wallet's key records and found that the transfers were signed with Unocoin's user key and backup key. BitGo's key was not used in any of the reviewed Ethereum transactions, and BitGo found no corresponding transaction-initiation records on its own platform. The transactions were broadcast directly to the blockchain, outside BitGo's systems. The enterprise freeze Unocoin requested on 6 November worked exactly as intended — BitGo's blog notes that transaction-building requests submitted through BitGo on 9 November were blocked by the freeze, and the last transaction signed through BitGo's normal process occurred on 6 November, before the freeze. But a freeze on BitGo's key cannot stop two other keys from signing together. The attackers did not need BitGo at all.

The backup keys themselves tell a story about how long security debt can sit quietly in a system. According to Unocoin, the encrypted backup signing keys were generated approximately eight years ago, printed on paper and placed in secure physical storage. Eight years is a long time for a credential to exist, and the investigation found that a decryption passphrase associated with those printed backups existed within Unocoin's compromised infrastructure. In other words, the encrypted paper backups were protected by a passphrase, and that passphrase was stored in the same infrastructure the attackers had compromised. The precise method by which the attackers obtained usable signing credentials has not been established — whether they decrypted the paper backups, found the keys elsewhere, or obtained them another way remains under investigation. BitGo has advised Unocoin to move its remaining funds to new wallets backed by newly generated keys.

What the On-Chain Evidence Shows: Bitquery's $182,270 Trace

While Unocoin and BitGo were publishing their findings, blockchain analytics firm Bitquery was independently tracing the suspicious transactions, and its results — published with figures verified through 14 November — add a concrete, checkable layer to the story.

Bitquery identified an Ethereum multisignature wallet it links to Unocoin that lost approximately $182,270 in Ether and other tokens between 9 and 11 November, across 98 successful outgoing transfers involving 96 different assets. The wallet, 0x41ade1cd005741bd093b4df7391fdd8347dc42ee, uses a two-of-three multisignature structure consistent with BitGo's wallet architecture, and Bitquery connected it to Unocoin through an Ethereum deposit address previously identified in a public customer post from May 2018.

Two details in Bitquery's reconstruction stand out. First, the speed: the attacker removed Ether, BAT and USDT worth approximately $78,000 within the first minute of activity, and the backup-key address received a small amount of Ether to pay transaction fees just 48 seconds before its first outgoing transaction — the kind of preparation that shows the transfers were planned, not opportunistic. Second, the key-usage pattern: Bitquery found 124 outgoing transaction requests initiated using the backup key, of which 26 failed, and the backup key had been unused in the wallet's earlier history — routine transactions had always been signed through BitGo. The freeze worked, yet the assets could still move, because the user key and backup key together were enough.

One caveat matters, and Bitquery states it plainly: Unocoin has not confirmed that it owns the wallet Bitquery identified. The $182,270 figure is therefore an independently calculated estimate for one address, not an officially established exchange-wide loss. It is close to Unocoin's own $200,000 figure — the difference is consistent with the two other hot wallets Unocoin says were affected, and with the $182,270 covering only Ethereum and ERC-20 tokens in one wallet, while Unocoin's figure covers three wallets. BitGo's own review also identified transfers involving XRP on the XRP Ledger, HBAR on Hedera and EOS, which Bitquery's Ethereum-focused trace would not capture. The numbers point in the same direction, but they are not the same number, and they should not be quoted as if they were.

The Customer Data Warning: What May Be Exposed

The second half of Unocoin's 14 November update is, for many users, the more worrying part. Beyond the cryptocurrency theft, Unocoin acknowledged that portions of its infrastructure may have exposed registered email addresses, residential addresses, encrypted passwords, account balances and KYC-related information.

Three careful distinctions are needed here. First, "may have been exposed" is not the same as "was stolen". Unocoin has not confirmed whether the potentially exposed information was actually extracted by the attackers, and its investigation into possible unauthorised access is ongoing. Second, the passwords were encrypted, which means they are not immediately usable — though encrypted passwords can still be attacked, and users who reused the same password elsewhere should act as if it is compromised. Third, Unocoin says investigators have found no evidence that actual identity-verification documents — the ID proofs submitted during KYC — were accessed. That is the most sensitive category of data an exchange holds, and so far there is no evidence it was taken.

Even so, the exposure list is exactly the combination attackers use for follow-on fraud. An email address plus a home address plus a balance is enough to craft a convincing phishing message: "your Unocoin account held ₹X, click here to recover it." A list of registered emails is enough to run a wave of fake Unocoin password-reset messages. And encrypted passwords, if they are ever decrypted, open every other account where the same password was reused. The data warning is therefore not a footnote to the theft — for most Unocoin users, whose individual balances are far below the $200,000 total, it is the part of the incident most likely to affect them personally.

What Unocoin Says It Will Do Next

Unocoin has made three commitments in its 14 November update. First, it will cover the approximately $200,000 loss from its own resources, so customer balances should not be reduced by the theft. Second, it is rebuilding its server infrastructure, a process it estimated on 12 November would take four to five working days, with services suspended until the rebuild is complete. Third, it says some of the affected cryptocurrency has been frozen through coordination with industry partners, though it has not disclosed how much was recovered or restricted.

Indian media reports have pointed to Tuesday 17 November as a resumption target, but that date has not been confirmed by Unocoin itself in the material reviewed for this guide, and it should be treated as reported rather than promised — the 12 November update gave a rebuild estimate, not a reopening date. Users should check Unocoin's own channels for the resumption announcement rather than relying on a reported target.

It is also worth noting what Unocoin has not said. It has not named the attacker, and no government agency or security firm has attributed the incident to any group. It has not explained how the attackers first got into its infrastructure on 6 November. And it has not said whether it has filed a complaint with Indian law enforcement or the Financial Intelligence Unit — a step that matters, because the exchange is registered with FIU-IND and the incident involves both stolen funds and potentially exposed customer data.

What This Means for Indian Users

For Indian readers, the Unocoin incident lands in a week when the rupee on-ramp to crypto has already been fragile. Coinbase's INR withdrawals remain halted after an outage at its banking partner, ZebPay's INR withdrawals are delayed, and Unocoin itself has now been suspended for six days. Against that background, the practical points are these:

  • Do not try to move funds that cannot move. Unocoin's services — deposits, withdrawals and logins — have been suspended since 9 November. Attempting withdrawals during the suspension will fail or sit pending. Wait for Unocoin's own resumption announcement.
  • Change your passwords, starting with Unocoin. Once the service is back, change your Unocoin password, and change the same password anywhere else you used it. Encrypted passwords may have been exposed, and password reuse is the fastest way a breach at one exchange becomes a breach at another.
  • Turn on two-factor authentication everywhere. If you have not enabled two-factor authentication on your email account and on every exchange account you hold, do it now — before the service resumes, not after. An attacker with your email address and a stolen password still cannot get in if the account needs a second factor.
  • Expect phishing, and treat every Unocoin message as suspect. Attackers who hold customer email lists commonly send fake password-reset and "fund recovery" messages after a breach. Unocoin will not ask you for your password, your seed phrase or a payment to release your funds. Verify any message by going to Unocoin's own website or app directly, never by clicking a link in the message.
  • Check what you actually hold, when you can. Once services resume, verify your balances against your own records. Unocoin says it will cover the loss from its own resources, but confirming your own balance is a basic check that costs nothing.
  • The tax treatment is unchanged. The incident does not change Indian tax law. Gains on virtual digital assets are taxed at a flat 30% plus a 4% cess, with 1% TDS on transfers. Tax note: crypto tax rules can change — the 30% rate and 1% TDS described here were current as of September 2026. Verify the latest rules before filing. A loss caused by theft is not the same as a trading loss, and how it is treated for tax purposes is a question for a qualified tax adviser, not for this guide.

How This Differs From the Posts Already on This Site

This site has covered the Unocoin incident twice, but never this development. The post from 12 November covers the breach itself — the suspicious activity on 6 November, the unauthorised server access on 9 November, the service suspension and the four-to-five-day server rebuild — and it states explicitly that no loss figure had been confirmed. The post from 13 November covers the BitGo recovery-feature mechanism — how transfers could be signed outside a frozen platform — and it too states that no loss figure had been confirmed. Neither post covers the $200,000 loss figure, the reversal of the "no funds lost" assurance, the eight-year-old paper backup keys, the decryption passphrase inside the compromised infrastructure, Bitquery's $182,270 independent trace, or the customer-data exposure warning. This post is about the dated development of 14 November — the day Unocoin first admitted that funds were stolen and that customer data may have been exposed — and it should be read alongside the two earlier posts, not instead of them.

The Bottom Line

On 14 November 2026, Unocoin confirmed that about $200,000 in cryptocurrency — roughly ₹1.88 crore — was stolen from three of its more than 20 hot wallets, reversing its 9 November assurance that no funds had been lost. The theft was made possible by compromised backup signing keys generated about eight years ago and printed on paper, with a decryption passphrase sitting inside the infrastructure the attackers had already breached; the two Unocoin-controlled keys were enough to authorise transfers, so freezing the BitGo account could not stop them. Bitquery independently traced about $182,270 leaving one linked Ethereum wallet in 98 transfers between 9 and 11 November, though Unocoin has not confirmed it owns that wallet. Separately, Unocoin warned that email addresses, home addresses, encrypted passwords, balances and KYC information may have been exposed, while saying it has found no evidence that identity-verification documents were accessed. The exchange says it will cover the loss from its own resources, and its services remain suspended while it rebuilds its servers. For Indian users, the immediate steps are unglamorous and specific: change reused passwords, enable two-factor authentication, and treat every message claiming to be from Unocoin as suspect until the service is back.

Keep Learning

Frequently asked questions

How much crypto did Unocoin actually lose?

Unocoin confirmed on 14 November 2026 that attackers stole approximately $200,000 in cryptocurrency — about ₹1.88 crore at roughly ₹94 to the dollar — from three of its more than 20 operational hot wallets. The exchange says the loss is significantly less than 1% of the crypto it holds for customers, and that it will cover the loss from its own resources rather than deducting anything from customer balances. Separately, blockchain analytics firm Bitquery traced about $182,270 leaving one Ethereum wallet it links to Unocoin between 9 and 11 November, but Unocoin has not confirmed that it owns that wallet, so the Bitquery figure is an independent estimate for one address, not the official total.

How were the funds stolen if Unocoin had frozen its BitGo account?

Unocoin's affected wallet used a two-of-three multisignature setup: Unocoin controlled the user key and the backup key, while BitGo controlled the third key. Any two keys could authorise a transfer. On 6 November Unocoin froze its BitGo enterprise account, and BitGo's own blog confirms that the freeze worked as intended — no transaction needing BitGo's signature went through after it. But the attackers had Unocoin's backup signing key, so they could sign transfers with the user key and the backup key together and broadcast them directly to the blockchain, outside BitGo's platform. The freeze stopped BitGo's key from being used; it could not stop the two Unocoin-controlled keys from being used together.

I have a Unocoin account. What should I do right now?

First, do not panic-move funds you cannot move — Unocoin's services have been suspended since 9 November, so deposits, withdrawals and logins are unavailable while it rebuilds its servers. Second, change your Unocoin password once the service is back, and change it anywhere else you reused the same password, because Unocoin has warned that registered email addresses, residential addresses, encrypted passwords, balances and KYC information may have been exposed. Third, turn on two-factor authentication on your email and every exchange account, and treat any message claiming to be from Unocoin with suspicion — attackers who hold customer emails commonly send phishing messages after a breach. Unocoin says it has found no evidence that identity-verification documents were accessed, and it has not confirmed whether the exposed information was actually taken.

Related guides