Cryptocurrency wallet security faces a watershed moment as Fireblocks researchers uncover BitForge — a series of critical zero-day vulnerabilities lurking inside the most widely used multi-party computation (MPC) protocols in the digital asset industry. With Bitcoin trading at $29,429 and Ethereum at $1,850, the potential impact on user funds is staggering.
The Exploit Mechanics
The BitForge vulnerabilities target three foundational MPC protocols: GG-18, GG-20, and Lindell17. These protocols are the backbone of wallet security for over 15 major digital asset wallet providers, blockchains, and open-source projects. The attacks exploit a missing zero-knowledge proof in the GG-18 and GG-20 implementations, allowing an attacker with privileged access to exfiltrate the full private key from a wallet. In some implementations, the attack completes in mere seconds, leaving no trace for the user or vendor to detect.
The GG protocol vulnerability operates at the pseudocode level, meaning every vendor implementing these protocols is potentially exposed. Attack severity varies by implementation — some require as few as 16 signatures to extract the key, while others need up to a billion. The Lindell17 flaw takes a different route: it exploits deviations from the original academic paper specification, specifically in how failed signatures are handled. An attacker targeting the party that finalizes the signing process can exfiltrate the key after approximately 200 failed signature requests.
Affected Systems
The scope of BitForge is sweeping. Over 15 wallet providers, blockchains, and open-source projects are affected, including implementations used by major cryptocurrency platforms. Notably, Coinbase WaaS and Zengo were among the first to respond, with both recognized by Fireblocks as best-in-class at managing and resolving the vulnerabilities promptly.
Fireblocks’ own MPC-CMP and MPC-CMPGG protocols are not affected, as they incorporate the required Zero Knowledge Proofs to validate all secret key material throughout the key generation, signing, and storage processes. This distinction highlights a critical lesson: the vulnerability lies not in MPC as a concept, but in flawed implementations that skip essential cryptographic safeguards.
The Mitigation Strategy
Fireblocks initiated a 90-day responsible disclosure process, documenting and verifying findings before delivering disclosure messages to impacted providers. The cryptography community responded positively, with multiple wallet providers rushing to fix their implementations. The recommended fix centers on implementing the required zero-knowledge proofs in all GG-18 and GG-20 implementations, and ensuring Lindell17 implementations adhere strictly to the academic paper specification.
Fireblocks has also established a bug bounty on HackerOne, encouraging crowdsourced testing of their MPC implementation to proactively identify future vulnerabilities. This approach of combining internal research with external expertise represents the emerging gold standard for cryptographic security.
Lessons Learned
BitForge exposes a fundamental tension in the crypto industry: the rush to implement cutting-edge cryptographic protocols often outpaces the rigor needed to ensure their security. The fact that these vulnerabilities existed in widely adopted protocols for years before detection underscores the need for continuous, independent security auditing of cryptographic implementations. The crypto market cap stands at approximately $1.18 trillion — a massive attack surface that demands equally massive security investment.
The incident also validates the importance of zero-knowledge proofs as a non-negotiable component of MPC implementations. Without these proofs, the entire security model of distributed key management collapses, leaving user funds exposed to extraction by anyone with access to the signing process.
User Action Required
If you use a wallet provider that implements MPC technology, take immediate action. Check with your provider directly about their BitForge status, or visit the Fireblocks BitForge Status Checker. If your provider has not confirmed remediation, consider migrating your funds to a wallet with verified MPC security. For institutional users, demand proof of independent cryptographic audits and zero-knowledge proof implementation from your wallet infrastructure providers.
Disclaimer: This article is for informational purposes only and does not constitute financial or security advice. Always conduct your own research before making decisions about cryptocurrency wallet security.
GG-18 and GG-20 had missing zero knowledge proofs. these are protocols securing billions. how does a ZKP implementation miss the actual ZK part
bugbounty the real question is how many implementations skipped the ZKP because it was computationally expensive and no one noticed. performance wins over security until it doesnt
Wei Chen performance over security is the entire crypto industry motto. MPC just made it to the smart contract audit tier of negligence
skipping the zero knowledge proof because it was computationally expensive is like removing seatbelts for speed. the audit process for MPC wallets is theater
16 signatures to extract a full private key in some implementations. thats not a vulnerability thats an open door
Fireblocks found it but who else was looking? if one team found missing ZK proofs, state actors probably found it years earlier
zero_witness_ Fireblocks found it but state actors probably knew for years. zero-day disclosure to crypto companies is like reporting a fire to an arsonist
Fatima 16 signatures is wild. and some vendors had it deployed in production for years without anyone catching it. the audit pipeline for MPC wallets is basically nonexistent
16 signatures to drain someones wallet and zero detection from the vendor. MPC marketing has been ahead of MPC security for years
16 signatures and zero vendor detection. the MPC space sold trustlessness while shipping code that was trivially exploitable
proof_carry_ 16 signatures to extract a key and zero detection. the MPC vendors who skipped the ZKP for performance reasons should be liable for losses
Fireblocks responsibly disclosed but you have to wonder how many attackers already knew about this before the public advisory
^ this is the real question. nation state actors dont publish research papers
15 major wallet providers affected and most users had no idea their keys were extractable. MPC marketing needs more scrutiny
fireblocks found bitforge hitting 15 plus mpc wallet providers at 29429 btc. nobody disclosed for months
lindell17 protocol also exposed with no zero knowledge proof. all three MPC standards were broken
GG-18 and GG-20 missing ZK proofs is like a bank vault with no combination lock. someone at the protocol design level decided computation cost was worth the risk
gg18 and gg20 missing zk proofs lets 16 signatures extract the key. the ZK part was the whole point
schmidt_m the worst part is 16 signatures is not a lot. active wallet users hit that in a month easily
schmidt_m removing the ZK proof because it was computationally expensive is the most crypto-brained decision ever. ship fast and hope nobody notices the gaping security hole
riya p. removing the ZK proof for computation savings while securing billions is peak crypto priorities. ship fast lose everything
Fireblocks found it and got credit. how many MPC vendors still have not patched after disclosure
tee_time_ the real scandal is how many MPC vendors patched quietly without disclosing which versions were affected. users have no idea if their wallet was vulnerable
16 signatures to extract a private key and some vendors still havent disclosed if they patched. the MPC security model needs independent audits not vendor self reporting
Henrik O. 16 signatures is like 2 weeks of normal use for an active wallet. most users would never even know they hit the threshold
the real question nobody asks is how many MPC vendors silently patched without telling their users. if you used a wallet in 2023 you might have been exposed and still dont know