The Liquid Attacker Returned Most of the Stolen Bitcoin

The strangest bitcoin heist of the year has ended the way it was negotiated: with most of the money returned. Two days after a single peg-out drained 3,998.5 bitcoin — about $320 million, roughly 95% of the reserves backing Blockstream’s Liquid sidechain — the person behind it has sent the bulk of the coins back to the federation, keeping about 598 for themselves.

That is close to $270 million returned and roughly 15% retained: an outcome that looks less like a robbery than a bug bounty the attacker set for himself.

How the door opened

The September 6 drain was not a stolen key. A flaw in Liquid’s Elements software let the peg-out — the step that releases bitcoin locked on the main chain — approve a withdrawal that created unbacked L-BTC, and the federation’s signers waved it through. Reserves fell from 4,200 bitcoin to 197.

The terms of the return

The mover left an on-chain message — “we are whitehats” — and Blockstream opened a public negotiation rather than a manhunt. The condition on the return was technical: the coins would come back once the underlying flaw was patched across the network’s nodes, so the same door could not be reopened. Blockstream deployed the patches, and the coins began flowing back.

About 598 bitcoin remain with the attacker, framed by both sides as a white-hat reward. Whether that framing holds — a bounty no one agreed to in advance is still a sum taken without permission — is a question for Liquid’s users and, potentially, for prosecutors.

What was and wasn’t at risk

Bitcoin’s main chain never moved a satoshi, and Liquid’s other assets — the dollar token USDt, the Brazilian real token DePix, and various tokenized instruments — were untouched. The damage was confined to the bitcoin held behind the federation’s multi-party wallet.

The base layer had no bad day. The bridge built on top of it did.

That is the recurring lesson of sidechains and bridges: they buy speed and features by parking coins behind a committee and a large body of code, and they inherit the risk of both. This time the code failed and the person on the other end chose to give most of it back. The next failure may not come with an olive branch.

Why it matters: a cooperative attacker turned a $320 million bug into a mostly-recovered scare — but the roughly 600 bitcoin still gone shows convenience layers keep bitcoin’s worst risks alive.

A follow-up to our September 7 report. Return amounts were still settling as of September 8, 2026 and may change. Informational only — not financial advice.