Liquid Network Exploit Drains Nearly 4,000 BTC

| btcstudy.org
The Liquid Network suffered a critical security exploit on 6 September 2026, allowing an attacker to create about 4,000 unbacked LBTC. A vulnerability in Elements’ confidential-transaction range-proof cache let an invalid transaction pass consensus checks on Liquid’s 15 functionary nodes. The attacker used SideSwap’s standard peg-out process to withdraw roughly 3,996 BTC. Further withdrawals reduced Liquid’s reserves from about 4,205 BTC to 197 BTC before bridge nodes were halted. The exploit involved an incomplete cache key and a later patch that omitted length prefixes, allowing crafted byte collisions. Blockstream deployed emergency fixes and released Elements v23.3.4. Liquid resumed controlled block production on 9 September after removing the invalid chain history, although peg operations remained suspended during recovery. The attacker returned 3,400 BTC after negotiations, leaving about 602 BTC outstanding. USDt and DePix were not directly compromised, but transfers and trading were temporarily disrupted. SideSwap’s online signing key, automated withdrawals, and lack of withdrawal limits, velocity controls and manual review exposed additional bridge and custody risks. The Liquid Network incident may continue to pressure LBTC liquidity, cross-chain settlement and market confidence.
Bearish
The incident is bearish for LBTC because it exposed a major supply-inflation vulnerability, depleted Liquid’s reserves and disrupted peg-out operations. In the short term, traders may discount LBTC because of redemption uncertainty, reduced liquidity and counterparty concerns around SideSwap and the federation. The return of 3,400 BTC, emergency patches and controlled network recovery may limit further damage, but roughly 602 BTC remains outstanding and peg operations were still restricted. Over the longer term, Elements v23.3.4 and stronger operational controls could reduce technical risk. However, confidence in LBTC’s reserve backing, bridge security and cross-chain settlement may take time to recover, keeping the risk-reward outlook negative.