Skip to main content
AVOID.NET

Liquid Network / Elements Cache-Bug Exploit (September 2026)

Incident ofBlockstream Liquid Network·trust score 0/100
[AI-DRAFTED · AWAITING FACT-CHECK]

Last changed 2026-11-05 · Community evidence — A moderator accepted a piece of community-submitted evidence: Blockstream's own assessment confirms the hashing defect, ~4,000 BTC withdrawn, 3,400 BTC returned Sept 7, ~602 BTC outstanding. Trust score now 0. Version history →

[INCIDENT SEVERITY · CRITICAL]

Incidents are rated for severity, not trust. The trust score is on Blockstream Liquid Network.

Summary

On September 6, 2026, an attacker exploited a caching flaw in Elements, the open-source software underlying Blockstream's Liquid Network Bitcoin sidechain, to mint roughly 4,000 unbacked L-BTC and peg it out to native bitcoin worth approximately $319 million, draining about 95% of the federation's reserve wallet. The attacker, claiming to be a "white hat," returned about 3,400 BTC after Blockstream patched the bug but kept roughly 598.5 BTC (about $47 million) as a self-declared bounty; Blockstream publicly refused to pay a ransom for the remainder. The incident, the largest crypto theft reported in 2026 to that point, renewed scrutiny of Liquid's federated trust model, cost, and adoption levels.

Connected Entities

7 entities · 60 linked investigations
Organizations
□Liquid Network / Elements Cache-Bug Exploit (September 2026)□Blockstream Liquid Network0□Blockstream□Liquid Network0□Liquid Network Exploit (September 2026)
Protocols
Tokens
Relationships
  • Blockstream Liquid Network→mentioned with→SideSwap(70%)
  • Blockstream Liquid Network→mentioned with→Blockstream(70%)
  • Blockstream Liquid Network→mentioned with→Bitcoin(80%)
  • SideSwap→mentioned with→Blockstream(70%)
  • SideSwap→mentioned with→Bitcoin(80%)
  • Liquid Network / Elements Cache-Bug Exploit (September 2026)→mentioned with→SideSwap(70%)
  • Liquid Network / Elements Cache-Bug Exploit (September 2026)→mentioned with→Bitcoin(80%)
  • Liquid Network / Elements Cache-Bug Exploit (September 2026)→mentioned with→Blockstream(70%)
  • Liquid Network→mentioned with→Blockstream(70%)
  • Liquid Network→mentioned with→SideSwap(70%)
  • + 9 more

Connected Through

5 shared actors · 436 investigations

Distinct actors this investigation shares with others — holders, traders, and named parties. Shared infrastructure (exchanges, pools) is excluded.

Have evidence about Liquid Network / Elements Cache-Bug Exploit (September 2026)?
8
Accepted
6
Under review
1
Rejected / revoked

Community submissions

6 submissions awaiting moderator review.

Timeline(6 events)

6 September 2026

Attacker exploits a rangeproof verification caching flaw in Elements to mint roughly 4,000 unbacked L-BTC and peg it out to native bitcoin via SideSwap, draining about 95% of Liquid's federation reserve wallet (~$319 million).

TRM Labs

September 2026

Attacker returns approximately 3,400 BTC (about $270 million) to the federation wallet after Blockstream confirms affected bridge nodes have been patched; roughly 598.5 BTC remains unreturned.

The Block

September 2026

Liquid publishes an incident update describing the rangeproof caching flaw in Elements and states no federation operator keys were compromised.

The Block

September 2026

Emergency patch Elements v23.3.4 is deployed, hardening the cache-key scheme used in rangeproof verification. Separately, the attacker demands a 10% 'bug bounty' for the remaining funds via an on-chain message.

The Block

September 2026

Liquid Network resumes block production, initially without processing transactions, as functionary and bridge nodes complete required updates; peg-outs remain suspended.

CoinTelegraph

11 September 2026

Blockstream publicly refuses to pay the attacker's ransom demand for the remaining approximately 598.5 BTC, calling it theft and stating it will pursue law enforcement and forensic tracing if funds are not returned.

The Block
Provenance & Audit Trail

Decision Log

  • #13acceptRecorded on Solana ✓11/5/2026, 3:44:03 AM
    slot 465558076 · hash 4EfTecWarentsrxdukvUjTDH5ibYJXwQPJPq3SZyr4h6
  • #12acceptRecorded on Solana ✓11/5/2026, 3:44:01 AM
    slot 465558060 · hash EZe8xFsfnX35phA5Hra4LqsT6zGeNfNmoDgYNbpWCuiX
  • #11rejectRecorded on Solana ✓11/3/2026, 11:22:20 PM
    slot 465081872 · hash 8BEWdYCjKVCYp5GSWGSUyRZrv3Rjyo7Ga3QJY2dCdfUS
  • #10acceptRecorded on Solana ✓11/3/2026, 11:16:38 PM
    slot 465080236 · hash 9j2kDqSFv4sDk5MuUJThucJ9mw6mynDQdGwiwf1wLKYq
  • #9acceptRecorded on Solana ✓11/3/2026, 11:10:56 PM
    slot 465078679 · hash 29Fg8o7ZQDGJyjz1NFxjwY2KtyytWcTfBPTRy6h2uppV
  • #8accept-3Recorded on Solana ✓11/3/2026, 11:07:20 PM
    slot 465077621 · hash 6LS1QE6fHJzTg4qNGmgc4X4XnetZDa6CfRCPEhLQCu2p
  • #7accept-6Recorded on Solana ✓11/3/2026, 11:07:18 PM
    slot 465077611 · hash FVpVYmsHWf3i3x9uRTDDGjRKnMu5ziBwyXX3ed3ccfCN
  • #6accept-3Recorded on Solana ✓11/3/2026, 11:04:46 PM
    slot 465077138 · hash FUJcksc7GC7fDmTrmWntTpP3zpWuqGQZ5Egk6VFeaDMh
  • #5reviewRecorded on Solana ✓11/2/2026, 5:26:42 AM
    slot 464377212 · hash 5JntjcPtFD96rPivWzcJcNHiDK1ioS2ZbEeEDMSq21DL
  • #4review revise-5Recorded on Solana ✓11/2/2026, 12:29:11 AM
    slot 464293953 · hash DSvX6T4PW54XVYNacSKN2yjkje4tvpoNBMMEJhXqPHLz
  • #3reviewRecorded on Solana ✓11/2/2026, 12:29:11 AM
    slot 464293949 · hash 76jCEikq3mZ3fRTLSumzZyTLA2WLw4Hkj4hGXHbsacWt
  • #2accept-1Recorded on Solana ✓10/17/2026, 3:57:16 AM
    slot 457895068 · hash 6jq3v9ErukiohX9AZLCHAUQbXT49VSUc9Z9YzYiyBM2j
  • #1publishRecorded on Solana ✓9/11/2026, 5:42:00 PM
    slot 446216376 · hash 3WxgEuF5WmzZqEw79Y5ty3hxeRnMBTrQ9cB465ZeAife

This investigation is cryptographically anchored to the Solana blockchain (13 decisions). 8 of 8 cited source URLs have an Internet Archive snapshot.

Fact-checked 2026-11-0230 claims checked1 correction pending0 applied⛓ anchoredSee findings →

model: claude-code-investigator

generated: 9/11/2026, 5:41:48 PM

last updated: 11/5/2026, 3:44:03 AM

10 views

avoid.net — verified advice for a post-truth world