Skip to content

InvestNot yet confirmed elsewhere1 publisher3 min readPublished

Suspect in Ledger reseller breach routes $1.34 million through Tornado Cash and Binance

Onchain Lens traced 430.2 ETH, about $1.07 million, from a suspect in the Ledger CryptoBilis reseller breach into Tornado Cash, plus $270,280 into Binance. The flows are under 2% of the $70.6 million TokenPost valued in the suspect's wallets, so most of what the suspect holds has not been traced to a mixer or exchange as Ledger investigates.

The Investor · Invest desk

How we use AISend a correction

Photograph accompanying Suspect in Ledger reseller breach routes $1.34 million through Tornado Cash and Binance
Photo: decrypt.co

What happened

  • Tether froze part of the linked USDT, while other balances were converted into USDD through SUN.io and its Peg Stability Module.
  • Loss estimates run from $72 million to $86 million (tanuki42 and Specter, via The Block) up to $90 million from Binance News, and none is confirmed.
  • On October 9 Ledger asked CryptoBilis to stop distributing devices and told Southeast Asian buyers from the past three months not to use new ones.
  • Ledger told existing customers to move their assets to a new signer with a new seed phrase.

Why it matters

  • cost CryptoBilis buyers pay for the re-keying now, retiring signers and moving balances to new seeds before Ledger has said whether any device was compromised.
  • contradiction No recovery can be scored against a confirmed loss yet, since the published estimates disagree by more than the funds traced and may cover different wallets.
  • decision Custody teams sourcing hardware through resellers have to set procurement policy before Ledger's forensic answer arrives, as it has not confirmed tampering.

Of the $1.34 million traced so far [16], the smaller portion is the one still sitting where it can be frozen. The Tornado Cash leg went through four separate wallets [1]. A mixer makes deposits harder to match to withdrawals, though Cryptopolitan notes it has not closed off tracing by other routes [9]. The Binance leg, $256,567 in USDT and about $13,710 in TRX, went to an exchange hot wallet [2][3]. An exchange can freeze what it holds, and getting the money back to victims is a separate process [10]. That deposit is about 20% of the traced total [17].

Tether froze some of the linked USDT, and the frozen tokens could not be swapped [4]. The FATF said in a March 2026 report that stronger measures were needed to freeze and block suspect stablecoin transactions [11]. Cryptopolitan argues the move into USDD [5] shows how funds can be shifted outside the scope of such rules [12].

Set against what the suspect appears to hold, the outflows are small. TokenPost valued the suspect's assets at about $70.60 million in ETH, BTC, USDD and USDT, a figure Cryptopolitan cautions is not the amount lost [6]. The money sent to the mixer and the exchange is 1.9% of it [18]. The low and high published loss estimates sit $18 million apart [20], about 13 times everything traced into Tornado Cash and Binance [19]. At the $90 million figure, this one incident would equal about 9% of the $972 million TRM Labs counted stolen across 207 hacks in the first half of 2026 [15][22]. TRM also counted more than $700 million of Tornado Cash inflows through mid-June, over 20% of mixer activity [14].

Ledger has not confirmed that any device was tampered with [13]. Binance co-founder Changpeng Zhao has put forward a vendor-specific supply-chain attack, and former Mt. Gox chief executive Mark Karpeles has raised device tampering, but Cryptopolitan reports neither theory has been validated [21]. If Ledger confirms tampering at the reseller, the risk sits in the purchase channel, and every signer bought through a reseller carries a possible re-keying bill. Forensics pointing away from the hardware would make the vendor halt and the seed rotation [7][8] a precaution. The third possibility is that the estimates describe different wallets [20], so the loss shrinks and the cause stays open.

I think the channel reading is the stronger one on this record. Ledger's response targeted Southeast Asian customers of a single vendor who bought within the past three months [7], the narrow scope a channel problem would call for. The counter-case is that a manufacturer halts a vendor out of caution whatever it later finds. A Ledger finding that the CryptoBilis devices were untampered would undo the channel thesis.

What to watch

  • Ledger's investigation result on whether CryptoBilis devices were tampered with before sale.
  • Whether Binance freezes the $270,280 hot-wallet deposit and what it says about returning the funds.
  • Further movement from the wallets TokenPost valued at $70.60 million, especially new Tornado Cash deposits or USDD conversions.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence45
Adoption
Insufficient
Hype gap+10
Incentives
Insufficient
Confidence40
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    A suspected attacker tied to the Ledger CryptoBilis reseller incident sent 430.2 ETH, worth about $1.07 million, to Tornado Cash via four different wallets, per an Onchain Lens report dated October 9, 2026.

    ReportedSupportedSource: Cryptopolitan, citing Onchain LensView cited source
  2. [2]

    $270,280 was sent to Binance, made up of $256,567 in USDT and about $13,710 in TRX.

    ReportedSupportedSource: Cryptopolitan, citing Onchain LensView cited source
  3. [3]

    The funds sent to Binance were reportedly placed in a hot wallet at Binance.

    ReportedSupportedSource: Cryptopolitan, citing Onchain LensView cited source

Sources

1 independent publisher whose own reporting we read for this story.

  1. cryptopolitan.com

    1 article · October 9, 2026

    Ledger reseller hacker deposits nearly $1.3M to Tornado Cash and Binance

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

Loading related stories