Liquid

Galaxy

2026

Ergo

Bitcoin

<ul>
 <li><strong>Attackers claiming white-hat status drained close to 95% of the Liquid Network’s Bitcoin reserves</strong></li>
 <li><strong>The exploit abused a validation bug in Elements to mint unbacked L-BTC and peg out real Bitcoin</strong></li>
 <li><strong>No private keys were compromised, and every signature on the withdrawal was valid</strong></li>
 <li><strong>Blockstream paused the sidechain and is negotiating a return through messages written into Bitcoin blocks</strong></li>
</ul>
<p>Blockstream halted its Liquid Network on Sunday after attackers who call themselves<a href="https://x.com/Liquid_BTC/status/2096696272447218108" rel="noopener noreferrer nofollow"> white hats withdrew roughly 4,000 BTC</a>, worth about $320 million, from the federation wallet that backs the sidechain’s L-BTC token. The withdrawal cleared through SideSwap, a peg-out partner whose authorization key sits on the federation whitelist, and it emptied close to 95% of the Bitcoin held in reserve. Blockstream disabled the bridge nodes within hours and froze L-BTC deposits and withdrawals. By Monday afternoon the coins had not moved, and both sides were trading conditions for their return in messages written into Bitcoin blocks.</p>
<blockquote class="twitter-tweet">
 <p>We are aware of a security incident on <a href="https://x.com/Liquid_BTC?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">@Liquid_BTC</a>. Purported white-hat hackers have withdrawn ~4,000 BTC (~$320 million) from the Liquid Federation wallet. The <a href="https://x.com/Blockstream?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">@Blockstream</a> team is working on contacting them on-chain with a signed message.</p>
 <p>What we know so far is that the funds…</p>
 <p>— Liquid Network <img src="https://s.w.org/images/core/emoji/17.0.2/72x72/1f30a.png" alt="🌊" style="height: 1em; max-height: 1em;"> (@Liquid_BTC) <a href="https://x.com/Liquid_BTC/status/2096696272447218108?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">September 6, 2026</a></p>
</blockquote>
<h2 id="strong-the-elements-bug-let-attackers-print-l-btc-that-no-bitcoin-backed-strong"><strong>The Elements bug let attackers print L-BTC that no Bitcoin backed</strong></h2>
<p>The attackers never stole a key. They found a validation flaw in Elements, the open-source software that runs the sidechain, and used it to mint L-BTC that no Bitcoin backed. That fake L-BTC entered SideSwap’s authorized peg-out service as a routine customer order. The system did exactly what a peg-out is built to do: it burned the incoming L-BTC and released real Bitcoin from the reserve to a fresh address.</p>
<p>Block 965,783 settled the 3,996 BTC withdrawal at 14:28:56 UTC in a single 83-input transaction. The peg wallet started Sunday with about 4,200 BTC and ended with roughly 200. SideSwap says the L-BTC came from the Elements bug, not from any of its systems, and Blockstream confirms no key was compromised.</p>
<p>Bitcoin developer Adam Simecka, founder of MannaBitcoin, <a href="https://x.com/AdamSimecka/status/2096776435700543821" rel="noopener noreferrer nofollow">framed the timing as the core problem</a>, arguing that Blockstream had been patching an older Elements vulnerability in phases and disclosed where it sat before every node applied the fix. He offered no evidence for intent and called both a serious blunder and a deliberate scapegoat technically plausible. Blockstream has not confirmed how the bug was found or whether the public patching is linked to the drain, and no technical post-mortem has been published.</p>
<h2 id="strong-eleven-functionaries-signed-a-withdrawal-the-software-swore-was-clean-strong"><strong>Eleven functionaries signed a withdrawal the software swore was clean</strong></h2>
<p>Liquid’s defenses held right up until they failed. An 11-of-15 multisig guards the peg wallet, so at least eleven of fifteen vetted functionaries must sign any withdrawal, and a second lock, the Peg-out Authorization Key, is meant to stop any single compromised member from moving funds. Both layers worked. Eleven or more hardware modules signed a transaction that, from their side, was entirely valid. Nobody was tricked into approving a bad payment. The software told them the peg-out was backed, and it was not. FailSafe chief executive Aneirin Flynn described the failure as a breakdown in Liquid’s automated validation, one that let a fabricated ledger state walk past the multisig instead of defeating it.</p>
<h2 id="strong-the-attackers-set-their-terms-in-op_return-and-blockstream-answered-strong"><strong>The attackers set their terms in OP_RETURN, and Blockstream answered</strong></h2>
<p>The response played out in public, on Bitcoin itself. The attacker address posted an OP_RETURN message claiming white-hat intent and inviting contact on-chain. Blockstream replied in the same channel with a signed message pointing to its security team, a ping that Galaxy Digital’s Alex Thorn logged at block 965,822.</p>
<div style="background: #f5fafc; border: 1px solid #d5e7ee; border-radius: 10px; padding: 24px 22px; margin: 26px 0; font-family: Arial,Helvetica,sans-serif;">
 <div style="font-size: 13px; letter-spacing: .06em; text-transform: uppercase; color: #0e7c9b; font-weight: bold; margin-bottom: 20px;">
  On-chain timeline
 </div>
 <div style="border-left: 2px solid #bcd7e0; margin-left: 8px; padding-left: 22px;">
  <div style="position: relative; padding-bottom: 22px;">
   <p><span style="position: absolute; left: -32px; top: 0; width: 20px; text-align: center; color: #17a2b8; font-size: 20px; line-height: 1.2;">●</span></p>
   <div style="font-size: 13px; font-weight: bold; color: #0a1f44;">
    Sep 6, 14:06 UTC
   </div>
   <div style="font-size: 15px; color: #33424f; line-height: 1.5;">
    Peg-out request for roughly 3,996 BTC enters through SideSwap’s whitelisted authorization key.
   </div>
  </div>
  <div style="position: relative; padding-bottom: 22px;">
   <p><span style="position: absolute; left: -32px; top: 0; width: 20px; text-align: center; color: #2563eb; font-size: 20px; line-height: 1.2;">●</span></p>
   <div style="font-size: 13px; font-weight: bold; color: #0a1f44;">
    Sep 6, 14:29 UTC
   </div>
   <div style="font-size: 15px; color: #33424f; line-height: 1.5;">
    Federation functionaries sign the withdrawal in Bitcoin block 965,783.
   </div>
  </div>
  <div style="position: relative; padding-bottom: 22px;">
   <p><span style="position: absolute; left: -32px; top: 0; width: 20px; text-align: center; color: #7c3aed; font-size: 20px; line-height: 1.2;">●</span></p>
   <div style="font-size: 13px; font-weight: bold; color: #0a1f44;">
    Sep 6, afternoon
   </div>
   <div style="font-size: 15px; color: #33424f; line-height: 1.5;">
    Analyst Ergo BTC flags the drain; Liquid confirms the exploit and pauses bridge nodes.
   </div>
  </div>
  <div style="position: relative; padding-bottom: 22px;">
   <p><span style="position: absolute; left: -32px; top: 0; width: 20px; text-align: center; color: #d97706; font-size: 20px; line-height: 1.2;">●</span></p>
   <div style="font-size: 13px; font-weight: bold; color: #0a1f44;">
    Sep 6, later
   </div>
   <div style="font-size: 15px; color: #33424f; line-height: 1.5;">
    The attacker embeds an OP_RETURN message claiming white-hat status and asking for contact.
   </div>
  </div>
  <div style="position: relative; padding-bottom: 22px;">
   <p><span style="position: absolute; left: -32px; top: 0; width: 20px; text-align: center; color: #0e9f6e; font-size: 20px; line-height: 1.2;">●</span></p>
   <div style="font-size: 13px; font-weight: bold; color: #0a1f44;">
    Sep 7, block 965,822
   </div>
   <div style="font-size: 15px; color: #33424f; line-height: 1.5;">
    Blockstream pings the attacker with 1,000 satoshis and a PGP-signed message.
   </div>
  </div>
  <div style="position: relative;">
   <p><span style="position: absolute; left: -32px; top: 0; width: 20px; text-align: center; color: #dc2626; font-size: 20px; line-height: 1.2;">●</span></p>
   <div style="font-size: 13px; font-weight: bold; color: #0a1f44;">
    Sep 7, afternoon
   </div>
   <div style="font-size: 15px; color: #33424f; line-height: 1.5;">
    Funds remain stationary; the attackers condition any return on a patched, fully updated network.<span style="background-color: #ffffff; color: #222222; font-family: Verdana, BlinkMacSystemFont, -apple-system, 'Segoe UI', Roboto, Oxygen, Ubuntu, Cantarell, 'Open Sans', 'Helvetica Neue', sans-serif;">&nbsp;</span>
   </div>
  </div>
 </div>
</div>
<p>The attackers say they will return most of the funds, but only after Blockstream patches Elements and proves every node runs the fix. “Most” has no number, no deadline, and no name behind it. A return counts only when Bitcoin moves to a federation-controlled address, which had not happened at the time of writing. Blockstream keeps calling the actor a purported white hat, and holding 95% of a network’s backing hostage to force an upgrade is not how responsible disclosure usually works. Ledger CTO Charles Guillemet <a href="https://x.com/P3b7_/status/2096705787221655938" rel="noopener noreferrer nofollow">questioned the white-hat label</a>, arguing that genuine white hats do not drain a bridge and then solicit contact on-chain, though he allowed the actors could be well-intentioned people unused to responsible disclosure.</p>
<h2 id="strong-circulating-l-btc-now-trades-on-five-cents-of-backing-strong"><strong>Circulating L-BTC now trades on five cents of backing</strong></h2>
<p>The freeze stops a second withdrawal, but it also strands everyone holding L-BTC.</p>
<div style="display: flex; flex-wrap: wrap; gap: 14px; margin: 24px 0; font-family: Arial,Helvetica,sans-serif;">
 <div style="flex: 1 1 240px; background: #fffaf3; border: 1px solid #f0d9b8; border-top: 4px solid #d97706; border-radius: 8px; padding: 16px 18px;">
  <div style="display: inline-block; font-size: 11px; font-weight: bold; letter-spacing: .05em; text-transform: uppercase; color: #b45309; background: #fdecd0; border-radius: 20px; padding: 3px 10px; margin-bottom: 10px;">
   Frozen
  </div>
  <div style="font-size: 16px; font-weight: bold; color: #1f2937; margin-bottom: 6px;">
   Liquid Bitcoin (L-BTC)
  </div>
  <div style="font-size: 14px; color: #4b5563; line-height: 1.5;">
   Deposits and withdrawals suspended. Circulating L-BTC is backed by roughly five cents on the dollar until the funds return.
  </div>
 </div>
 <div style="flex: 1 1 240px; background: #fffaf3; border: 1px solid #f0d9b8; border-top: 4px solid #d97706; border-radius: 8px; padding: 16px 18px;">
  <div style="display: inline-block; font-size: 11px; font-weight: bold; letter-spacing: .05em; text-transform: uppercase; color: #b45309; background: #fdecd0; border-radius: 20px; padding: 3px 10px; margin-bottom: 10px;">
   Disrupted
  </div>
  <div style="font-size: 16px; font-weight: bold; color: #1f2937; margin-bottom: 6px;">
   Aqua wallet (JAN3)
  </div>
  <div style="font-size: 14px; color: #4b5563; line-height: 1.5;">
   The consumer wallet run by Samson Mow’s JAN3 leans on Liquid rails and is hitting functional outages.
  </div>
 </div>
 <div style="flex: 1 1 240px; background: #f2fbf5; border: 1px solid #c6ecd3; border-top: 4px solid #15803d; border-radius: 8px; padding: 16px 18px;">
  <div style="display: inline-block; font-size: 11px; font-weight: bold; letter-spacing: .05em; text-transform: uppercase; color: #15803d; background: #d7f2e0; border-radius: 20px; padding: 3px 10px; margin-bottom: 10px;">
   Unaffected
  </div>
  <div style="font-size: 16px; font-weight: bold; color: #1f2937; margin-bottom: 6px;">
   USDT, DePix, RWAs
  </div>
  <div style="font-size: 14px; color: #4b5563; line-height: 1.5;">
   Stablecoins and tokenized real-world assets issued on the sidechain keep working normally.
  </div>
 </div>
 <div style="flex: 1 1 240px; background: #f2fbf5; border: 1px solid #c6ecd3; border-top: 4px solid #15803d; border-radius: 8px; padding: 16px 18px;">
  <div style="display: inline-block; font-size: 11px; font-weight: bold; letter-spacing: .05em; text-transform: uppercase; color: #15803d; background: #d7f2e0; border-radius: 20px; padding: 3px 10px; margin-bottom: 10px;">
   Unaffected
  </div>
  <div style="font-size: 16px; font-weight: bold; color: #1f2937; margin-bottom: 6px;">
   Bitcoin base layer
  </div>
  <div style="font-size: 14px; color: #4b5563; line-height: 1.5;">
   Layer-1 nodes, keys and consensus never came into contact with the exploit.
  </div>
 </div>
</div>
<p>Had the freeze also caught the stablecoins and tokenized assets on Liquid, exchanges would have faced a far wider liquidity event. Bitcoin traded around $79,600 throughout, untouched.</p>
<h2 id="strong-analysts-blame-the-ledger-logic-not-the-fifteen-keys-strong"><strong>Analysts blame the ledger logic, not the fifteen keys</strong></h2>
<ul>
 <li><strong>Alex Thorn, Head of Research, Galaxy Digital:</strong> the case<a href="https://x.com/intangiblecoins/status/2096808321332158474" rel="noopener noreferrer nofollow"> exposes the systemic risk in wrapped and bridged Bitcoin</a>, since a software logic flaw makes the physical distribution of keys irrelevant.</li>
 <li><strong>Aneirin Flynn, CEO, FailSafe (to Bloomberg):</strong> preliminary evidence<a href="https://www.bloomberg.com/news/articles/2026-09-07/bitcoin-network-says-320-million-stolen-in-latest-crypto-hack" rel="noopener noreferrer nofollow"> points to a bug that allowed unauthorized minting of L-BTC</a>, and draining roughly 95% of reserves exposes a critical weakness in Liquid’s validation and backing model.</li>
 <li><strong>Discovery method, unconfirmed:</strong> several outlets have raised AI-assisted probing as the likely source of the bug, though Blockstream has not said how it was found.</li>
</ul>
<h2 id="strong-blockstream-s-bitvm-bridge-suddenly-looks-less-optional-strong"><strong>Blockstream’s BitVM bridge suddenly looks less optional</strong></h2>
<p>Blockstream now has to find the flaw, ship a patch, and push it to every functionary before repayment is even negotiable on the attackers’ terms. Exchanges have already cut L-BTC deposits and withdrawals, so the token stays illiquid whatever the talks produce. The heavier consequence lands on the federated model itself.</p>
<p>Blockstream had been building a BitVM 1-of-n bridge to reduce reliance on trusted custody, alongside its Simplicity language and quantum-readiness work, and a bug in the legacy Elements system now sits directly in front of that roadmap. Boltz Exchange, a Liquid partner, disabled its swap service weeks earlier and warned that AI-assisted vulnerability probing was outpacing patching. The Liquid drain follows a rough stretch for the sector, with <a href="https://ethnews.com/bitmarts-restart-plan-turns-a-shutdown-into-a-creditor-test/" rel="noopener noreferrer nofollow">BitMart still working through the fallout</a> of its own breach and Trezor disclosing a customer-data leak that now tops 80,000 people. With crypto protocols already down at least $1.3 billion to hacks through August, verifiable bridges stop reading as a long-term ambition.</p>
<p>The post <a href="https://ethnews.com/liquid-network-exploit-drains-320m-blockstream-halts-sidechain/" rel="noopener noreferrer nofollow">Liquid Network Exploit Drains $320M, Blockstream Halts Sidechain</a> appeared first on <a href="https://ethnews.com" rel="noopener noreferrer nofollow">ETHNews</a>.</p>

Liquid Network Exploit Drains $320M, Blockstream Halts Sidechain

Table of Contents

ETHNews

Other articles published on Sep 7, 2026

Join our free newsletter for daily crypto updates!