Indian crypto trading platform Unocoin says BitGo multi-signature backup mechanism may have been exploited
Indian crypto trading platform Unocoin updated on November 13, 2026, saying that it had obtained the necessary information and clarifications from custodian BitGo. BitGo has frozen its corporate account as directed by Unocoin on November 6, and the freeze currently appears to have taken effect as expected.
Unocoin said the relevant transactions were directly signed and broadcast on-chain by an external party, without going through the BitGo platform and without BitGo’s involvement. BitGo’s multi-signature wallet is designed with a backup mechanism so that funds can still be withdrawn if BitGo is unavailable; this backup mechanism appears to have been exploited. The company will continue investigating the specific mechanism, any loss of crypto assets, and information privacy issues, and will resume services after the investigation is completed.
The background is that after Unocoin discovered suspicious and unauthorized activity on November 6, it asked BitGo and Fireblocks to immediately freeze the corporate account (no crypto asset loss had been identified at the time). On November 12, Unocoin discovered an outgoing transfer from an ETH address in its BitGo wallet used to fund ERC-20 tokens, and reported it to BitGo. Because the account remained frozen and change addresses were used, the transaction situation could not be fully reconstructed at the time. Unocoin had previously also said that services had been suspended and that it was rebuilding its server infrastructure.
Original source: blog.unocoin.com/security-incident-update
ABAB AI Insight
The key issue is the disconnect between the freeze and the on-chain transfers: the BitGo corporate account freeze took effect as instructed, but transactions could still be completed through external signing and broadcasting. The subject is Unocoin’s own statement, based on clarifications obtained from BitGo, rather than an independently audited confirmation of the loss amount.
The multi-signature backup mechanism was originally meant as a recovery channel when the custodian was unavailable; this time it is suspected to have become an attack surface. A historical comparison shows that a custodian freeze only restricts operations within the platform and cannot stop an external party holding the backup key from directly broadcasting transactions; key management failures can bypass the custodial layer.
On the capital path, if the backup key was obtained, the corporate account freeze would be ineffective against actual outflows, shifting the risk from the custodian to the customer’s key storage and server environment. The short-term beneficiary is the party that successfully withdrew the assets; in the long term, the effectiveness of multi-signature custody and distributed key storage will be repriced, affecting the trust premium for exchanges and custodians.
Conclusion: this is a verified statement about the progress of the platform’s investigation, with the core point being that the freeze took effect while external-signed transfers also occurred, and the backup mechanism may have been exploited. The final loss and root cause remain to be determined after the investigation is completed; the market will accordingly reassess the practical constraints that custodian freezes impose on multi-signature backups.
ABAB News · Cognitive Law
Freeze does not mean blockage: freezing a custodian account only constrains the platform path; external keys can still broadcast directly.
Backup equals attack surface: a recovery mechanism designed for unavailable scenarios can be turned around and exploited.
Key management determines the custody boundary: custodian security does not replace customer-side key control.