Wallet Security Data Report — August 31 – September 6, 2026

Weekly Data Report · September 08, 2026 · 5 min read · The OpSecWallet Research Team
Wallet SecurityDeFiScamsHardware WalletsTRONUSDT

This is the weekly data report: what was taken, from whom, by what method, and how that compares with the weeks before it. Every figure is traced to a public disclosure or security-firm analysis, and where a number is an estimate we say so.

This edition covers August 31 – September 6, 2026. Cost and price figures are indicative reference values from public marketplaces, verified on September 8, 2026.

1. Headline Numbers

~$321.8M
Combined tracked direct losses
protocol and settlement-layer scope below
$320M
Largest incident: Liquid Network
3,996 BTC, Sept 6; 85% returned Sep 7
≈42×
Week-over-week vs Aug 24–30
vs ~$7.7M tracked the prior week
~$1.8M
Total excluding the Liquid incident
down ~77% week over week

One incident dominates everything. Roughly 3,996 BTC — about $320M at ~$80,000 per bitcoin — left the Liquid Network federation wallet on September 6, after roughly 4,000 L-BTC was sent to SideSwap's authorised peg-out service. Liquid said the Peg-out Authorization Key was not compromised and that no other keys were; the network paused new transactions and disabled public bridge nodes while federation members responded. The federation reserve fell from about 4,200 BTC to roughly 197 BTC.

Everything else was ordinary. On the protocol side we track two further confirmed drains inside the window: Notional Finance at ~$1.73M (a legacy V1 escrow contract, September 4) and Reddio's RedSonic Vault at 9.25 ETH (September 5). Combined tracked direct losses for the window: approximately $321.8M, of which the Liquid incident is about 99.5%. Excluding it, the week's tracked losses come to roughly $1.8M — about 77% below the prior week's ~$7.7M.

Key point: The single most important uncertainty in this table: the actors behind the Liquid withdrawal described themselves as white hats and said on-chain they would return the funds once the underlying bug is patched. No return had been recorded by 6:15 UTC on September 7, when this edition closed. Post-publication update (September 8): after Blockstream confirmed in a signed on-chain message that its bridge nodes were patched, the actors returned 3,400 BTC (roughly $269M, about 85%) to the federation wallet in Bitcoin block 965,950 on September 7. Roughly 598.5 BTC (about $47M) remains in their address. The September 7 return falls in the following weekly window, so the gross figure for this window stays ~$321.8M; on a running net basis, the outstanding amount from the Liquid incident is roughly $47M, and the week's net tracked total — including the other two drains — is roughly $48.8M.

2. Incident Ledger

DateTargetMethodAmountStatus
Sep 6Liquid Network (federation wallet)Peg-out via authorised service; Elements range-proof cache flaw reported~$320MNetwork paused
Sep 4Notional Finance (legacy V1 escrow)Unsafe uint128 downcast in free-collateral valuation$1.73MConfirmed
Sep 5Reddio RedSonic Vault (Ethereum)Permissionless asset registration plus flash-loan share inflation9.25 ETHConfirmed
Sep 3–6Coldcard theft proceeds (laundering)THORChain swaps and CoinJoin rounds, wave three97.09 BTC movedPrior theft
Sep 5Olas (formerly Autonolas)Malicious governance proposal disguised as treasury migration40.196 ETH at riskNot executed
Sep 1–6Hardware-wallet customersShipping-partner data exposure (Trezor / ShipMonk)80,689 recordsData only

Two rows are deliberately not counted as losses. The Coldcard movements are laundering of thefts that began on July 30, not new losses inside this window. The Olas proposal placed 40.196 ETH at risk but was not executed, and the Trezor exposure is contact data rather than funds. Counting rules are stated here so the totals can be reproduced.

3. Attack-Type Distribution

Share of the week's ~$321.8M tracked direct losses.

CategoryLossShareRepresentative case
Settlement / federation layer~$320M≈99.5%Liquid Network peg-out, Sept 6
Arithmetic overflow (legacy contract)$1.73M≈0.5%Notional Finance V1 escrow
Vault accounting / flash loan9.25 ETH<0.1%Reddio RedSonic Vault

A single category holding 99.5% of the total is unusual and worth naming: it means this week's distribution tells you almost nothing about attack trends and a great deal about concentration risk. The more informative cut is the ex-Liquid view, where the week's two confirmed protocol drains were both accounting and type-handling bugs — an unsafe integer downcast and a double-counted collateral balance — rather than stolen keys, drained approvals or compromised signers.

4. Week Over Week and Against the Baseline

WindowTracked direct lossesLargest incidentChange
Aug 31 – Sep 6~$321.8M$320M — Liquid Network≈42× the prior week
Aug 24 – 30~$7.7M$5.72M — Cosmos EVM bug−37%
Aug 17 – 23~$12.3M~$8.5M — Term Finance governance capture−67%
Aug 9 – 15>$37Mmultiple protocol incidentsspike week

The four-week sequence reads >$37M, then ~$12.3M, then ~$7.7M, then ~$321.8M — with the caveat, detailed above, that roughly $269M of the final figure was returned on September 7, leaving about $47M outstanding from the Liquid incident. The three-week decline that preceded this week is intact in the ex-Liquid series — ~$1.8M would be the fourth consecutive fall — but the headline number is dominated by a single infrastructure event whose final size depends on whether the funds are returned.

For annual context, DeFiLlama data cited this week put losses between September 2025 and September 2026 at $1.732B, with first-half 2026 theft and fraud above $1B against $2.3B in the first half of 2025.

5. What Moved, What Did Not

6. Reading the Numbers Carefully

Three cautions on this week's figures. First, the Liquid number is a gross withdrawal, not a confirmed permanent loss: roughly $269M of it was returned on September 7, leaving about $47M outstanding, so the week's realized loss sits between those two figures depending on the final outcome. Second, the Coldcard movements inside the window are laundering of an earlier theft, and counting them as new losses would double-count roughly $7.7M. Third, several user-side events this week — a dismantled drainer ring, a disrupted botnet, a batch of malicious extensions — produced confirmed mechanisms but no reliable loss totals, so they are described rather than counted.

Frequently Asked Questions

How much was lost in the week of August 31 – September 6, 2026?

Approximately $321.8M in tracked direct losses, of which about $320M comes from a single incident: the September 6 withdrawal of roughly 3,996 BTC from the Liquid Network federation wallet. The two other confirmed in-window protocol drains were Notional Finance at $1.73M and Reddio's RedSonic Vault at 9.25 ETH. Excluding Liquid, the week's tracked total is roughly $1.8M. Post-publication update: 3,400 BTC was returned on September 7 (the following window), leaving roughly 598.5 BTC — about $47M — outstanding.

Is the $320M Liquid loss permanent?

No — most of it came back. After Blockstream confirmed in a signed on-chain message that its bridge nodes were patched, the actors returned 3,400 BTC (about $269M, roughly 85%) on September 7, in Bitcoin block 965,950. Roughly 598.5 BTC (about $47M) remains in their address, with no published agreement on whether it will be returned. The September 7 return falls in the following weekly window, so this edition's gross figure stands and the net position will be reflected in next week's comparison.

Why are Coldcard fund movements not counted as a new loss?

Because the theft occurred earlier — the underlying seed-entropy flaw was exploited from July 30 — and what happened inside this window was the attacker moving already-stolen coins through THORChain and CoinJoin. Counting the 97.09 BTC moved in wave three as a fresh loss would double-count funds already attributed to earlier weeks.

What was the most common attack type this week?

By value, settlement-layer failure, entirely because of Liquid. By count and by relevance to wallet users, the recurring categories were unchanged: malicious browser extensions and fake investment platforms for user-side theft, and accounting or type-handling bugs (an unsafe integer downcast, a double-counted collateral balance) on the protocol side.

How does this week compare with the 2026 baseline?

The preceding three weeks declined sequentially from more than $37M to ~$12.3M to ~$7.7M. This week's ex-Liquid figure of roughly $1.8M would extend that decline, but the headline total is roughly 42 times the prior week because of one infrastructure event.

Sources & Methodology

This article is based on public data and official disclosures. Figures were last reviewed on September 08, 2026. Values change with network conditions; always verify against the primary source before making decisions.

  1. Liquid Network's own incident report (September 8, 2026), with The Block, Bitcoin Magazine and Decrypt: recovery of 3,400 BTC after the bridge exploit, the on-chain negotiation and the block 965,950 return.
  2. Liquid Network's own incident report, CertiK's Notional Finance analysis and ExVulSec's RedSonic Vault analysis for September 1–7, 2026.
  3. Liquid Network's own statements and Blockstream's incident status page (September 6–7, 2026): ~3,996 BTC withdrawn, reserve reduction, paused network.
  4. CertiK's and SlowMist's own analyses (September 4–5, 2026): Notional Finance $1.73M, fund routing to Tornado Cash.
  5. ExVulSec's own analysis (September 5–6, 2026): Reddio RedSonic Vault, 9.25 ETH.
  6. International Business Times (citing Galaxy Research, September 7, 2026): Coldcard wave-three movements, 97.09 BTC, vault distribution and remaining static share.
  7. DeFiLlama's tracker and Genians' report (September 5, 2026): $1.732B twelve-month losses; H1 2026 above $1B against $2.3B in H1 2025.
  8. Operator rate cards read on each provider's own site (September 8, 2026): 21–38 SUN per energy unit for 65,000-energy one-hour rentals. The on-chain Energy burn price of 100 SUN per unit is chain parameter getEnergyFee, published in TRON's own resource documentation at developers.tron.network and queryable through TRONSCAN (tronscan.org).
  9. Prior editions of this report (August 17–23 and August 24–30, 2026) for the week-over-week series.
OSW
The OpSecWallet Research Team

We are an independent research desk focused on wallet security and safe on-chain operation. Every report is written from public data and official security disclosures, cross-checked against primary sources, and reviewed for accuracy before publication. We never ask readers for keys, seeds or transfers.

Disclaimer: This content is for informational purposes only and does not constitute financial, legal or security advice. No checklist or tool eliminates risk entirely; self-custody means you are responsible for your own keys.