Blockstream refuses ransom for 598.5 BTC held by Liquid Network exploit actors

Blockstream has publicly refused to pay a ransom for the roughly 598.5 BTC that remains under the control of the actors behind the Liquid Network exploit, rejecting their framing of the incident as white-hat research and pledging to pursue the funds with law enforcement, exchanges and forensic specialists.

“We will not pay a ransom for the return of stolen funds,” the company said in a Sept. 11 post on X. “Taking assets without authorization and withholding their return is a crime, not responsible disclosure. It is not white-hat activity. It is theft.”

The statement follows days of on-chain negotiation after nearly 4,000 BTC was withdrawn from Liquid’s federation wallet on Sept. 6, and after the actors returned 3,400 BTC on Sept. 7 — roughly 85% of the withdrawn amount. The remaining coins were worth close to 47 million USD when that repayment completed.

How the negotiation broke down

The actors had initially described themselves as white hats and communicated with Blockstream through messages embedded in Bitcoin transactions. Before returning the 3,400 BTC, they told the company to fix the vulnerability and ensure every affected node had been patched — conditions Blockstream later confirmed it met through a signed message verifying that its bridge nodes had been updated.

Subsequent on-chain messages changed the terms. The actors demanded that Blockstream pay a 10% bounty from its own funds, or leave Liquid holders facing the loss. Friday’s statement is Blockstream’s formal answer: no payment of any kind tied to the return of the remaining coins.

Blockstream argued that developers of open-source Bitcoin software should not be forced to pay a ransom exceeding their economic participation in a project after someone exploits the code. “Bitcoin is hard money and can’t be minted without costs. Bitcoin doesn’t haircut users to pay a ransom,” the company said.

An expensive cache-key collision

A post-incident examination found the Sept. 6 exploit stemmed from a cache-key collision in confidential transaction verification logic. Federation keys were not compromised; the actors used the flaw to extract Bitcoin directly from the federation reserve, which represented most of the Bitcoin held in the reserve at the time.

Liquid halted block production during the incident, and exchanges were asked to suspend L-BTC deposits and withdrawals. Block production resumed after the affected bridge nodes were patched, with the Elements software updated to harden the range-proof cache keys involved in the bug.

The episode is the largest security event this year for a Bitcoin sidechain, and its resolution has become a test case for how the industry treats partial returns after exploits — a gray zone between negotiated bug bounties and outright extortion.

Precedent worries and the path forward

Blockstream said paying the demand would establish a precedent in which open-source developers could be forced to fund large payouts whenever someone drains a system built on their software — effectively converting public code into an unlimited liability for its maintainers.

The company left the door open for a voluntary return, saying those controlling the remaining Bitcoin still have an opportunity to send it back and return to standard white-hat principles. If the funds stay outstanding, Blockstream said it will work with law enforcement agencies, exchanges, service providers and forensic specialists to trace the coins and identify those responsible.

Bitcoin’s public ledger gives investigators a continuing view of movements from addresses tied to the incident, even if the coins are split across multiple wallets. “Transactions do not disappear, and neither does the evidence they leave behind,” the company said, closing with a two-word demand: “Return the bitcoin.”

A different playbook than BTCPay’s bounty

The stance contrasts with a notable precedent from August, when supporters of BTCPay Server backed a recovery bounty equal to 10% of retrieved funds — capped at 3 BTC — after an exploit exposed LND admin macaroon credentials. That bounty was funded voluntarily by the project’s community rather than demanded by the attackers as a condition of return.

Blockstream also linked the growing security pressure on open-source Bitcoin infrastructure to advances in artificial intelligence, saying teams across the ecosystem have been dedicating time to finding and fixing weaknesses in one another’s systems. The Coldcard exploit trail — where researchers attributed 1,789 BTC in losses and tracked 1,561 BTC sitting unmoved at identified addresses shared with exchanges and law enforcement — illustrates the tracing apparatus now awaiting anyone who holds stolen Bitcoin at scale.

For Liquid users, the immediate crisis has passed: 85% of the taken funds are back, the network is producing blocks, and peg-outs have resumed under tightened procedures. The fate of the final 598.5 BTC now moves from negotiation table to investigation — with Blockstream betting that time and blockchain transparency favor the pursuers, not the holder.

The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.

🌱 FOR BUSINESSES BitcoinsNews.com
Reach 100K+ Crypto Readers
Sponsored content, press releases, banner ads, and newsletter placements. Put your brand in front of Bitcoin's most engaged audience.

26 thoughts on “Blockstream refuses ransom for 598.5 BTC held by Liquid Network exploit actors”

  1. “it is not white hat activity. It is theft.” politely said but absolutely the right call. paying a ransom on 598.5 BTC just guarantees the next exploit

    1. @onchain_olaf right? imagine leaving a permanent paper trail of your extortion on a public ledger while claiming to be the good guy

        1. Silk Road comparison is a bit unfair. Ross at least did not sign his negotiation notes with the private keys holding the loot.

  2. Mireille Sabatier

    Returning 3,400 of 4,000 BTC and then keeping 598.5 as a “bounty” after promising white hat behavior. The self-incrimination through OP_RETURN is remarkable.

  3. 598.5 BTC sitting in limbo and the exploit actors still think they will get paid lmao. blockstream was never gonna reward a ~4k BTC grab

      1. even mixed coins have to exit somewhere eventually. every deposit address tied to that 598.5 is a poisoned output the second it touches a venue, blockstream just has to stay loud and patient

        1. yep, and the post-mortem said federation keys were never touched, just that cache-key collision. so the whole we did you a favor framing collapses. you found a bug, great, you still drained the reserve

          1. cache-key collision in the CT verification logic is an obscure thing to trip over. finding it takes deep federation knowledge, which makes the white hat story weirder, not better

      2. years of tracing plus a permanent on-chain confession letter. every OP_RETURN message is exhibit A for the prosecutors lol

      3. mixing only delays it though. returning 3,400 btc proved they can move size, which means exchanges already have the withdrawal fingerprints on file

  4. the 10 percent bounty demand after already returning 3400 btc is such a weird hill to die on. they had a clean white hat exit ramp and chose extortion instead

  5. returning 3,400 BTC then holding 598.5 hostage for a bounty is the worst negotiation posture ive ever seen. blockstream loses nothing by waiting, the actors lose everything the longer they hold

    1. blockstream waiting costs them nothing while that 47M gets colder by the day. the OP_RETURN negotiation trail was the real unforced error on the actors side

      1. the waiting game cuts both ways though. every day those 598.5 sit unmoved is another day forensic teams map every hop from the sept 6 withdrawal. time is on blockstreams side here, not theirs

        1. time pressure cuts both ways. 47M buys a lot of patience and chainhopping, this drags for years before anyone sees cuffs. blockstream wins the long game but days is cope

          1. chainhopping burns liquidity at every hop tho. moving 598.5 into clean fiat is the actual hard part, years is generous

  6. the strangest part is they already did the right thing. returned 3400 btc, got the patch confirmation, then invented a 10% bounty at the finish line. snatched extortion from the jaws of a clean white hat exit

  7. 85 percent returned within a day, then they haggle over 598.5 and frame it as a bounty. the sept 11 statement basically dared them to keep it and eat the consequences

    1. the bounty framing died the second blockstream quoted the exact figure. 598.5btc traceable on-chain is a confession with a timestamp, not an invoice

  8. That line about bitcoin not haircutting users to pay a ransom is the strongest part of the whole statement. Pay the 10 percent once and every federation wallet becomes a bounty board

    1. exactly this. pay the 10 percent once and every federation wallet gets a price tag on it. refusal is the only move that keeps the precedent

Leave a Comment

Your email address will not be published. Required fields are marked *

BTC$76,660.00-4.1%ETH$2,192.08-4.9%SOL$93.84-5.8%BNB$704.59-5.5%XRP$1.21-6.6%ADA$0.1870-5.0%DOGE$0.0739-5.0%DOT$0.9057-6.7%AVAX$8.18-5.2%LINK$10.51-7.7%UNI$6.53-6.8%ATOM$1.50-5.7%LTC$54.23-6.7%ARB$0.1536-6.6%NEAR$4.00-10.4%FIL$0.8006-8.6%SUI$0.8529-5.9%BTC$76,660.00-4.1%ETH$2,192.08-4.9%SOL$93.84-5.8%BNB$704.59-5.5%XRP$1.21-6.6%ADA$0.1870-5.0%DOGE$0.0739-5.0%DOT$0.9057-6.7%AVAX$8.18-5.2%LINK$10.51-7.7%UNI$6.53-6.8%ATOM$1.50-5.7%LTC$54.23-6.7%ARB$0.1536-6.6%NEAR$4.00-10.4%FIL$0.8006-8.6%SUI$0.8529-5.9%
Scroll to Top