Onchain Files
File #006 · Liquid Network exploit: 4,000 BTC from nothingMONITORINGv0.1 · findings locked · Oct 6, 2026

4,000 bitcoin from nothing. 598.5 still out.

Liquid bug→~4,000 L-BTC→Peg-out→Attacker address→3,400 back→598.5 kept

On Sep 6 an attacker used a bug in Liquid's software to create about 4,000 L-BTC that no bitcoin backed, then swapped it out of the sidechain for 3,996 real BTC in 36 minutes. The next day 3,400 BTC came back after a negotiation written into Bitcoin transactions. The rest, 598.5 BTC, sits in one address under a 10% ransom demand that Blockstream refused. Every figure below is tied to a transaction.

3,996BTCPaid out of the Liquid federation's Bitcoin reserve in one peg-out, Sep 6 14:28 UTC (≈ $318.7M reported).
36minFrom the unbacked mint on Liquid (13:53 UTC, as reported by Blockstream) to real BTC in the attacker's address.
3,400BTCSent back to the federation wallet on Sep 7, 16:09 UTC, after on-chain messages.
598.5BTCStill in one output at the attacker's address (read Oct 13). Unmoved since Sep 9. Watched every block.
MONITORING

Still held

598.5 BTC, one output

Last move

Sep 9, 11:45 UTC (ransom message)

Ransom

10% demanded, refused Sep 11

Last checked

Oct 13

The findings are locked. The status bar updates when the watched addresses move. Additions are logged below.

Current exposure

Stolen3,996 BTC
Returned3,400 BTC, Sep 7
Frozen—
Still traceable≈ $49.8M

Where it can still be stopped

  • Monitored, not freezable today · BTC held in self-custody. If it reaches an exchange or a service, that is the moment to act; we watch for it around the clock.
  • Law enforcement · a full evidence pack (every transaction, CSV) is available on request.

The claim

"we are whitehats. contact us on chain"

The attacker's address, in a Bitcoin transaction, Sep 6 18:30 UTC (c103de9581…9a19) Verified

"We will not pay for the return of stolen property."

Blockstream, Sep 11, as reported by The Block Project-reported

The evidence

  • Verified

    3,996.01834922 BTC left the federation's peg wallet in one transaction (83 inputs, block 965,783) and 3,995.99999857 BTC reached the attacker's address in the same block.

  • Verified

    3,400 BTC went back to the same federation wallet on Sep 7; the change, 598.5 BTC, stayed with the attacker.

  • Verified

    The attacker and Blockstream talked through OP_RETURN messages: 16 of them between Sep 6 and Sep 9, several encrypted.

  • Project-reported

    The unbacked L-BTC came from a bug in how Liquid's software cached proof checks (Blockstream's assessment).

The unknown

  • Unknown

    Who the attacker is.

  • Unknown

    What the encrypted messages say.

  • Unknown

    Whether the 598.5 BTC will move, and where.

01 · The window

Rehearsed in the morning, cashed out after lunch.

Sep 6, 2026, UTC. Small test peg-outs first, then the mint on Liquid and one large peg-out to Bitcoin. Four hours later the bridge was halted and the attacker posted the first message.

2026-09-06 · UTC

Hover a marker for the transaction

Chart loading…

Shaded: from the mint to the payout. Test peg-out times at 11:30 and 11:39 are Bitquery's; the rest are read from Bitcoin blocks or reported by Blockstream.

02 · Key findings

What the chain shows.

F1

Created from nothing

Project-reported

At 13:53 UTC on Sep 6, a transaction in Liquid block 4,050,336 created about 4,000 L-BTC that had no bitcoin behind it. Blockstream traces it to the cache that remembers which proofs a node has already checked: the cache key left out parts of the transaction (a 2018 bug), and the fix published on Sep 1 joined the remaining fields without length markers, so two different transactions could share one key. No private keys were taken.

Evidence: Liquid mint tx f24a4b179b…183f (Blockstream incident assessment). Read from Blockstream; our engine does not read Liquid.

F2

Out through the front door

VerifiedService named by Bitquery

The L-BTC was swapped out of Liquid through a peg-out service. At 14:28:56 UTC the federation paid 3,996.01834922 BTC from its reserve (83 inputs, 4,019.44 BTC) to an intermediate address, which forwarded 3,995.99999857 BTC to bc1ql4mfu6aundtkksxklfajs2h3t9nzcd6gyqjlte in the same block. Bitquery and Blockstream identify the service as SideSwap, which says its own keys were not compromised.

Evidence: Peg-out 8db751a650…b140, forward 85d2ca15be…5043 (block 965,783).

F3

A rehearsal first

Verified

Two days earlier the attacker moved about 1.08 and 1.07 BTC into Liquid (Sep 4, 03:11 and 16:35 UTC). On the morning of Sep 6, small test peg-outs came back; at 14:01:57 UTC three of them, 2.4975 BTC, were combined into the attacker's address. Twenty-seven minutes later came the real one.

Evidence: Peg-ins f156fc7ee2…9a52, 4aa0ce4f15…858e; tests collected afff7f39a9…443b.

F4

A negotiation written into Bitcoin

Verified

With no other channel, both sides wrote into OP_RETURN fields. 18:30 Sep 6, attacker: "we are whitehats. contact us on chain". 19:31, Blockstream: "Please contact security@blockstream.com". 02:20 Sep 7, attacker: "sending most back to bc1qdlld6…, is that ok". 03:30: "Please fix the bug first… Make sure every node is patched." Blockstream, signed: "Yes, thank you." 11:46: "Bridge nodes are patched, safe to return the funds." 12:43, attacker: "plz confirm again…". Several messages in between are PGP-encrypted. After the return, at 21:03: ":("

Evidence: Messages c103de9581…9a19, 91271efcbb…2fe8, 3a3eac4a26…80aa, 83825b2135…3c4b, 87dc0a2009…120c, 0256e33797…9016, d7e8837c51…6d52; 16 in total from the two addresses.

F5

3,400 back, 598.5 kept

VerifiedRefusal reported

At 16:09 UTC on Sep 7 the attacker sent 3,400 BTC back to the federation wallet and kept 598.49955894 BTC as change. On Sep 9 at 11:45 UTC another message demanded a 10% bug bounty "using your own money", or holders would bear a 15% loss. On Sep 11 Blockstream refused and said it would work with law enforcement and exchanges.

Evidence: Return a6d697a252…a46d; ransom message f7055f6c8d…9588 (block 966,199); refusal: The Block, Sep 11.

F6

Still there

Verified

On Oct 6 the attacker's address held 598.5044 BTC: one output of 598.50010393 BTC, created by the Sep 9 message transaction and unspent since, plus about 0.0046 BTC of dust that strangers keep sending to it. More than 1,200 dust payments, many carrying spam messages, have landed on the address since; none of them is from the attacker.

Evidence: Address bc1ql4mfu6aundtkksxklfajs2h3t9nzcd6gyqjlte; output f7055f6c8d…9588:2. Read through mempool.space, Oct 6 05:46 UTC.

03 · Money flow

Where the 3,996 BTC went.

From the federation's reserve to the attacker, and part of the way back.

BTC by route

Hover a band for amounts

Chart loading…

04 · The whole trail

Every edge shows its evidence. Click one.

A grey line is a transfer we read on-chain. A dotted box is a name taken from a public label or a project's statement. Times UTC.

LIQUID · SEP 6 BRIDGE ATTACKER NOW Unbacked mint~4,000 L-BTC Federation reservebc1qdlld…xxr Peg-out serviceSideSwap (attributed) bc1ql4mf…lte3,996 BTC in Returned3,400 BTC, Sep 7 Still held598.5 BTC

Click or tap any line in the map to see its evidence: status, transactions, time and amount.

Verified transferDirect cross-chain linkInferred linkNamed by label

05 · Evidence map

Every link, and what supports it.

LinkEvidenceStatus
Federation → peg-out service3,996.01834922 BTC, one tx, block 965,783Verified
Peg-out service → attacker3,995.99999857 BTC, same blockVerified
Attacker → federation3,400 BTC return, Sep 7Verified
Messages16 OP_RETURN messages from the attacker's and Blockstream's addressesVerified
Unbacked mintBlockstream's assessment (Liquid not read by us)Project-reported
Peg-out service is SideSwapBitquery and BlockstreamAttributed
Verified
  • 3,996 BTC left the reserve and reached the attacker in one block
  • 3,400 BTC returned; 598.5 BTC still at one address
  • Every message quoted here is in a Bitcoin transaction
Attributed
  • SideSwap as the peg-out service
Project-reported
  • The bug and the mint (Blockstream)
  • Ransom refused (Blockstream, via The Block)
Unknown
  • Who the attacker is
  • What the encrypted messages say

The attacker calls itself a white hat; Blockstream calls keeping the 598.5 BTC theft. We report what the chain shows and who said what.

06 · Timeline

In order.

Sep 4 · 03:11First peg-in to Liquid: ≈ 1.08 BTC
Sep 4 · 16:35Second peg-in: ≈ 1.07 BTC
Sep 6 · 13:53~4,000 unbacked L-BTC created on Liquid (Blockstream)
Sep 6 · 14:283,996 BTC paid out to the attacker
Sep 6 · 18:26Bridge halted
Sep 6 · 18:30"we are whitehats. contact us on chain"
Sep 7 · 01:09Emergency patch deployed (Blockstream)
Sep 7 · 16:093,400 BTC returned
Sep 9 · 11:45Ransom message: 10% "using your own money"
Sep 9 · 21:05Liquid produces blocks again (Blockstream)
Sep 11Blockstream refuses to pay
Oct 6598.5 BTC still at the attacker's address

07 · Ledger

The transactions.

Every transaction in this File, oldest first.

Transactions
UTCEventAmountTransaction
Sep 4 · 03:11:06Peg-in to Liquid≈ 1.08 BTCf156fc7ee2…9a52
Sep 4 · 16:35:59Peg-in to Liquid≈ 1.07 BTC4aa0ce4f15…858e
Sep 6 · 13:53:10Unbacked mint (Blockstream)≈ 4,000 L-BTCf24a4b179b…183f
Sep 6 · 14:01:57Test payouts collected2.4975 BTCafff7f39a9…443b
Sep 6 · 14:28:56Federation peg-out3,996.0183 BTC8db751a650…b140
Sep 6 · 14:28:56Forward to the attacker3,996.0000 BTC85d2ca15be…5043
Sep 6 · 18:30:10Message: "we are whitehats"—c103de9581…9a19
Sep 7 · 02:20:18Message: "sending most back…"—3a3eac4a26…80aa
Sep 7 · 16:09:25Return to the federation3,400 BTCa6d697a252…a46d
Sep 9 · 11:45:49Ransom message—f7055f6c8d…9588

Download every transaction behind this File (CSV): chain, time, from, to, amount, status and an explorer link for each. Check any line yourself.

08 · Method and standard

How we know.

Bitcoin transactions and the address balance read through mempool.space's API by the Onchain Files engine (Oct 6, 2026); OP_RETURN messages decoded from the attacker's and Blockstream's own transactions (inbound spam ignored). The mint, the bug and the timeline of the halt and patch are Blockstream's; the peg-out service and test peg-out times are Bitquery's. The Liquid sidechain itself was not read by our engine.

Verified

Read on-chain by us. A direct link is proven by records on both chains.

Inferred

Our deduction from patterns. The method is stated.

Attributed

Someone else's claim or label. The source is named.

Project-reported

A statement from the project involved.

Unknown

What we could not establish, listed.

Sources