Wallet Security Data Report — Week of October 5–11, 2026

Weekly Data Report · October 12, 2026 · 7 min read · The OpSecWallet Research Team
Wallet SecurityHardware WalletsDeFiScamsTRONUSDT

This weekly data report tracks publicly confirmed wallet-security incidents and their direct losses for October 5–11, 2026. Figures come from protocol disclosures, security-firm analyses and on-chain investigators; where a number is an estimate or partly frozen, we say so. Indirect costs — token price effects, lost uptime, unrecovered amounts in ongoing investigations — are not included.

This edition covers October 5–11, 2026.

1. Headline Numbers

~$4.58M
Confirmed direct losses across four quantified incidents
the largest protocol-layer item was 200 ETH from a legacy MakerDAO keeper
$72M–$94.5M
Suspected user losses tied to one reseller's Ledger devices
analyst estimates only; Ledger has confirmed a hardware implant but no loss figure
200 ETH
Largest confirmed protocol loss: the legacy MakerDAO keeper
~$542,982, drained October 6 and routed through Tornado Cash (CertiK)
~$4M
A trader's wallets swept during TOKEN2049 Singapore
nine tokens, swapped for ETH, BNB and SOL and moved through privacy tools

This week's ledger has two levels and they should not be blended. On the confirmed side — incidents with a disclosed target, method and figure — the week printed about $4.58M across four quantified items, including 200 ETH drained from a dormant 2020 MakerDAO auction-keeper contract. On the suspected side sits the largest number anyone attached to the week: $72M–$94.5M in possible user losses linked to Ledger hardware wallets bought through the reseller CryptoBilis, where Ledger has confirmed that one affected device contained an unauthorized hardware implant but has confirmed no loss total, no affected-customer count and no causal link between the implant and the drains. The two levels are why this report separates them: the confirmed loss and the suspected loss differ by a factor of roughly twenty, and a ledger that reports the second as if it were the first is not a ledger. Net of nothing recovered, the confirmed total stands at about $4.58M.

2. Incident Ledger

DateTargetMethodAmountStatus
Oct 9–10Ledger devices sold through reseller CryptoBilis (Southeast Asia)Confirmed unauthorized hardware implant in one affected device; suspected reseller supply-chain tampering (Ledger's own systems reported not compromised)$72M–$94.5M in suspected user losses (Specter, tanuki42, Bitquery, YFarmX estimates)Ledger investigation open; no figure or affected-device count confirmed; CryptoBilis halted hardware-wallet sales; Tether froze ~$10M in USDT
Oct 6Legacy MakerDAO auction keeper (Ethereum)Unauthenticated function granted Vat delegation; auctions 1457–1460 settled and 200 ETH withdrawn200 ETH (~$542,982)Funds routed through Tornado Cash in nine 10 ETH tranches; no recovery reported
Oct 7Trader 'Frogman' wallets (TOKEN2049 Singapore)Cause not disclosed; nine tokens moved and swapped for ETH, BNB and SOL~$4MRouted via Privacy Cash and Chainflip; addresses flagged
Oct 6Set Protocol (Ethereum)Rounding-error exploit~$22KNo recovery reported
Oct 7Locus Finance (Arbitrum)Contract exploit~$18KNo recovery reported
Key point: The confirmed rows this week are small and old: a five-year-dormant keeper, a rounding error, a pair of pocket-sized exploits. The large row is unconfirmed, and the thing it confirms is narrower than the headline — a single tampered device, from a single reseller, in a single region. That is the whole discipline of this ledger in one week: the number nobody has verified is not the number a holder should act on, and the number that is verified is what the defenses should be tested against.

3. Attack-Type Distribution

Share of the week's ~$4.58M in confirmed direct losses:

Failure typeAmountShareIncidents
Wallet compromise, vector undisclosed~$4M≈87%Frogman wallets during a conference
Legacy contract, unauthenticated function~$543K≈12%MakerDAO auction keeper
Contract logic error~$40K≈0.9%Set Protocol, Locus Finance

Set the suspected hardware-wallet estimates beside that table and the shape of the week doubles. The confirmed distribution is the small-scale version of the year's recurring theme — a dormant contract with a callable-without-authorization function, a wallet whose owner cannot name the entry point, two arithmetic bugs — and the estimated distribution is almost entirely one row: a supply-chain problem at a single reseller, reported at between $72M and $94.5M. Neither is a drainer wave and neither is a phishing campaign, which is worth noting in a week when a 5% bitcoin drawdown was manufacturing exactly the urgency that phishing feeds on.

4. Five-Week Comparison

WeekTracked direct lossesDefining event
Sep 7–13~$1.9M net (~$3.7M gross)Wrapper unbackings at Nomic and Symbiosis
Sep 14–20~$20.9M gross, no recoveriesApp-wallet signing flaw; Safe module drain; stolen mint keys
Sep 21–27~$412.3M grossBitget backend compromise; Neutron governance takeover
Sep 28–Oct 4~$9.6M gross, $3.865M returnedGravity Bridge signing keys; NEAR Intents full return
Oct 5–11~$4.58M confirmed, plus $72M–$94.5M estimatedLedger reseller hardware implant; MakerDAO legacy keeper

The confirmed sequence reads ~$1.9M net, ~$20.9M, ~$412.3M, ~$9.6M and now ~$4.58M — the third consecutive week of contraction on the confirmed ledger, and the first time this record has printed two consecutive weeks under $10M since August. Excluding each week's single largest confirmed incident, the baseline prints at roughly $0.6M, $13.1M, $24.8M, $4.2M and now $3.9M across the five most recent weeks, where the $3.9M is the remainder after the MakerDAO keeper is set aside. That is the second down-move in the baseline series, but the week's real headline is not in this column at all: it sits one layer out, in the $72M–$94.5M of suspected losses that no protocol disclosure backs and no issuer has confirmed — a reminder that this ledger measures what is disclosed, and disclosure is a choice.

5. Recovery Ledger

6. The Month: October Two Weeks In

Two weeks of October have printed roughly $14.2M in confirmed direct losses — about $9.6M in the first week and about $4.58M in the second — against September's roughly $759M on our gross ledger. The suspected hardware-wallet estimates sit outside that total, and the reasons are methodological rather than editorial: the figure is an analyst range rather than an issuer disclosure, the affected devices have not been counted, and the causal path from implant to drained wallet is not yet established for any individual case. What the confirmed half of October does show is a month that is, so far, cheap at the protocol layer and expensive in trust: the losses that reached the quantified file are small, and the story that dominated the week is a hardware-wallet vendor telling buyers to stop using a product they bought precisely to be safe.

7. What We Count, and What We Do Not

Counting scope is explicit: only publicly disclosed incidents with confirmed direct losses are included, and figures that are floors or estimates are labelled and held apart from the confirmed total. The Ledger-reseller estimates ($72M–$94.5M from Specter, tanuki42, Bitquery and YFarmX) are excluded from the ~$4.58M confirmed figure because no issuer has confirmed an amount, a device count or causation; Ledger's October 10 confirmation of a hardware implant is carried as a fact, and the implant is not itself counted as a loss. The MakerDAO keeper is counted at CertiK's figure of 200 ETH. Frogman is counted at EmberCN's token-by-token tally of about $4M. Set Protocol and Locus Finance are counted at their reported amounts. Recovered or frozen amounts are noted in the recovery ledger rather than netted against gross losses, so that gross and net can be read separately.

Not counted as losses: the U.S. government's movement of over $1B of forfeited bitcoin, which is custody and restitution rather than theft; ESMA's stablecoin deadline, the CFTC's commodity-classification proposal and FinCEN's withdrawn mixing rule, which are regulatory actions with no direct asset loss; and the Hong Kong Police investment-fraud statistic — more than 40 cases and losses above HK$36M in a week, including one HK$21M crypto case — which is aggregate consumer-fraud reporting rather than a single disclosed wallet-security incident. Prior-window events — Liquid, Balancer, Zentra, the rsETH front-run, the Bitget breach — are carried only for their recovery status. As always: if a figure in this report is later shown to be materially different from the initial disclosure, we will correct it in the next edition and note the change.

Frequently Asked Questions

How much was lost in the week of October 5–11, 2026?

Two answers, and the difference matters. The confirmed direct losses came to about $4.58M across four quantified incidents: about $4M from the TOKEN2049 wallet sweep, 200 ETH (~$542,982) from the legacy MakerDAO keeper, and roughly $22K and $18K from Set Protocol and Locus Finance respectively. Separately, on-chain analysts estimated $72M–$94.5M in suspected user losses tied to Ledger devices sold by one Southeast Asian reseller — but Ledger has confirmed only a hardware implant in a single affected device, and no loss figure at all. We report the first number as the week's confirmed loss and the second as an unconfirmed estimate.

Why do you separate the Ledger estimate from the confirmed total?

Because the two are not the same kind of number. The confirmed total is built from incidents where a target, a method and a figure have been disclosed by an issuer or a security firm; the Ledger range is an analyst estimate over hundreds of wallets, from a case in which the vendor has confirmed a tampering method but neither the amount nor the number of affected devices nor that tampering caused the drains. Blending them would overstate what is known by roughly a factor of twenty and would treat a suspicion as a finding. We carry the estimate, clearly labelled, and keep it out of the confirmed figure.

Is the MakerDAO keeper drain a live risk to current DeFi users?

No — it is legacy exposure, not a present threat to active protocols. The contract was a 2020-vintage auction keeper holding unsettled collateral from that year's 'Black Thursday' liquidations; the attacker needed only an unauthenticated function to take control of the keeper's position and settle the old auctions. No recent user interaction was involved. The generalizable point is that contracts do not retire when their narrative does: any protocol with historical contracts still holding value should be auditing what those contracts can still do, because an unauthenticated function is a door regardless of how long the room has been empty.

Did anything get recovered this week?

Partially, and mostly by freezing rather than clawback. Tether froze roughly $10M in USDT linked to the suspected Ledger-reseller drains — the firmest figure in that case. Bitget's Protection Fund was restored above $300M, but that is the exchange's capital covering its own loss, not recovered funds: investigators had frozen only about $1.07M, roughly 0.28% of the $387.5M taken. The MakerDAO keeper's 200 ETH was laundered through Tornado Cash within minutes; Frogman's ~$4M moved through privacy tools; and the carried items — Liquid's 598.5 BTC, the rsETH position, Balancer, Zentra — remain outstanding.

Liquid's figure changed from $52M to $49.6M. Did the recovery move?

No — the bitcoin did not move, the price did. Liquid's outstanding amount has been carried at roughly 598.5 BTC since the September window, and we re-read the dollar conversion each edition at the prevailing price, as we do for every historical crypto amount. Last edition the price was near $86,500, printing about $52M; this week it is near $82,900, printing about $49.6M. The BTC figure — the thing that actually describes the outstanding exposure — is unchanged. We convert for readability and state the rate, so the dollar line moving is expected and the coin line moving would not be.

Sources & Methodology

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

  1. Ledger's own support statements on X (October 9–10, 2026): investigation into reported losses from Southeast Asian buyers of reseller CryptoBilis, request to pause sales and shipments, guidance for buyers within 90 days, and the October 10 confirmation that one affected user's device contained an unauthorized hardware implant, with no indication that Ledger's own systems were compromised; CryptoBilis suspending all hardware-wallet sales. Loss estimates posted on X by Specter and tanuki42 and carried by The Block and CoinDesk: Specter above $86M across Ethereum, TRON and Bitcoin; tanuki42 above $72M; Bitquery about $92.9M across 311 wallets; YFarmX about $94.5M; Tether's reported ~$10M USDT freeze; individual cases including an 80 BTC address, the TRON wallet TY24Ya (~7M USDT) and a 59 ETH loss.
  2. CertiK's own incident analysis (October 6, 2026): 200 ETH (~$542,982) drained at 06:13:11 UTC from a legacy MakerDAO auction-keeper contract, four 50 ETH lots of the March 2020 'Black Thursday' liquidations settled in one transaction (auctions 1457–1460), an unauthenticated function granting Vat delegation, and Tornado Cash funding and deposits.
  3. EmberCN's own alert on X (October 7, 2026): roughly $4M drained from two wallets during TOKEN2049 Singapore across nine tokens including 1.43M BP (~$1.77M), 13.96M MarsCoin (~$1.55M) and 3.7M Cash Cat (~$510K), swapped for ETH, BNB and SOL and routed through Privacy Cash and Chainflip.
  4. DeFiLlama's hack registry (October 2026) for the Set Protocol rounding-error exploit on Ethereum (~$22K, October 6) and the Locus Finance contract exploit on Arbitrum (~$18K, October 7).
  5. Bitget's own incident progress page (last updated October 4, 2026) and its September 30, 2026 announcement: Protection Fund replenished above $300M ahead of schedule, with the CEO's October 6 statements on the fund and additional capital; Certora's estimate of post-halt outflows; and the reported ~$1.07M actually frozen (about 0.28% of $387.5M).
  6. Blockstream's own Liquid incident status page: peg-outs suspended pending reserve restoration with no announced resumption date; approximately 598.5 BTC outstanding, converted at this week's bitcoin price near $82,900; carried recovery figures for prior windows from the issuers' own notices (Kelp DAO, Balancer, Zentra).
  7. Hong Kong Police statement (October 9, 2026) carried by Sing Tao Daily: more than 40 investment-fraud reports in a week with losses above HK$36M, including one HK$21M cryptocurrency case — carried here as aggregate consumer-fraud context, not counted in the wallet-security ledger.
  8. Public market data for the week's bitcoin range (Monday high near $86,655, intraweek low near $80,400, weekend near $82,900) and Farside Investors ETF flow data referred to in the review column: $729M of two-day outflows with a $484.9M single-day outflow on October 7 and a $21.1M inflow on October 9, against the prior week's $241M inflow.
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.