API
< Back to situations

This situation has concluded

It was preserved as a record on October 11; the timeline below shows how it unfolded, with sources. Get the briefing to follow the top situations still developing: three emails a week, sourced and in order.

[SITUATION] · [QUIET] · [TECHNOLOGY]

3 clusters · 75 sources · 5 days · First seen · Last updated

Liquid Network exploit and fund recovery

Overview

The Liquid Network, a Bitcoin sidechain developed by Blockstream, suffered a major security exploit on September 6, 2026, caused by a software bug in its underlying Elements technology. A vulnerability in range proof verification caching—specifically identified by security firm SlowMist as a cache key collision—allowed for the creation of approximately 4,000 unbacked L-BTC tokens. These tokens were used to withdraw roughly 4,000 BTC (valued at approximately $320 million) from the federation wallet via the peg-out mechanism, draining approximately 95% of the Liquid Federation’s reserves.

Following the application of a security patch (Elements v23.3.4) demanded by the attackers—who identified as ‘whitehats’—3,400 BTC was returned to the Liquid Federation wallet. Blockstream confirmed that core multisignature keys were not compromised and the issue was strictly a software verification failure. Approximately 598.5 BTC, valued at roughly $46–$47 million, remains outstanding.

As of September 10, 2026, the network has resumed block production; however, it is operating in a limited capacity. Regular transactions and peg operations, including withdrawals via Peg-out Authorization Keys (PAKs), remain suspended to allow for stabilization and the restoration of the BTC/L-BTC reserve.

Negotiations have reached an impasse as Blockstream has officially rejected demands for a ransom or bug bounty. The attackers reportedly demanded a 10% bounty for the return of the remaining assets, a request Blockstream characterized as theft rather than responsible security research. Blockstream stated it will not pay for the return of stolen property and intends to pursue recovery through law enforcement, exchanges, and forensic specialists.

Entities

Blockstream · Elements · Bitcoin · SideSwap · Liquid Network

Claims

What the coverage asserts, and how many sources carry each claim.

Timeline

  1. [TECHNOLOGY] 22 sources
    Blockstream rejects ransom demand following Liquid Network Bitcoin theft

    Blockstream has rejected a ransom demand from hackers who stole 4,000 BTC from the Liquid Network. While 3,400 BTC were returned, 598.5 BTC remain outstanding following a software exploit.

  2. [TECHNOLOGY] 12 sources
    Liquid Network exploit results in theft of 4,000 Bitcoin

    Attackers exploited a software bug in the Liquid Network to drain 4,000 Bitcoin. After Blockstream patched the vulnerability, the hackers returned 3,400 BTC, leaving approximately 598 BTC outstanding.

  3. [TECHNOLOGY] 59 sources
    Liquid Network recovers 85% of $320M Bitcoin stolen in exploit

    Liquid Network recovered 85% of 4,000 BTC ($270M) stolen in a software bug exploit after negotiating with self-described white-hat hackers. Approximately 600 BTC remains outstanding.

Sources

ad-hoc-news.de · ambcrypto.com · americanbazaaronline.com · bitcoin.fr · bitcoinbasis.de · bitcoinethereumnews.com · bitcoinke.io · bitcoinmagazine.com · bitnewsbot.com · bizblog.spidersweb.pl · block-builders.de · blockchainreporter.net · blocktempo.com · brasilemfolhas.com.br · btc-echo.de · cahighways.org · cnbce.com · coinchoice.net · coincu.com · coindeskjapan.com · coindoo.com · coinedition.com · coinpedia.org · cointelegraph.com · cointrust.com · criptotendencias.com · cryps.pl · crypto-times.jp · crypto.news · cryptobreaking.com · cryptobriefing.com · cryptonews.com.au · cryptoninjas.net · cryptopolitan.com · cryptoslate.com · cybernoz.com · decrypt.co · detlionblood32.wordpress.com · dijitaliyidir.com · doviz.com · economytoday.sigmalive.com · equasis.org · fakt.pl · financiarul.ro · finanzasdigital.com · finex.cz · generation-nt.com · guiadoinvestidor.com.br

This summary has been updated 6 times: see revision history