💧 Looting of Liquid Sidechain Underscores Emerging Cyber Threat to Bitcoin

What it is

The Liquid Network exploit (Blockstream's federated Bitcoin sidechain), analyzed by Galaxy Research. The summary already covers the theft mechanism, amounts, and the extortion dynamic. What it omits: the specific SideSwap auto-forward mechanic, the negotiation timeline/content, and the comparative framing against the concurrent Coldcard incident.

How it works

Attackers exploited a sidechain node code bug to mint 4,000 L-BTC without backing, then requested a peg-out. Normally peg-out destinations must be whitelisted, but federation member SideSwap ran an auto-forward service: anyone could withdraw to SideSwap's own whitelisted address, and SideSwap would then automatically forward funds onward to whatever address the requestor specified — effectively laundering an unwhitelisted withdrawal through a whitelisted one.

Timeline / negotiation detail

• Hackers consolidated funds, tagged the transaction with an OP_RETURN note: "we are whitehats. contact us on chain."
• Blockstream and the hackers exchanged 28 messages over four days, encrypted via OP_RETURN using Blockstream's published PGP key (hacker replies encrypted to Blockstream's key; Blockstream's replies encrypted to the hackers' address, so content is one-sided/unreadable).
• Hackers returned 3,400 BTC (85%) but held 600 BTC (15%, ~$26m), then went public in plaintext on Sep 9 demanding Blockstream itself pay a 10% bug bounty (340 BTC) from its own funds, threatening to otherwise keep the 15%.
• The hacker address became a public message board, receiving more OP_RETURN posts in one day than Satoshi's Genesis Block received in ten years (legal threats, pleas, spam, memecoin ads).

flowchart LR
    A[Node bug: mint 4000 L-BTC] --> B[Request peg-out]
    B --> C{Destination whitelisted?}
    C -->|No| D[Blocked normally]
    C -->|Via SideSwap auto-forward| E[Forward to attacker's real address]
    E --> F[3400 BTC returned 85%]
    E --> G[600 BTC held hostage 15%]

Preconditions / Affected

Required SideSwap's auto-forward feature as a federation-member peg-out service — a policy/service-design gap sitting alongside Liquid's core peg-out whitelist, not a break of the whitelist itself. Galaxy notes Liquid is not systemically important to core Bitcoin, unlike the concurrent Coldcard case (separate, non-remotely-patchable hardware-wallet vulnerability, 50 BTC, funds placed in a Wyoming trust for return) and BTCPay Server, which the piece cites as a pattern of rising Bitcoin-specific infrastructure attacks previously more associated with smart-contract chains.

Caveats

Galaxy's own framing, stated directly: holding 15% hostage while negotiating a bounty is extortion, not legitimate white-hat disclosure — the proper path was responsible disclosure to Blockstream, who could have patched the node bug remotely (contrasted with Coldcard, which could not be remotely patched). Whether the hackers' hostility toward Blockstream predates the hack or arose from the negotiation itself is called "a matter of conjecture." The AI-assisted-discovery angle is explicitly speculation, not established fact.