Crypto exchange Unocoin said on Nov. 13 that disputed wallet transfers were signed and broadcast outside BitGo, while the freeze on its BitGo enterprise account had worked so far.
The exchange suspended all services on Nov. 9 after detecting further unauthorized activity. It had requested freezes on its enterprise accounts at BitGo and Fireblocks after initially detecting the activity on Nov. 6.
In its incident update, Unocoin said a backup mechanism designed to preserve access to funds if BitGo became unavailable appeared to have been exploited. It is still investigating how that mechanism was used, cryptocurrency losses, and potential information exposure.
Related Company BitGo Digital asset custody and wallet infrastructure
Two routes to a wallet signature
BitGo's wallet documentation describes three keys: the user key, backup key, and BitGo key. Normal transactions use the user and BitGo keys to meet a two-of-three signing requirement. The backup key can instead pair with either of the other two keys.
Related Company Fireblocks Building your digital asset business
Pairing the backup key with the user key provides a signing route that does not require BitGo's key, and the two-of-three requirement still applies in that recovery arrangement.
What changes is the pair of keys used to satisfy it: the user and backup keys replace the usual user-and-provider combination, leaving BitGo outside that signing process.
BitGo notes that limit in its withdrawal-policy documentation, saying that those policies apply only to transactions involving BitGo. Recovery transactions using the user and backup keys bypass the policies configured with the provider.
An account freeze and a wallet signature control different routes
BitGo documents a recovery route that pairs the user and backup keys without its participation.
Two of three keys must sign2of 3
- One backup key is not enough.The pairing determines whether BitGo participates.
Two of three keys must sign2of 3One backup key is not enough.Two keys must sign together.
Compare documented signing routesCompare documented signing routesNormal signingUser + backup recovery
The user and BitGo keys sign. BitGo participates, and its withdrawal policies apply.
Normal signing routeTwo selected keys connect to one on-chain transfer. The user and BitGo keys sign; BitGo withdrawal policies apply.User keyBitGo keyBackup keyNot used
On-chain transferBitGo withdrawal policies apply
Normal signing routeTwo selected keys connect to one on-chain transfer. The user and BitGo keys sign; BitGo withdrawal policies apply.UserkeyBitGokeyBackupkeyNot used
On-chain transferBitGo withdrawal policies apply
The user and backup keys sign without BitGo. Its withdrawal policies are bypassed.
User and backup recovery routeTwo selected keys connect to one on-chain transfer. BitGo does not participate and its withdrawal policies are bypassed.User keyBitGo keyBackup keyNot used
On-chain transferBitGo withdrawal policies bypassed
User and backup recovery routeTwo selected keys connect to one on-chain transfer. BitGo does not participate and its withdrawal policies are bypassed.UserkeyBitGokeyBackupkeyNot used
On-chain transferBitGo withdrawal policies bypassed
A provider's withdrawal controls do not cover every combination of keys that can sign a wallet transaction.
General BitGo documentation, not a reconstruction of Unocoin's incident. The exact keys and process used in that incident remain unestablished by this diagram.
Sources and evidence
Sources
- BitGo wallet key architecture
- BitGo withdrawal-policy scope
- BitGo documents three wallet keys: user, backup and BitGo; normal transactions use the user and BitGo keys for a two-of-three signature, while the backup key can pair with either other key. [1]
- BitGo says withdrawal policies apply only to transactions involving BitGo, and recovery transactions using the user and backup keys bypass those policies. [2]
Supporting facts
Method
Qualitative diagrams of the normal user-plus-BitGo route and the documented user-plus-backup recovery route. Connectors show signing participation, not value, timing or transaction flows.
Scope
General BitGo documentation, not a reconstruction of Unocoin's incident. The exact keys and process used in that incident remain unestablished by this diagram.
Infographic by CryptoSlate
This recovery capability preserves access when the provider is unavailable and helps explain why an account freeze cannot be treated as a blanket restriction on every transaction the wallet's keys can sign.
Unocoin reported identifying outgoing transactions on Nov. 12 from an Ethereum address within its BitGo wallet infrastructure used to fund ERC-20 tokens. Its Nov. 13 explanation attributes the disputed activity to external signing, while the suspected misuse of backup access remains under investigation.
Related Asset Ethereum ETH · $1,919.96 24-hour change: down 3.94%
In the Nov. 12 report, Unocoin said more than 90% of customer cryptocurrency funds were maintained in cold storage. It was still establishing the complete status of holdings and potential exposure, so that statement does not settle the loss assessment.
Unocoin's latest update said work to restore services continued. Unresolved questions include how the suspected recovery path was accessed, what losses or information exposure resulted, and when services can resume.