BTC sidechain exploit withdraws 4,000 BTC

TLDR

Hackers drained about 4,000 BTC from the Liquid Network sidechain's federation wallet, prompting a shutdown of the bridge and fresh concern about Bitcoin sidechain risk.

1. Around 4,000 BTC, roughly 95 percent of Liquids reserve, was withdrawn from its federation wallet, while Bitcoin itself remained unaffected.
2. The incident exploited a bug in Liquids Elements software that allowed unbacked L BTC to be minted and cashed out via a normal peg out flow.
3. Self described white hats have already returned most of the BTC, but the sidechain remains paused and the L BTC peg and trust in federated bridges are under scrutiny.

Deep Dive

1. What Happened To The 4,000 BTC

Reports indicate that nearly 4,000 BTC, worth about 320 million USD, were withdrawn from the Liquid Network federation wallet that backs L BTC, forcing the sidechain to halt bridge activity and exchanges to pause L BTC deposits and withdrawals. This represented roughly 95 percent of the wallets balance, dropping reserves from about 4,200 BTC to around 200 BTC. Bitcoins base layer was not hacked; the issue was confined to Liquid, a Bitcoin sidechain operated by Blockstream that holds real BTC in a custodial multisig and issues L BTC against it.

Multiple sources describe the actors as purported white hat hackers who left an on chain message saying we are whitehats. contact us on chain and opened communications with Blockstream, as covered in a detailed incident summary on Liquids federation withdrawal.

2. How The Exploit Worked And What Was Not Compromised

Liquid and SideSwap state that the withdrawal flowed through SideSwaps Peg out Authorization Key (PAK) as a seemingly normal customer order, but that no federation keys or PAK keys were directly compromised. Instead, a bug in Elements, the software that underpins Liquid, allowed the creation of unbacked L BTC, which were then burned under a valid authorization, triggering a legitimate peg out of about 3,996 BTC to the attackers address.

In other words, the consensus and asset issuance logic accepted L BTC that should not have existed, so the federation followed the rules as coded and paid out real BTC, as explained in an analysis of the Elements based exploit path. This is an inflation or minting bug, not a stolen key event, and it highlights how wrapped BTC systems inherit the security of their bridge or sidechain code.

3. Current Status, Peg Risk And What To Watch

After bridge nodes were patched, the hackers returned about 3,400 BTC, roughly 85 percent of the stolen funds, but retained around 598.5 BTC, according to follow up coverage on returned funds and remaining shortfall. Liquid remains paused while operators work to ensure all nodes are updated and to decide how to handle the remaining gap in L BTC backing.

Key uncertainties now are whether the rest of the BTC will be returned, how any residual deficit will be socialized across L BTC holders, and whether users will treat L BTC at a discount once peg outs resume. More broadly, this incident raises questions about the safety and centralization of federated wrapped BTC models compared with trust minimized approaches or staying on Bitcoin L1.

Conclusion

A software level bug on the Liquid Network sidechain allowed nearly all of its BTC reserves to be drained through a legitimate looking peg out, even though Bitcoin itself remained secure. Most funds have been returned after emergency patches, but L BTCs peg and trust in federated Bitcoin bridges have taken a clear hit. Going forward, the main questions are how Liquid restores full backing, whether users accept its design trade offs, and how other wrapped BTC systems respond to this warning shot.