BTC $77,275.00 -1.52%
ETH $2,538.01 -1.65%
SOL $101.79 -1.29%
XRP $1.37 -1.74%
Coinwy
News

Blockstream Rejects Ransom Demand Over 600 BTC Liquid Exploit

According to unconfirmed reports, that wording came from Blockstream, but no original statement, named speaker, or publication date has been verified, so it

Blockstream Rejects Ransom Demand Over 600 BTC Liquid Exploit Thumbnail

Blockstream has, according to unconfirmed reports, refused a ransom demand tied to a remaining 600 BTC from a Liquid Network exploit, but the company’s only verified public communication so far is a phishing warning, and the ransom terms, recovery status, and even the exploit mechanics remain unproven in the available evidence.

Blockstream reportedly refuses the Liquid exploit ransom demand

The headline driving this story states that Blockstream refused a ransom demand connected to a Liquid Network exploit, with the phrase “Return the bitcoin” attached to the reported response. According to unconfirmed reports, that wording came from Blockstream, but no original statement, named speaker, or publication date has been verified, so it should be read as headline language rather than a confirmed quote. For related coverage, see Spot XRP ETF Performance: Is XRP Leading the Crypto Rebound?.

What Blockstream has actually published is a security notice. In a phishing alert dated September 9, 2026, the company acknowledged a recent Liquid Network incident and identified itself as Liquid’s technical provider. The alert says the incident does not require users to move funds, enter a recovery phrase, check a reimbursement, re-peg assets, or install software sent by email. For related coverage, see DKNG Launches on Solana via Sunrise, Issued by Backpack.

Blockstream also warned that impersonators are posing as Liquid, Blockstream, and support staff through emails, copied websites, and direct messages. The company stated it will never ask for a recovery phrase or PIN, or ask users to send funds anywhere. The context around Liquid’s disruption echoes an earlier report that the Liquid Network paused following a large bitcoin withdrawal. For related coverage, see Canary Lists TRXS Spot TRX ETF With Staking in the US.

What the remaining 600 BTC refers to

The headline describes 600 BTC as the amount “remaining” from the exploit. It does not identify that figure as the ransom amount, and the available evidence does not establish the original loss, any prior recoveries, asset custody, or a demand figure. The word “remaining” alone does not show how much was taken or whether any funds were returned.

No incident-linked transaction hashes, wallet addresses, or explorer entries have been identified to support the 600 BTC figure, so it should not be treated as an on-chain confirmed balance. A dollar conversion is also not warranted without a sourced transfer-time price; for reference only, Bitcoin traded around its current level well above prior cycle ranges, but that snapshot has no established link to the incident.

The affected assets, users, and exploit mechanics likewise remain unverified. The available notices acknowledge an incident without detailing how it happened or whether the Liquid protocol itself, as opposed to a related component, was compromised.

What remains unclear about recovering the bitcoin

A reported demand to return funds is not the same as evidence that funds were recovered. The headline reports a refusal but provides no confirmed subsequent recovery outcome, and no supporting statements, transaction records, or investigation updates are available to close that gap.

On the operational side, Liquid’s own notice offers the clearest verified detail: the official Liquid homepage states that issued-asset transfers have resumed, while LBTC (Liquid Bitcoin) transfers and peg-out operations remain paused. That split shows partial service restoration but does not confirm any recovery of the disputed funds.

Any claim about returned bitcoin would require direct statements and corroborating transaction evidence, and any claim about ongoing negotiations would require sourced statements; neither exists in the available material. Bitcoin infrastructure incidents have coincided with broader market swings before, as seen when Bitcoin moved on macro data ahead of a Fed decision, but no incident-specific market reaction has been verified here. For now, the ransom terms and recovery status stay open questions.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.

Read Next

From the Archive