Blockstream Refuses Ransom for 598.5 Bitcoin (BTC) Still Held by Liquid Attackers

Blockstream Refuses Ransom Demand

Blockstream, the lead developer of the Bitcoin sidechain Liquid Network, said on September 11 that it will not pay a ransom to the attackers still holding 598.5 BTC from last week's exploit. In its official statement, the company rejected the actors' claimed white-hat status outright: “Taking assets without authorization and withholding their return is a crime, not responsible disclosure. It is not white-hat activity. It is theft.” Blockstream said it had engaged with the group in good faith to recover user funds, but stressed this should not be read as acceptance of their terms. It also declined to set a precedent in which developers of open-source software are forced to pay ransoms far exceeding their economic stake in what they maintain, noting that Bitcoin's fixed issuance means holder assets cannot simply be diluted to fund a payoff. Should the coins not be returned voluntarily, the company warned it will work with law enforcement, exchanges, service providers and forensic specialists to trace the assets and identify those responsible — adding that the transactions, and the evidence they leave behind, do not disappear.

How the 3,998.5 BTC Was Taken

The breach began on September 6, when the attackers exploited a flaw in Elements, the node software underlying Liquid, and minted roughly 4,000 L-BTC — the federated sidechain's wrapped Bitcoin asset — without matching collateral. Routing the tokens through SideSwap's peg-out infrastructure, they pulled about 3,998.5 real BTC, roughly $320 million at the time, from the federation wallet, which held approximately 4,200 BTC. That exposed about 95% of the network's reserves. On September 7 the group returned 3,400 BTC, restoring roughly 85% of the haul and leaving 598.5 BTC — about $46.3 million at $77,391 per coin — parked in an attacker-controlled address. That remainder became the centerpiece of an extortion attempt: a September 9 message embedded in Bitcoin block 966,199 via an OP_RETURN output demanded that Blockstream pay a 10% bug bounty from its own funds, or every Liquid holder would absorb a 15% loss. The message accused the company of spending as little as $1.5 million to secure $5 billion in assets and promised to release private keys decrypting prior communications. The on-chain ultimatum was shared by Jan3 CEO Samson Mow, Blockstream's former chief strategy officer.

Pegs Suspended as Recovery Proceeds

Liquid's recovery is proceeding on a controlled timeline. Blockstream shipped Elements v23.3.4 to close the exploited flaw, patched the functionary and bridge nodes, and resumed block production on Thursday — though blocks initially carried no transactions, and peg-in and peg-out conversions between BTC and L-BTC remain suspended until reserves are restored. Executive chairman Adam Back addressed the peg directly on September 10, confirming with an unambiguous yes that the 1:1 backing between L-BTC and Bitcoin will be made whole, while urging holders not to sell at a discount on over-the-counter markets. Samson Mow's subsequent recovery updates indicate transaction processing is returning to normal, with L-BTC currently only about 85% backed until the outstanding coins are recovered. The incident lands amid a bruising stretch for Bitcoin DeFi infrastructure: BTCPay Server, Coldcard and Blockstream's own Core Lightning have all disclosed vulnerabilities or thefts over the past month, and the episode has sharpened the self-custody debate across the ecosystem.

On-Chain Trail Keeps Pressure On

Our reading of the on-chain record: the 598.5 BTC had not moved as of publication, and every OP_RETURN message the actors have used to negotiate sits permanently on the public ledger — the same permanence Blockstream is betting on as tracing efforts expand across exchanges and forensic firms, as detailed in our earlier breakdown of the Liquid exploit. The company's official post-mortem identifies the Elements flaw as the root cause, with the v23.3.4 patch and restored block production already deployed as remediation; reserve restoration remains the final step. Until pegs reopen, confidence in Bitcoin sidechain security rests on the pledge that the 1:1 backing holds — funded without an attacker payout.