Web3 Security Weekly Data Report — September 28–October 4, 2026
This report computes the week's indicators from the four loss events that occurred inside the September 28 – October 4 window, using the same shared dataset as the matching news review. It is the smallest weekly figure this site has recorded since early September, and every share statistic on this page describes a four-event list rather than the single-event outliers of the past two weeks.
Approximately $10.2M in realized losses across four in-window events — about 2.5% of the prior week's ~$408M and the smallest weekly figure since early September. The largest is an unidentified Base vault drained of ~$6M in wstETH through its own borrowing allowlist (Oct 4); NEAR Intents lost ~$3.8M through its Omni deposit rail (Oct 1, returned in full on Oct 2); a third-party Aave v3 loop module lost ~$305K; and a Uniswap v4 hook leaked ~$115K of protocol-owned liquidity. Tracked freezes in the Bitget case reached roughly $840K (enforcement, not a loss).
- Realized losses~$10.2M~2.5% of prior week's ~$408M
- Loss events4in-window events
- Largest event~$6MUnidentified Base vault, Oct 4
- Top-2 concentration~96%of the in-window total
The Week in Numbers
| Indicator | Reading | Basis |
|---|---|---|
| Realized losses | ~$10.2M | Four events dated inside the window |
| Reported events | 11 items | 4 in-window losses, 1 completed recovery (same event), 1 compensation program launch, 1 attribution report, 1 no-loss infrastructure incident, 3 prior-case developments, 1 laundering-rails update |
| Largest event | ~$6M | Unidentified Base vault allowlist takeover, Oct 4 |
| Top-2 concentration | ~96% | Base vault $6M + NEAR Intents $3.8M |
| Median event size | ~$2.1M | Midpoint of the four-event list (between $305K and $3.8M) |
| Enforcement (excl.) | ~$840K | Tracked freezes: Circle+Tether ~$318K + NEAR Intents ~$503K, ~0.2% of the $387.5M |
Where the Losses Sat
| Failure vector | Realized loss | Share | Events |
|---|---|---|---|
| Withdrawal / bridge middleware | ~$9.8M | 96% | 2 (Base vault allowlist $6M, NEAR Intents Omni rail $3.8M) |
| Safe module / hook accounting | ~$0.42M | 4% | 2 (FlashLoopAdapter $305K, GoldPesa GPXHooks $114.9K) |
What the Numbers Say
First, the week-over-week whiplash is the data point. Roughly $10.2M against last week's ~$408M is a ~40x drop, and it is the smallest weekly figure since early September's ~$5.1M low. Two weeks ago the median was meaningless next to a $387.5M outlier; this week the mean (~$2.55M) and the median (~$2.1M) sit within half a million dollars of each other for the first time in a month — the list is close to a normal distribution of ordinary-size failures, which is the honest baseline the outlier weeks distort.
Second, the whole week sat in the glue. Every dollar lost came from a permission or middleware layer: a borrowing allowlist changed by a valid multisig signature, a Safe module's missing caller check, a hook's shared-unlock netting, a deposit/withdrawal rail's contract interaction. The core layers all held — Aave V3's Base market, Uniswap v4's contracts, the NEAR chain and Base itself functioned as designed, and each incident report says so explicitly. The monitoring story is consistent with it: two of the four events were caught in progress by real-time alerting, and one was patched within about an hour, yet none of that stopped the outflows, because the compromised component was the thing that decides which calls are legitimate.
Third, the recovery column produced its first completed return. NEAR Intents' ~$3.8M is counted here at outflow value — the money left on October 1 — while the full return on October 2 is recorded as recovery, not as a smaller loss. That convention matters this week more than usual: netting the return would show a ~$6.4M week and hide the fact that a mid-size protocol treasury can be emptied and refilled inside 36 hours. The loss series and the recovery series answer different questions, and this week both have clean readings.
Month Context
The five weeks before this one (August 24 – September 27) total roughly $551M on this site's realized basis, and about 70% of that is the single Bitget breach — so this week's ~$10.2M is best read against the pre-Bitget baseline of ~$5–45M per week, not against the Bitget week itself. Third-party anchors published this week: DefiLlama's database carried about 277 hacks for 2026 with losses near $1.84B by late September, against 148 incidents and ~$2.7B in all of 2025 — 2026 has nearly doubled last year's incident count with a quarter of the calendar left. CertiK's monthly report put September at roughly $766M (revised to ~$773M on CertiK's dashboard), and independent roundups of the month agree on its structure: Bitget and the Liquid Network breach together account for about 92% of September's gross, meaning the month's other incidents — 95 of them on CertiK's 97-incident count — averaged small — exactly the profile this week's four-event list extends.
Method Note
In-window basis: only incidents whose on-chain activity occurred between September 28 and October 4 count toward the weekly total. The Base vault is counted at ~$6M — 1,783.067 aBaswstETH borrowed and redeemed for roughly 1,783 wstETH at the ~$3,386 wstETH print; some counts place it at $6.0–6.1M depending on the price moment. NEAR Intents is counted at the ~$3.8M preliminary figure (Bitquery's reconstruction reads 3.865M USDT across five withdrawals); the full return of October 2 is tracked in the recovery column, not netted here, consistent with this site's standing treatment of recoveries. FlashLoopAdapter is counted at ~$305K per the incident registry; SlowMist's alert counts approximately 114.09 ETH, consistent at reporting-time prices — the registry dates the exploit October 1 and the SlowMist alert landed October 2. GoldPesa is counted at ~$114.9K (the attacker's net was 114,428.51 USDC per on-chain reads). Two items are excluded from the loss series on classification grounds: the fake GIWA bridge scam (~$2M, occurred September 26) — a user-facing social-engineering event that SlowMist files as fraud rather than a hack, carried as a development — and the MetaMask/ether.fi staking-infrastructure incidents, which have disclosed no fund loss. Enforcement freezes (~$840K cumulative in the Bitget case) are recoverable in principle and excluded, per convention. Category shares, concentration and the median are computed exactly from the four-event list and rounded to the nearest point.
Sources
- Blockaid, PeckShield, CertiK, GoPlus Security and ExVul alerts (Oct 4) and on-chain Safe records for the Base vault exploit (1,783.067 aBaswstETH; ~$31.7M remaining).
- NEAR Intents statements (Oct 1–2); Bitquery reconstruction (3.865M USDT, five withdrawals; $10/$11 tests on Sep 30); ZachXBT tracing; Shevchenko return confirmation (Oct 2).
- SlowMist alert (Oct 2, ~114.09 ETH) and incident registry entry (Oct 1, ~$305K) for FlashLoopAdapter.
- Defimon Alerts (Oct 3) on GoldPesa GPXHooks; The Crypto Times; DeFiHackLabs PoC; on-chain reads (net 114,428.51 USDC).
- Bitget Academy timeline and Protection Fund notices; Bloomberg via DefiLlama proof-of-reserves ($463M/24h outflows); BlockSec tracing summary (~$840K cumulative freezes).
- MetaMask user update (Oct 1); Lido governance forum; ether.fi statement; CryptoBriefing vault-flow data.
- Drift/Velocity DFX launch announcement (Oct 1); recovery dashboard (3.11M USDT pool; 299.5M DFX); CryptoSlate and The Block.
- DefiLlama 2026 running totals (277 incidents / ~$1.84B late-September snapshot) via TradingView/CryptoBriefing; CertiK monthly report ($766.4M on Sep 30; $773.4M on the dashboard, Oct 7); TRM Labs via the Financial Times (carried).
- Protos (Sep 29) on the D'CENT spread; DYORSWAP reconstruction on the fake GIWA reimbursements; THORChain and NEAR Intents statements on transfer blocking.
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. The Base vault's ~$6M moves with the wstETH price (counts range $6.0–6.1M). NEAR Intents' $3.8M is the preliminary figure against Bitquery's 3.865M on-chain reconstruction. FlashLoopAdapter's ~$305K and SlowMist's 114.09 ETH are the same event on two bases. GoldPesa's headline ~$114.9K nets to 114,428.51 USDC on-chain. None of the four figures has a project-published counter-count yet — the Base vault has no known owner to publish one.
How is the concentration computed this week?
The two largest in-window events divided by the in-window total: ($6M + $3.8M) / $10.2M ≈ 96%. Top-1 — the Base vault alone — is ~59%, a far more ordinary shape than last week's ~95% single-event concentration.
Why does the 'Where the Losses Sat' table have only two rows?
Because the four events genuinely fall into two buckets: two failures of withdrawal/bridge middleware (the Base vault allowlist and NEAR Intents' Omni rail, ~$9.8M) and two failures of add-on contract logic (a Safe module and a Uniswap v4 hook, ~$0.42M). No exchange, no governance process and no key-management failure appears in the loss list this week — the first week this site has recorded with that profile.
Is the NEAR Intents money back, and does that reduce the week?
The money is back — returned in full by October 2. It does not reduce the loss figure, because the loss series counts outflows during the window and the recovery is a separate, separately-reported fact. Reading the two series together: ~$10.2M left during the window, and ~$3.8M of it came back within 36 hours — a recovery rate no other week in this coverage has approached.
Strengthening your defenses? See how transaction fees and energy costs scale on Tron at Tronsell.io.