Ledger said it was investigating reports of fund losses among customers who bought its hardware wallets through Southeast Asian reseller CryptoBilis. On-chain reports describe USDT freezes and transfers of other assets, but they do not establish a final loss total or prove that Ledger devices were tampered with.
7
11
What investigators reported about the funds
Bitquery reported that Tether froze about $10 million in USDT linked to the incident.
10 That is a reported blockchain-tracking estimate, not a full accounting from Tether of all affected funds or their recoverability. The available reports do not establish how much, if any, was ultimately recovered.
Onchain Lens was reported to have traced 430.2 ETH—about $1.07 million at the time—deposited into Tornado Cash through four wallets.
16 Separate reporting said about $270,300 in suspected incident-related funds reached Binance, including approximately 256,570 USDT and 41,120 TRX.
44 A reported transfer to a Binance hot wallet is not evidence that Binance identified or froze an account.
Reports also describe USDT being swapped for USDD through SUN.io and USDD’s Peg Stability Module after Tether froze related funds.
16
21 The reported sequence does not establish why the swaps occurred or whether they were intended to bypass issuer controls.
Tracked holdings are not the same as total losses
One report citing Arkham tracking put the suspected wallet cluster’s holdings at about $70.6 million: 11,406 ETH, 213.371 BTC, 13.646 million USDD and 10.909 million USDT.
21 A separate Odaily report, citing monitoring by Galaxy’s head of research, said about $72.9 million remained in attacker-controlled addresses and about $3.1 million had entered Tornado Cash; it described other funds as bridged, swapped or moved through relayers.
19
Those are reported snapshots of funds being tracked, not necessarily estimates of all victims’ losses. Published loss estimates have varied, from more than $72 million to more than $86 million, with Bitquery later reporting $92.9 million across 311 wallets on five networks.
9
10
15 The figures should not be added together: they come from different reports and may describe different address sets, assets or points in time. Ledger has not confirmed a final total.
7
11
Ledger’s response and advice to recent buyers
On October 9, Ledger said it was investigating the reports and asked CryptoBilis to pause sales and shipments.
7
11 CryptoBilis was reported to have suspended sales and shipments through its physical and online channels in Malaysia, Indonesia and the Philippines.
18
Ledger’s reported guidance applied to people who bought from the reseller within the previous 90 days: do not initialize an unused device; if it has already been set up, consider moving assets to a new signer using a new recovery seed.
7
40 The advice to use a new seed is distinct from restoring the same seed on another device.
40
The cause remains unknown
A supply-chain compromise has been discussed as one possible explanation, but the available reporting does not establish that a malicious implant was found or that Ledger’s hardware security was compromised.
4
6
11 Ledger’s investigation announcement and the reports of suspicious transactions are not, by themselves, proof of a device-level breach. The number of affected devices and the method behind the reported losses also remain unconfirmed.
4
6