Web3 Security Weekly Data Report — September 14–20, 2026

This report computes the week's indicators from the five loss events that occurred inside the September 14 – 20 window, using the same shared dataset as the matching news review. One of them ran for six days: the D'CENT App Wallet drain is counted at its cumulative figure as of the window's close. The SingularityNET bridge mint is counted at PeckShield's attacker-holdings figure (~$16.77M), not the face value of the tokens created. Incidents that happened earlier but had their figures or their settlement terms become public this week are reported separately as a disclosure backlog, because folding them into the weekly total would misdate the money.

How much did Web3 security incidents cost in the week of September 14–20, 2026?

Approximately $45.0M in realized losses across five in-window events — about 8.8x the prior week's ~$5.1M. Two signing-key failures led: a six-day drain of the D'CENT App Wallet that emptied 6,678 XRP Ledger wallets of 11.75M XRP (~$16.7M), and a SingularityNET bridge mint from a compromised key that left the attacker holding ~$16.8M. Next came a $7.73M Safe module exploit on Ethereum in which the proceeds went to an MEV searcher rather than to the attacker. Separately, incidents from August published ~$4.3M of first-time figures during the week, and Tether froze ~$3.62M across 16 TRON addresses (enforcement, not a loss).

The Week in Numbers

IndicatorReadingBasis
Realized losses~$45.0MFive events dated inside the window
Reported events14 items5 in-window losses, 1 freeze, 2 backlog disclosures, 2 prior-week losses with settlement news, 4 no-loss
Largest event~$16.8MSingularityNET bridge mint, Sep 20 (attacker holdings; D'CENT floor ~$16.7M)
Top-3 concentration~91%SingularityNET $16.8M + D'CENT $16.7M + Safe/rsETH $7.73M
Median event size~$7.7MMiddle value of the five-event list (Safe/rsETH)
Disclosure backlog~$4.3MPrior-period incidents first quantified this week
Enforcement (excl.)~$3.62MTether, 16 TRON addresses (Sep 14–15)

Where the Losses Sat

Failure vectorRealized lossShareEvents
Wallet key / signing compromise~$33.5M74%2 (D'CENT App Wallet XRP Ledger leg; SingularityNET bridge mint from a compromised signing key)
Module / authorization abuse~$7.73M17%1 (Safe module via custom Uniswap v4 hook)
Oracle / price manipulation~$3.85M9%2 (Nostra ~$3.5M, Flamincome ~$345.9K)

What the Numbers Say

Three observations, computed from the tables above. First, three quarters of the week ran on keys rather than broken code: 74% of the total came from wallet-side signing failures — 37% from a flaw that let an operator work through a prepared list of keys for six days (6,678 XRP Ledger wallets, 11.75M XRP, and 5,001 emptied accounts deleted afterwards to claim the reserve each one held), and another 37% from a bridge whose signing key was compromised, letting the attacker mint 260M AGIX and 53.8M WMTx it still holds. Nothing on the XRP Ledger itself was broken. Second, the pattern this site has tracked for weeks produced the rest of the damage: 17% of the week came from an authorization check that was never there — a public keeper multicall driving a Safe's custom module into attacker-controlled code, with the wallet's own signature threshold never consulted. Add the Radix vault reference and the GalaChain signature scope from the backlog table and that missing-check class accounts for about 24% of everything disclosed this week, in-window or not. It is not a novel technique; it is maintenance debt surfacing across six systems in the space of a month.

Third, the figures carry very different degrees of certainty, and two of the five are floors. D'CENT has quantified only the XRP Ledger leg — 11,746,198 XRP — a cumulative count that grew for six days and stopped at the window's close, while the company states that addresses on Bitcoin, Ethereum, TRON and EVM chains may also be exposed, so the eventual number can only move up. An independent XRPL intelligence tally, working from a narrower address set, puts the same campaign at 6,160 addresses and 9.3M XRP. Nostra's ~$3.5M is borrowed value against collateral whose entire market was under $600K, and the protocol's own reconciliation is unfinished. SingularityNET's ~$16.8M is PeckShield's attacker-holdings count from September 20 — the face value of what was minted is far higher, and the realizable value moves with the market. Anyone quoting a single precise September figure for either incident is quoting a snapshot, not a total.

Fourth, the week's most-discussed exploit did not end up with the attacker — and it is no longer the week's largest loss. The Safe exploit transaction was broadcast to the public mempool and front-run in the same block by an automated searcher, which forwarded 18.93 ETH (about $46K) to a block builder for priority; the tokens sit at a known address that the rsETH issuer paused for 24 hours. The victim's $7.73M left the wallet either way. The contrast with the two losses that now outrank it is the point: neither needed a race, an atomic transaction or a novel trick — only keys, whether an operator's prepared wallet list or a bridge's signing key.

The Disclosure Backlog

Two incidents that occurred before this window had their figures become public during it. On a combined basis they add ~$4.3M — about 9% of the ~$49.3M of losses disclosed this week, in-window or not — and they are listed separately rather than folded into the weekly total, so the week-over-week series keeps measuring when money actually left. The other two prior-period incidents in this week's news review, Chainflip and Splash, occurred inside the September 7 – 13 window and are counted in that week's total; only their settlement and patch news appears here.

IncidentOccurredLossWindow covered here
GalaChain signature replayAug 18~$3.0MPost-mortem Sep 14
Radix vault authorizationAug 31~$1.26MFoundation disclosure Sep 17
Total—~$4.3M—

Month Context

September's first calendar week (September 1–7) was independently tallied at roughly $322M, dominated by the September 6 Liquid Network event. Adding this window's ~$45.0M and the prior week's ~$5.1M puts the month near $372M on published figures — already above August's ~$255.4M across 46 incidents (DefiLlama, via Quantstamp), with ten days still to count. Even so, September's structure is unusual: strip Liquid out — $320M of that first-week tally — and the rest of the month totals roughly $52M across the other three weeks, which is a quiet month by count and a record month by dollars. For a longer anchor, a CertiK- and Forbes-cited analysis puts DeFi exploit losses above $1.3B in the first eight months of 2026.

Method Note

In-window basis: only incidents whose on-chain activity occurred between September 14 and September 20 count toward the weekly total. A multi-day campaign is counted once, at its cumulative figure as of September 20 — that is how the D'CENT drain is measured, and it is why its number differs from the single-wave totals still circulating. Prior-period incidents disclosed during the window are shown in a separate backlog table and are excluded from the weekly figure and from the week-over-week change. Enforcement freezes — the Tether batch and its continuation — are recoverable in principle and are excluded from loss sums, consistent with this site's standing convention. Category shares and concentration are computed exactly from the five-event list and rounded to the nearest point; the SingularityNET figure uses PeckShield's attacker-holdings count (~$16.77M, September 20) rather than the face value of tokens minted; D'CENT's figure covers one chain of five named as exposed, and Nostra's is borrowed value against collateral pending the protocol's own reconciliation. D'CENT's dollar figure converts its 11,746,198 XRP at ~$1.42, the September 15 rate used consistently with the matching news review; the ledger quantity, not the conversion, is the primary figure. Flamincome is counted at the ~$345,900 that Blockaid and SlowMist both put on the attacker's realised profit; DefiLlama's dataset carries ~$595,000 for the same incident on a broader basis, and that figure is not used here.

Sources

  1. Blockaid exploit detection alert and SlowMist analysis (Sep 16 Flamincome, ~$345.9K attacker profit); The Crypto Times.
  2. Blockaid exploit detection alert (Sep 15 Safe/rsETH).
  3. BlockSec, SlowMist, AstraSec and PeckShield analyses of the Safe module authorization flaw.
  4. The Crypto Times, AMBCrypto, PeckShield and CertiK on Nostra's NSTR oracle incident.
  5. PeckShieldAlert (Sep 20) on SingularityNET holdings (~$16.77M); World Mobile Chain and Fetch.ai statements; ChainCatcher.
  6. D'CENT preliminary incident report (Sep 17) and September 20 user notice; XRPL.to day-by-day drain reconstruction; U.Today; CoinGecko September 15 XRP rate (~$1.42) used for the dollar conversion.
  7. GalaChain post-mortem (Sep 14); Radix Foundation disclosure (Sep 17).
  8. Kelp DAO statement (Sep 15) on the 24-hour wallet-level rsETH pause.
  9. USDT blacklist tracker (aggregator, Sep 15); FinanceFeeds coverage of the TRON batch.
  10. DefiLlama hacks database (event-level losses); Quantstamp monthly review, August 2026.
  11. The Crypto Times, September first-week consolidated tally (month context).

This article is for general information only. It describes publicly reported security incidents; dollar figures are point-in-time estimates drawn from the sources listed above and may be revised as investigations continue. Nothing here is financial, legal or investment advice.

Frequently Asked Questions

Which numbers are estimates?

All dollar figures are point-in-time estimates from public reporting. Two are explicitly floors or placeholders: D'CENT has quantified only XRP Ledger losses (11,746,198 XRP across 6,678 wallets over six days) while stating additional exposure on four other chains, and Nostra's ~$3.5M is borrowed value against collateral the protocol is still reconciling. Blink Wallet and aelf have disclosed no figures. Event counts, category shares and concentration arithmetic are computed exactly from the five-event list.

How is top-3 concentration computed?

The three largest in-window events divided by the in-window total: ($16.8M + $16.7M + $7.73M) / $45.0M ≈ 91%.

Why is there a disclosure backlog table instead of one weekly number?

Because two incidents from earlier periods published their first hard figures only this week. Counting them in this window's total would overstate the week and understate the one they belong to; ignoring them entirely would hide real money. Keeping them in a separate, dated table preserves both the week-over-week series and the record. The other two prior-period incidents in this week's news review, Chainflip (September 12) and Splash (September 13), occurred inside the September 7 – 13 window and are counted in that week's total instead.

Does the Safe exploit count as a loss if an MEV bot took the money and the issuer froze the address?

Yes, at the point of loss. The ~2,900 rsETH left the victim wallet without authorization; whether the current holder returns it is a recovery question tracked in the recovery column, not a restatement of the loss. If the tokens come back, that entry changes — the loss does not.

Sources & Methodology

Sources

  1. Chainalysis - on-chain threat intelligence & loss data.
  2. SlowMist - security monitoring and incident advisories.
  3. CertiK & PeckShield - smart-contract incident analyses.
  4. TRONSCAN & main block explorers - on-chain verification.
  5. Project official blogs / X / GitHub - incident statements.
  6. Mainstream industry media, cross-checked against the whitelist.
  7. Figures labeled 'unconfirmed / under investigation' where the trail is not public.

This article is for general information only. It describes publicly reported security incidents; dollar figures are point-in-time estimates drawn from the sources listed above and may be revised as investigations continue. Nothing here is financial, legal or investment advice.

Strengthening your defenses? See how transaction fees and energy costs scale on Tron at Tronsell.io.