Web3 Security Weekly Recovery & Enforcement Update — October 5–11, 2026

This column tracks the recovery and enforcement side of the week's incidents: funds returned, assets frozen, bounty negotiations, compensation commitments and the cost of containment. Everything here is sourced; where nothing happened, the report says so.

What was the week's most significant recovery development?

Tether's freeze on the Ledger supply-chain drain — and its limit. After hundreds of Ledger users lost an estimated $72M–$94.5M to tampered devices, Tether blacklisted more than twenty linked addresses and froze roughly $10M of USDT across the cluster, a real recovery against a large base. The attacker's answer was immediate: within a day, USDT was converted into USDD through SUN.io and USDD's peg-stability module, moving the float onto a dollar token with no issuer-level freeze primitive. PeckShield then traced roughly $3.89M into Binance deposit addresses on Tron, the first account-level lead. The week's recovery story is therefore a control that worked and was routed around inside twenty-four hours.

Recovery Ledger: A Freeze and Its Escape Hatch

The Ledger/CryptoBilis drain produced the week's only meaningful recovery, and it is instructive precisely because of where it stopped. Tether froze roughly $10M of USDT across more than twenty linked addresses — a fast, issuer-level action on a case whose losses are estimated at $72M–$94.5M, so roughly a tenth of the base figure. The attacker adapted within a day: on October 9, USDT was converted into USDD via SUN.io's exchange route and USDD's peg-stability module, moving the stablecoin portion onto a token whose issuer has no blacklist function, so a Tether freeze on the USDT contract cannot touch it. On the Ethereum side, about 430 ETH (~$1.07M) was routed through Tornado Cash across four wallets. PeckShield's tracing then produced the week's most actionable new data: roughly $3.89M — 3.685M USDT plus 615,000 TRX — sent into Binance deposit addresses on Tron over a two-day window, after roughly $10M had already moved to Binance deposit addresses earlier. Centralized exchanges can act on a deposit in a way no permissionless rail can, which is why this lead matters more than the freeze total.

Issuer Freeze Ledger

The Ledger cluster's ~$10M is the week's freeze figure, and the case is also the week's argument about how much a freeze is worth. A freeze binds one token on one set of addresses; the same haul carried bitcoin and ether, which no issuer can freeze, and only the USDT portion was ever reachable by an issuer action at all. The larger ledger this column has tracked — the Bitget case's roughly $840K in tracked freezes against a $387.5M theft — barely moved this week, with the ~$343M across 13 identified wallets still dormant. The pattern across both cases is the same and worth stating plainly: issuer freezes are the fastest recovery tool the industry has, and they recover a small, token-dependent slice of any haul, which is why programs like Bitget's 5%/5% bounty and T3's freeze pipeline run alongside them rather than instead of them.

Enforcement: A Forfeiture, a Review and a Lawsuit

A busy enforcement week, and for once it moved on three fronts. The Department of Justice filed forfeiture complaints targeting more than $1B in cryptocurrency allegedly tied to the Iranian government — approximately 127,271 BTC, plus a separate complaint for approximately 442,534 USDT (seized by the FBI on or about June 4, 2026, and citing 18 U.S.C. § 981(a)(1)(C)); the USDT complaint is dated October 9 and a notice was filed in the Eastern District of New York the following day. Alongside it, the DOJ is reviewing whether Binance complied with its November 2023 settlement, with a focus on potential Iran-sanctions violations — the review confirmed by Tysen Duva, head of the Criminal Division, to Bloomberg on October 9 — against a parallel $61M forfeiture — filed in the Southern District of New York in September, before this window — alleging Iranian oil proceeds routed through Binance accounts tied to two Hong Kong entities, Blessed Trust and Hexa Whale. And in civil court, Conduit Technology sued four Tether entities in the Southern District of New York on October 5, seeking the release of $2.76M in USDT it says Tether froze for over a year with no court order and no compliance link to Conduit, plus at least $2.76M in damages and a share of the reserve profits Tether earned on the frozen tokens. Two of these are actions against funds; the third is a direct challenge to the freeze power itself.

CaseStatusWhat is actually owed or at stake
Ledger / CryptoBilisInvestigation open; sales paused at the reseller (Oct 9)~$86M base estimate ($72M–$94.5M range); ~$10M of USDT frozen; same-day USDD pivot; ~$3.89M traced to Binance deposits
79thVault (79AU)Operator role revoked; system-upgrade notice; no incident report~$12.5M; ~14,394.92 BNB (~$11.03M) unmoved at a consolidation address; 30 BNB to KuCoin; 10% bounty posted from the operator key
Mezo (veBTC)Chain and bridge restored Oct 6; refunds pledged5.52 BTC (~$470K); all affected users to be made whole from protocol-owned sources
MakerDAO legacy keeperLoss realized; third-party bot200 ETH ($542,982); proceeds by Tornado Cash — no recovery path
Second (Ark / Bark)Fix committed Oct 7; no tagged release yet0.75 BTC (~$62K) of Second's own liquidity; no user funds; attacker linked to the Sep 19 Blink theft
Conduit v. TetherFiled SDNY Oct 5; Tether had not responded$2.76M frozen since Sep 24, 2025; plaintiff seeks release + ≥$2.76M damages + reserve profits
DOJ / Iran forfeitureComplaints filed (Oct 9–10)>$1B sought (127,271 BTC + 442,534 USDT); enforcement, not loss
Bitget (carried)Fund replenished >$300M; bounty live~$387.5M; ~$840K frozen cumulative; ~$343M dormant in 13 wallets; no recovered figure published
Base vault (carried)Still unclaimed~$31.7M still inside a contract no team will claim
Drift / Velocity (carried)DFX claims open since Oct 1$295.4M verified; ~1.04% per dollar; Tether $127.5M + partners $20M are ceilings

Refund and Compensation Tracker

Two new commitments and a familiar shape. Mezo will make every affected veBTC holder whole from protocol-owned sources — five days after the October 5 exploit, having self-halted its chain and bridge to stop the bleeding, it pledged reimbursement directly to affected wallets and warned users against any link promising recovery, which is what a clean small-incident response looks like. 79thVault has offered a 10% bounty on the ~$14,394.92 BNB still parked at a consolidation address, but the offer arrived from the same privileged address used in the drain — GoPlus called the sender's authenticity into question, so there is no confirmed counterparty to negotiate with, only a wallet to watch. Carried without new movement: Bitget's 5%/5% bounty against ~$343M dormant; Drift/Velocity's DFX claims at ~$1.04% per dollar; DYORSWAP's reimbursement of the fake GIWA scam (40% for sub-5-ETH deposits); Neutron's ~1,227,121 ATOM held for return; and the D'CENT, Meter, Duelbits and Payy cases, each still short of a published completion.

Unrecovered and Unaddressed

The week added a nine-figure unresolved problem and did not subtract from the backlog. The Ledger haul is largely unrecovered: only ~$10M of the base estimate is frozen, no issuer can touch the bitcoin or ether portions, and the attacker's USDD pivot moved a large stablecoin tranche out of the freezable zone — with tens of millions still in tagged wallets as of mid-week. 79thVault's ~$11.03M sits at a single address with no confirmed negotiation. MakerDAO's 200 ETH is gone into Tornado Cash, and Second's 0.75 BTC is de-anonymized by a Blink link but not returned. Carried: the Base vault's ~$31.7M inside an unclaimed contract; more than 63,000 ETH in Bitget-exploiter-linked wallets and the ~$1.8M Neutron attacker balance; the D'CENT operator's 1,440,291 XRP; the Liquid Network's ~598.5 BTC; and Coldcard's remaining balance. The base rate this column keeps recording held again this week: a fast, well-run response (freeze, halt, tracing) both caps a loss and leaves most of it unrecovered, because the recovery instruments — issuer freezes, CEX deposits, court orders — cover a fraction of any haul, and every actor who reads them coming adapts.

What This Means for Buyers of Security

Three implications. First, freeze planning has to model the exit, not just the entry: an attacker who can convert stolen USDT into an unfreezable dollar token within a day turns a ~$10M freeze into a partial recovery, so the value of a freeze program is now bounded by what the funds can pivot into — a fact to weigh before counting on issuer controls. Second, the supply chain is part of the security budget, and it is currently priced wrong: if a hardware wallet's guarantee is only as good as the reseller that shipped it, then buying direct and verifying the device is not paranoia but part of the product, and any custody product built on resold hardware inherits a channel risk its audits do not mention. Third, the legal levers are in play and worth watching: the DOJ's >$1B Iran forfeiture and its Binance settlement review price the cost of post-settlement compliance, while the Conduit suit against Tether is the first serious challenge to where an issuer's technical freeze power ends and its legal authority begins — the answer will set the terms for everyone treating a stablecoin as working capital.

Watch Items

  • Ledger's own count and cause: device numbers, whether the flagged other resellers show confirmed exposure, and any recovery beyond the ~$10M frozen.
  • Whether Binance acts on the ~$3.89M traced to its Tron deposit addresses, and how the DOJ's Binance settlement review resolves.
  • Whether USDD absorbs more stolen stablecoin float — and if so, whether any issuer-level freeze precedent appears on Tron's stablecoin stack.
  • The Conduit v. Tether outcome on freeze authority, and Tether's public response.
  • Mezo's refunds landing and 79thVault's white-hat negotiations over the ~14,394.92 BNB.
  • Carried: the unclaimed Base vault's ~$31.7M, Bitget's full report, and the still-dormant ~$343M.

Sources

  1. Specter, tanuki42, MistTrack and Arkham tracing on the Ledger/CryptoBilis drain; Tether freeze figures (~$10M, 20+ addresses); the USDD/SUN.io conversion (Oct 9) via Crypto Briefing, The Defiant and Wu Blockchain; Tornado Cash transfer (~430 ETH) via Onchain Lens; PeckShield on Binance deposits (~$3.89M, Oct 11).
  2. GoPlus Security analysis of the 79thVault drain (Oct 8, 14,394.92 BNB unmoved; 30 BNB to KuCoin; 10% bounty caveat); Defimon Alerts; SlowMist hacked-database entry (Oct 7).
  3. Mezo incident report (Oct 5) and blog notice (Oct 7) on the make-whole pledge; Outposts summary.
  4. CertiK MakerDAO legacy auction-keeper analysis (Oct 6); SlowMist hacked-database entry (Oct 6, $538,000).
  5. Second X thread (Oct 8) and Bark repository commit (Oct 7); Mempolitics analysis.
  6. DOJ forfeiture complaints (USDT complaint dated Oct 9, 2026; Bitcoin notice E.D.N.Y. Oct 10); CoinScoop and aggregated reporting; Treasury Secretary Bessent remarks.
  7. Conduit Technology complaint, SDNY (Oct 5, via The Block and OffshoreAlert); Crypto.news and Cryptopolitan coverage.
  8. Bloomberg via Wu Blockchain and CoinCentral on the DOJ/Binance review (Oct 9); the ~$61M CD forfeiture complaint (filed SDNY, September 2026); Trading Dashboard and CoinDesk summaries.
  9. Carried items as recorded on this site: Bitget Protection Fund and bounty notices; Drift/Velocity DFX dashboard; DYORSWAP compensation updates; Cosmos Hub forum on Neutron; Base vault alerts (Oct 4).

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

Did Tether's freeze recover the Ledger funds?

Partially. An issuer freeze immobilized roughly $10M of the USDT in the case — real money against an ~$86M base estimate, and the week's largest recovery action. It did not recover the bitcoin or ether portions, which no issuer can freeze, and the attacker moved a large stablecoin tranche into USDD within a day to escape the freezable asset entirely. So the freeze is real and the recovery is partial, and the gap between the two is the story.

Is the DOJ's >$1B Iran action a recovery?

No — it is enforcement, not recovery, and this column does not count enforcement dollars as losses or as recovered funds. The forfeiture complaints target crypto already identified or seized, alleged to be tied to Iranian sanctions evasion; they establish amounts and a statutory basis on paper rather than returning anything to victims. It is tracked here because it is the week's largest legal development, not because it changes any loss figure.

Why does the Conduit v. Tether suit matter for ordinary users?

Because it is the first serious legal test of where an issuer's power to freeze a stablecoin address ends. Tether can switch off any address it chooses; the question the case poses is whether it also has the authority to do so without a court order or a compliance link — and it is the second freeze suit in the same court in five weeks. Whatever the outcome, it sets the terms for anyone who treats a stablecoin as an operating account rather than a bearer asset.

Which of this week's losses have a recovery path?

Mezo's 5.52 BTC does — the project pledged to make users whole from protocol-owned funds. 79thVault's ~$14,394.92 BNB is traceable and a bounty is nominally on offer, but with no confirmed counterparty. The Ledger cluster has a partial path through the ~$10M already frozen and the ~$3.89M traced to Binance, bounded by the USDD pivot. MakerDAO's 200 ETH and Second's 0.75 BTC have no working recovery path; the former is in Tornado Cash, the latter de-anonymized but unreturned.

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.