Liquid Federation Wallet Drained of 4,000 BTC via Unpatched SideSwap PAK Path

The theft occurred through the SideSwap Peg-out Authorization Key without the key itself being compromised, indicating a flaw in authorization logic or node state validation rather than key material exposure. Liquid suspended nodes and paused LBTC operations while federation members applied fixes; 598 BTC remain withheld pending confirmation that the chain split risk is resolved. Official statements emphasize no other keys were affected, yet the use of a production PAK for large-scale withdrawal reveals gaps in the multi-party computation controls that Liquid's sidechain model relies upon.

Related incidents include the 2022 Ronin bridge exploit and the 2023 Atomic Wallet drain, both tracing to similar weaknesses in federation or bridge signing logic where transaction paths bypassed intended authorization checks. Procurement records from Blockstream show repeated emphasis on enterprise-grade federation security, yet public incident reports lack detail on prior red-team findings against the PAK flow. This pattern suggests under-investment in adversarial testing of peg-out paths compared to core Bitcoin consensus code.

Operational impact extends beyond the $47 million still missing: exchanges have frozen LBTC pairs, forcing users into on-chain Bitcoin alternatives and reducing sidechain liquidity. Federation restart requires coordinated patching across members, creating a window where further state inconsistencies could be exploited. Independent node operators report the chain remains paused with no public diff for the fix.

Next steps hinge on whether Blockstream publishes the patched commit and audit trail before returning the remaining funds. Failure to do so risks renewed withdrawals or a prolonged split that fragments Liquid's pegged assets.