Skip to main content
AVOID.NET
← Ledger9 decisions on this page

Audit log

Every state-changing event for Ledger: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-05-14 15:45:19Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 419,716,359
    sig
    3KvL42mTnURa…PadHJHe2explorer ↗
    hash
    AuimycqdZNHK…Cx8CYiyNsha256 → base58
    verifying row…full verify ↗
    canonical bytes (27531 B) ▸
    {"actor":"system:backfill","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","kind":"publish","page_slug":"ledger","published_at":"2026-05-14T15:45:18.969Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Ledger","sections":[{"content":"Ledger SAS is a French hardware security company headquartered in Paris, founded in 2014. It produces the Ledger Nano S, Nano X, and Nano S Plus hardware wallets, which are among the most widely used cold storage devices in the cryptocurrency industry. Ledger hardware wallets are designed to keep private keys isolated on a secure element chip, preventing keys from ever being exposed to internet-connected devices. As of 2023, Ledger has sold over 6 million devices globally. The company is a legitimate registered entity and is not itself accused of operating as a scam or fraud. However, a pattern of security incidents, third-party data breaches, and the downstream scam ecosystem these incidents have enabled make Ledger-related risks a significant concern for users.","heading":"Company Background","severity":"low","sources":[{"credibility":1,"name":"Ledger Security Incident Report (Official)","type":"official","url":"https://www.ledger.com/blog/security-incident-report"}]},{"content":"In June 2020, Ledger suffered a data breach affecting its e-commerce and marketing database. The breach, which involved unauthorized access facilitated in part by a Shopify employee, exposed the personal data of approximately 1.075 million customers whose email addresses were stored, and a subset of 272,853 customers whose full names, home addresses, and phone numbers were also compromised. Ledger disclosed the breach in July 2020, but the stolen data was not publicly released until December 2020, when it was dumped on hacking forums. The public dump immediately triggered waves of phishing emails, SMS smishing campaigns, extortion letters, and physical threats sent to victims' home addresses — a uniquely dangerous consequence of leaking physical location data tied to known cryptocurrency holders. In at least one documented case, a victim lost approximately $280,000 in Bitcoin and Ethereum as a result of follow-on phishing enabled by the breach. Have I Been Pwned, the widely used breach notification service, indexed the Ledger breach and confirmed its scope.","heading":"2020 E-Commerce Data Breach (272,000 Physical Addresses, 1M+ Emails)","severity":"critical","sources":[{"credibility":1,"name":"Ledger CEO Statement on Data Breach (Official)","type":"official","url":"https://www.ledger.com/message-ledgers-ceo-data-leak"},{"credibility":1,"name":"Have I Been Pwned: Ledger Breach Entry","type":"official","url":"https://haveibeenpwned.com/Breach/Ledger"},{"credibility":2,"name":"Bitdefender: Hacker publishes stolen addresses of 270,000 Ledger users","type":"news","url":"https://www.bitdefender.com/en-us/blog/hotforsecurity/hacker-publishes-stolen-email-and-mailing-addresses-of-270000-ledger-cryptocurrency-wallet-users"},{"credibility":2,"name":"Decrypt: Ledger Faces Lawsuit Over Data Breach Cover Up","type":"news","url":"https://decrypt.co/65917/ledger-lawsuit-data-breach"}]},{"content":"A class action lawsuit was filed against Ledger SAS and Shopify on April 6, 2021 in the U.S. District Court for the Northern District of California. Plaintiffs alleged that Ledger and Shopify 'negligently allowed, recklessly ignored, and then intentionally sought to cover up' the 2020 data breach. The complaint alleged Shopify employees had taken Ledger customer data as early as April 2020, and that Ledger was aware of the breach prior to its public July 2020 disclosure. One named plaintiff alleged losses of approximately $280,000 in Bitcoin and Ethereum resulting from phishing enabled by the leaked data. The lawsuit was dismissed in November 2021 by a California court on jurisdictional grounds — the court found it lacked personal jurisdiction over Ledger (a French company) and Shopify (a Canadian company). The dismissal did not constitute a ruling on the merits of the allegations.","heading":"Class Action Lawsuit (Ledger and Shopify, 2021)","severity":"high","sources":[{"credibility":1,"name":"Schneider Wallace: Ledger and Shopify Class Action Complaint","type":"court_filing","url":"https://www.schneiderwallace.com/wp-content/uploads/2021/05/Chu-et-al-v.-Ledger-SAS-SWCK-Cryptocurrency-Lawsuit.pdf"},{"credibility":1,"name":"Bloomberg Law: Ledger, Shopify Beat Data Breach Class Suit","type":"news","url":"https://news.bloomberglaw.com/privacy-and-data-security/ledger-shopify-beat-data-breach-class-suit-due-to-home-bases"},{"credibility":1,"name":"Bloomberg Law: Ledger Must Face Claims it Failed to Safeguard Consumer Data","type":"news","url":"https://news.bloomberglaw.com/litigation/ledger-must-face-claims-it-failed-to-safeguard-consumer-data"}]},{"content":"Following the December 2020 public release of the breach data, Ledger customers became targets of sustained multi-vector attacks. Attackers sent physical letters to victims' home addresses — sourced directly from the leaked dataset — instructing them to scan QR codes and enter their 24-word recovery phrases on fraudulent websites. Security researchers documented cases of tampered 'replacement' Ledger devices mailed to victims: shrink-wrapped packages with fake Ledger letterhead contained modified hardware programmed to exfiltrate seed phrases upon setup. Some victims received extortion emails referencing their home addresses and threatening physical violence if cryptocurrency was not transferred. Ledger's own phishing status page documented takedowns of over 170 phishing sites in the two months following the public data dump. Kaspersky and Malwarebytes both published advisories tracking the phishing campaign patterns targeting Ledger users specifically. The physical address leak is widely cited by security researchers as one of the most dangerous consequences of the breach, as it enables targeted physical attacks ('wrench attacks') against identified crypto holders.","heading":"Post-Breach Phishing Campaigns and Physical Threats (2021–2022)","severity":"critical","sources":[{"credibility":1,"name":"Ledger: Ongoing Phishing Campaigns (Official)","type":"official","url":"https://www.ledger.com/phishing-campaigns-status"},{"credibility":1,"name":"Ledger: Physical Mail Phishing Scam Warning","type":"official","url":"https://support.ledger.com/article/physical-mail-phishing-scam"},{"credibility":2,"name":"Kaspersky: Phishing Scheme Targeting Ledger Users","type":"news","url":"https://www.kaspersky.com/blog/ledger-vulnerability-phishing-scheme-2/54182/"},{"credibility":2,"name":"Malwarebytes: Phishers Target Ledger Crypto-Wallet Users","type":"news","url":"https://www.malwarebytes.com/blog/news/2022/04/dont-enter-your-recovery-phrase-phishers-target-ledger-crypto-wallet-users"},{"credibility":2,"name":"Rescana: Trezor and Ledger Targeted by Snail Mail Phishing Attacks","type":"news","url":"https://www.rescana.com/post/trezor-and-ledger-users-targeted-by-sophisticated-snail-mail-phishing-attacks-cryptocurrency-wallet/"}]},{"content":"On December 14, 2023, Ledger's npm-hosted JavaScript library '@ledgerhq/connect-kit' was compromised in a supply chain attack. A former Ledger employee fell victim to a phishing attack, allowing the attacker to access Ledger's npm publishing account — which lacked two-factor authentication protections. The attacker published three malicious versions of the library (1.1.5, 1.1.6, and 1.1.7), embedding Angel Drainer malware — a malware-as-a-service crypto wallet drainer. The malicious code injected a fake wallet-connection modal into any DeFi frontend that loaded the compromised library, tricking users into signing transactions that drained their wallets to attacker-controlled addresses. Affected DeFi protocols included SushiSwap, Kyber, Revoke.cash, and Zapper, among others. The malicious versions were live for approximately five hours, with active fund draining occurring over a window of less than two hours. Total confirmed losses exceeded $600,000, with some reports citing figures as high as $850,000 before Tether froze USDT held in the attacker's addresses. Ledger deployed a fix (version 1.1.8) within 40 minutes of becoming aware of the attack. The attack was attributed to the Angel Drainer group based on the drainer contract and fee collection infrastructure identified on-chain. Known attacker addresses: Main Drainer Contract: 0x000067464bdcbec51051ddcce8551e702f130000; Collector Wallet: 0x658729879fca881d9526480b82ae00efc54b5c2d; Operator Wallet: 0x00003ffA7857408ab714c28B1451914330240000; Fee Collector (angel-drainer.eth): 0x412f10AAd96fD78da6736387e2C84931Ac20313f.","heading":"Ledger Connect Kit Supply Chain Attack (December 2023)","severity":"critical","sources":[{"credibility":1,"name":"Ledger: Security Incident Report (Official)","type":"official","url":"https://www.ledger.com/blog/security-incident-report"},{"credibility":1,"name":"TechCrunch: Supply Chain Attack Targeting Ledger Leaves Users Hacked","type":"news","url":"https://techcrunch.com/2023/12/14/supply-chain-attack-targeting-ledger-crypto-wallet-leaves-users-hacked/"},{"credibility":2,"name":"The Hacker News: Ledger Supply Chain Breach Results in $600,000 Theft","type":"news","url":"https://thehackernews.com/2023/12/crypto-hardware-wallet-ledgers-supply.html"},{"credibility":1,"name":"CoinDesk: Ledger Exploit Drained $484K; Former Staffer Linked to Malicious Code","type":"news","url":"https://www.coindesk.com/business/2023/12/14/ledger-exploit-drained-484k-upended-defi-former-staffer-linked-to-malicious-code"},{"credibility":2,"name":"Blockaid: Attack Report — Ledger Connect Kit (Attacker Addresses)","type":"onchain","url":"https://www.blockaid.io/blog/attack-report-ledger-connect-kit"},{"credibility":2,"name":"SlowMist: Supply Chain Attack on Ledger Connect Kit Analysis","type":"news","url":"https://slowmist.medium.com/supply-chain-attack-on-ledger-connect-kit-analyzing-the-impact-and-preventive-measures-1005e39422fd"}]},{"content":"In May 2023, Ledger announced an optional subscription service called 'Ledger Recover' priced at $9.99 per month. The service encrypts and splits a user's 24-word seed phrase into three shards, storing them with three custodians: Ledger, Coincover, and an independent backup provider. The announcement sparked immediate and widespread criticism from the security and crypto communities. Critics argued the feature fundamentally contradicted Ledger's core security premise — that private keys never leave the device — and that enabling firmware capable of extracting and transmitting seed phrase shards created an attack surface that did not previously exist. Additional criticism focused on the KYC requirement (users must submit a government-issued ID), privacy implications, and the fact that the three custodial shards are each subject to separate legal jurisdictions, any one of which could compel disclosure via subpoena. Ledger postponed the launch in May 2023 following community backlash, then released the service for Nano X wallets in October 2023. The controversy materially damaged community trust in Ledger's security posture.","heading":"Ledger Recover Controversy (May 2023)","severity":"high","sources":[{"credibility":1,"name":"CoinDesk: Ledger Bats Back Criticism of New Wallet Recovery Service","type":"news","url":"https://www.coindesk.com/tech/2023/05/16/ledger-bats-back-criticism-of-new-wallet-recovery-service"},{"credibility":1,"name":"The Block: Ledger Defends Crypto Wallet Recovery Tool Against Hostile Reaction","type":"news","url":"https://www.theblock.co/post/230992/ledger-defends-crypto-wallet-recovery-tool"},{"credibility":1,"name":"CoinDesk: Ledger Officially Rolls Out Recover","type":"news","url":"https://www.coindesk.com/tech/2023/10/24/crypto-wallet-maker-ledger-officially-rolls-out-recover-unleashing-fresh-round-of-snark"}]},{"content":"Between April 7 and April 13, 2026, a counterfeit 'Ledger Live' application published on Apple's App Store under the entity name 'Leva Heal Limited' drained approximately $9.5 million in cryptocurrency from at least 50 confirmed victims. The app mimicked the authentic Ledger Live interface and prompted users to enter their 24-word recovery phrase to 'restore' or 'sync' their wallet — a social engineering technique that the real Ledger Live never employs. Once a recovery phrase was entered, attackers rapidly emptied associated wallets, typically within minutes. Victims lost funds across Bitcoin, Ethereum, USDT, USDC, Tron, Solana, and XRP. The three largest individual losses were $3.23 million in USDT, $2.08 million in USDC, and $1.95 million across BTC, ETH, and stETH. A notable victim was Garrett Dutton, known as musician G. Love, who lost approximately 5.92 BTC (valued at approximately $424,000) after downloading the app on a new MacBook. Blockchain investigator ZachXBT traced the stolen funds through more than 150 KuCoin deposit addresses and into a centralized mixing service identified as 'AudiA6.' ZachXBT argued the scale of the incident may provide grounds for a class action lawsuit against Apple for allowing the fraudulent app through its review process. Apple removed the application only after community reports, not through its automated review systems. Separately, fake Ledger Live apps have also appeared on Microsoft's app store in earlier incidents. Additionally, security researchers have documented counterfeit Ledger hardware devices sold via third-party marketplaces with modified chips, hidden wireless components, and firmware designed to exfiltrate seed phrases — often directing victims via QR codes to malicious companion apps.","heading":"Fake Ledger Live Apps — Apple App Store Theft of $9.5M (April 2026)","severity":"critical","sources":[{"credibility":1,"name":"CoinDesk: Fake Ledger App on Apple App Store Drained $9.5M in Crypto","type":"news","url":"https://www.coindesk.com/business/2026/04/14/a-fake-ledger-app-on-the-apple-app-store-just-drained-usd9-5-million-in-crypto"},{"credibility":1,"name":"The Block: Fake Ledger App on Apple App Store Linked to $9.5M Theft (ZachXBT)","type":"news","url":"https://www.theblock.co/post/397388/fake-ledger-app-apple-app-store-crypto-theft-bitcoin-tron-solana-zachxbt"},{"credibility":2,"name":"CoinTelegraph: Fake Ledger App on Apple Store — $9.5M Crypto Theft","type":"news","url":"https://cointelegraph.com/news/fake-ledger-app-apple-app-store-9-5m-crypto-theft-zachxbt"},{"credibility":1,"name":"The Block: G. Love Loses 5.9 BTC to Fake Ledger App","type":"news","url":"https://www.theblock.co/post/397155/g-love-loses-btc-fake-ledger"},{"credibility":2,"name":"CCN: Fake Ledger App Alert — $9.5M Stolen, Funds Laundered via KuCoin","type":"news","url":"https://www.ccn.com/education/crypto/fake-ledger-app-9-5m-stolen-50-victims-kucoin-laundering/"},{"credibility":2,"name":"Apple Insider: Bogus Crypto Wallet on App Store Steals $9.5M","type":"news","url":"https://appleinsider.com/articles/26/04/14/bogus-crypto-wallet-on-app-store-steals-95m"},{"credibility":2,"name":"CryptoTimes: ZachXBT Slams Apple After G. Love Loses $424K Bitcoin to Fake Ledger App","type":"news","url":"https://www.cryptotimes.io/2026/04/13/zachxbt-slams-apple-after-musician-loses-424k-bitcoin-to-fake-ledger-app/"},{"credibility":2,"name":"CryptoPotato: Fake Ledger Wallet Exposed With Hidden Chip Stealing Seed Phrases","type":"news","url":"https://cryptopotato.com/fake-ledger-wallet-exposed-with-hidden-chip-stealing-seed-phrases-and-pins/"}]},{"content":"In January 2026, Ledger disclosed a second major data breach, this time originating from its third-party payments processor Global-e. The breach involved unauthorized access to Global-e's cloud systems, which held order data for multiple brands including Ledger. Exposed information included customer names and contact details. Payment information, wallet seeds, and cryptocurrency holdings were not compromised. Ledger published an official support article acknowledging the incident and directing affected customers to expect notification from Global-e. Blockchain investigator ZachXBT alerted his audience to the breach and warned users to be vigilant against follow-on phishing campaigns — consistent with patterns observed after the 2020 breach. The January 2026 incident represents Ledger's third significant customer data exposure event in under six years, reinforcing concerns about the company's supply chain and third-party vendor security practices.","heading":"January 2026 Third-Party Data Breach (Global-e)","severity":"high","sources":[{"credibility":1,"name":"Ledger: Global-e Incident to Order Data (Official Support Page)","type":"official","url":"https://support.ledger.com/article/Global-e-Incident-to-Order-Data---January-2026"},{"credibility":1,"name":"CoinDesk: Crypto Wallet Firm Ledger Faces Data Breach Through Global-e Partner","type":"news","url":"https://www.coindesk.com/markets/2026/01/05/crypto-wallet-firm-ledger-faces-data-breach-through-global-e-partner"},{"credibility":1,"name":"The Register: Ledger Confirms Customer Data Lifted After Global-e Snafu","type":"news","url":"https://www.theregister.com/2026/01/06/ledger_globale_breach/"},{"credibility":1,"name":"BleepingComputer: Ledger Customers Impacted by Third-Party Global-e Data Breach","type":"news","url":"https://www.bleepingcomputer.com/news/security/ledger-customers-impacted-by-third-party-global-e-data-breach/"},{"credibility":2,"name":"CoinPedia: Ledger Faces New Data Breach, ZachXBT Alerts Users","type":"news","url":"https://coinpedia.org/crypto-live-news/ledger-faces-new-data-breach-zachxbt-alerts-users/"}]},{"content":"The following on-chain addresses were identified by blockchain security firms Blockaid and SlowMist in connection with the December 2023 Ledger Connect Kit supply chain attack, attributed to the Angel Drainer malware-as-a-service group. Main Drainer Contract: 0x000067464bdcbec51051ddcce8551e702f130000. Collector Wallet (received majority of stolen funds): 0x658729879fca881d9526480b82ae00efc54b5c2d. Operator Wallet (executed draining transactions): 0x00003ffA7857408ab714c28B1451914330240000. Fee Collector Wallet (held ENS name angel-drainer.eth): 0x412f10AAd96fD78da6736387e2C84931Ac20313f. The fee structure of the Angel Drainer infrastructure directed 15% of stolen funds to the fee collector wallet and 85% to the main collector wallet. Tether coordinated with Ledger to freeze USDT held in attacker addresses following the incident. For the April 2026 fake app campaign, ZachXBT's on-chain tracing identified over 150 KuCoin deposit addresses and a centralized mixing service called 'AudiA6' as laundering infrastructure, but specific attacker deposit addresses were not published in reporting reviewed.","heading":"Known Attacker Addresses (Connect Kit Exploit)","severity":"high","sources":[{"credibility":2,"name":"Blockaid: Attack Report — Ledger Connect Kit (Primary Address Source)","type":"onchain","url":"https://www.blockaid.io/blog/attack-report-ledger-connect-kit"},{"credibility":2,"name":"SlowMist: Supply Chain Attack on Ledger Connect Kit Analysis","type":"onchain","url":"https://slowmist.medium.com/supply-chain-attack-on-ledger-connect-kit-analyzing-the-impact-and-preventive-measures-1005e39422fd"},{"credibility":2,"name":"Sonatype: Ledger Connect-Kit Compromise — A Crypto Drainer Attack","type":"news","url":"https://www.sonatype.com/blog/decrypting-the-ledger-connect-kit-compromise-a-deep-dive-into-the-crypto-drainer-attack"}]},{"content":"No enforcement actions by the SEC, CFTC, DOJ, or French financial regulators (AMF, CNIL) against Ledger SAS were identified in available public records as of May 2026. The 2021 U.S. class action lawsuit (Chu et al. v. Ledger SAS) was dismissed on jurisdictional grounds without ruling on the merits. Ledger remains a legally operating company incorporated in France. Its devices are sold globally through authorized retail channels. The absence of regulatory action reflects the company's status as a legitimate hardware manufacturer rather than a financial service provider or token issuer subject to direct securities regulation. However, the company's handling of customer data — particularly the 2020 breach and the 2026 Global-e incident — has drawn criticism from privacy advocates and security researchers regarding compliance with GDPR obligations, though no confirmed CNIL fines were identified in available sources.","heading":"Regulatory and Legal Standing","severity":"medium","sources":[{"credibility":1,"name":"Bloomberg Law: Ledger, Shopify Beat Data Breach Class Suit","type":"news","url":"https://news.bloomberglaw.com/privacy-and-data-security/ledger-shopify-beat-data-breach-class-suit-due-to-home-bases"},{"credibility":1,"name":"Schneider Wallace: Class Action Complaint Filing","type":"court_filing","url":"https://www.schneiderwallace.com/media/ledger-shopify-class-action-lawsuit-data-breach-cover-up/"}]},{"content":"Ledger's own security documentation and independent researchers agree on core protective measures for Ledger hardware wallet users: (1) Never enter a 24-word recovery phrase into any software application, website, or app — legitimate Ledger software never requests this. Recovery phrases should only be entered directly on the physical hardware device itself. (2) Only download Ledger Live from the official Ledger website (ledger.com) or through verified links. Do not use app store listings without confirming the publisher is 'Ledger SAS.' (3) Only purchase Ledger hardware devices directly from ledger.com or authorized resellers — third-party marketplace purchases carry a risk of tampered devices. (4) Users whose data was exposed in the 2020 or 2026 breaches should treat all inbound communications claiming to be from Ledger as potentially fraudulent and verify independently through official channels. (5) Physical letters requesting seed phrase entry or QR code scanning are phishing attacks. Ledger has explicitly confirmed it will never send physical letters asking for recovery phrases.","heading":"User Safety Guidance","severity":"medium","sources":[{"credibility":1,"name":"Ledger: Scams Targeting Crypto Holders (Official)","type":"official","url":"https://support.ledger.com/article/scams-targeting-crypto-holders"},{"credibility":1,"name":"Ledger: Physical Mail Phishing Scam Warning (Official)","type":"official","url":"https://support.ledger.com/article/physical-mail-phishing-scam"}]}],"sources_used":[],"summary":"Ledger SAS is a legitimate French company founded in 2014 that manufactures widely used hardware wallets (Ledger Nano S, Nano X, Nano S Plus). Despite being a legitimate business with no fraud allegations against the company itself, Ledger has accumulated a serious incident record including a major 2020 customer data breach that exposed physical addresses for 272,000 users and email addresses for over 1 million — data subsequently weaponized for years of phishing, social engineering, and physical threat campaigns. Additional incidents include a December 2023 supply chain attack on the Ledger Connect Kit JavaScript library that drained over $600,000 from DeFi users, a January 2026 third-party data breach via payment processor Global-e, and a wave of fake Ledger Live applications — including one on the Apple App Store that blockchain investigator ZachXBT traced to $9.5 million in theft across 50+ victims in April 2026.","timeline":[{"date":"2020-06","event":"Ledger e-commerce database breached via Shopify employee access; data includes over 1 million email addresses and 272,853 full customer records with home addresses.","source":"Ledger CEO Official Statement","source_url":"https://www.ledger.com/message-ledgers-ceo-data-leak"},{"date":"2020-07","event":"Ledger publicly discloses the data breach.","source":"Ledger CEO Official Statement","source_url":"https://www.ledger.com/message-ledgers-ceo-data-leak"},{"date":"2020-12","event":"Stolen Ledger customer data publicly dumped on hacking forums, triggering waves of phishing, extortion emails, and physical threat letters targeting customers at their home addresses.","source":"Bitdefender Report","source_url":"https://www.bitdefender.com/en-us/blog/hotforsecurity/hacker-publishes-stolen-email-and-mailing-addresses-of-270000-ledger-cryptocurrency-wallet-users"},{"date":"2021-04","event":"Class action lawsuit filed by Schneider Wallace against Ledger SAS and Shopify, alleging negligence and cover-up of the 2020 data breach.","source":"Schneider Wallace / Decrypt","source_url":"https://decrypt.co/65917/ledger-lawsuit-data-breach"},{"date":"2021-11","event":"U.S. District Court dismisses class action against Ledger and Shopify on jurisdictional grounds; no ruling on merits.","source":"Bloomberg Law","source_url":"https://news.bloomberglaw.com/privacy-and-data-security/ledger-shopify-beat-data-breach-class-suit-due-to-home-bases"},{"date":"2023-05","event":"Ledger announces 'Ledger Recover' optional seed phrase backup subscription service; announcement sparks major community backlash over security and privacy concerns. Launch postponed.","source":"CoinDesk","source_url":"https://www.coindesk.com/tech/2023/05/16/ledger-bats-back-criticism-of-new-wallet-recovery-service"},{"date":"2023-10","event":"Ledger Recover service officially launches for Nano X users despite earlier controversy.","source":"CoinDesk","source_url":"https://www.coindesk.com/tech/2023/10/24/crypto-wallet-maker-ledger-officially-rolls-out-recover-unleashing-fresh-round-of-snark"},{"date":"2023-12-14","event":"Supply chain attack on Ledger Connect Kit npm package. Former Ledger employee's account compromised via phishing. Malicious versions 1.1.5, 1.1.6, 1.1.7 injected Angel Drainer malware into DeFi frontends. Over $600,000 drained. Attacker addresses identified on-chain. Tether freezes USDT.","source":"TechCrunch / The Hacker News","source_url":"https://techcrunch.com/2023/12/14/supply-chain-attack-targeting-ledger-crypto-wallet-leaves-users-hacked/"},{"date":"2026-01","event":"Third-party payment processor Global-e discloses unauthorized access to cloud systems containing Ledger customer order data including names and contact details. ZachXBT alerts community.","source":"CoinDesk / CoinPedia","source_url":"https://www.coindesk.com/markets/2026/01/05/crypto-wallet-firm-ledger-faces-data-breach-through-global-e-partner"},{"date":"2026-04-07","event":"Fake Ledger Live app published on Apple App Store by 'Leva Heal Limited' begins draining victim wallets via seed phrase phishing.","source":"CoinDesk","source_url":"https://www.coindesk.com/business/2026/04/14/a-fake-ledger-app-on-the-apple-app-store-just-drained-usd9-5-million-in-crypto"},{"date":"2026-04-13","event":"Blockchain investigator ZachXBT traces $9.5 million in losses from fake Ledger Live app to 150+ KuCoin deposit addresses and 'AudiA6' mixing service. Musician G. Love publicly identified as losing 5.92 BTC.","source":"The Block / CoinTelegraph","source_url":"https://www.theblock.co/post/397388/fake-ledger-app-apple-app-store-crypto-theft-bitcoin-tron-solana-zachxbt"},{"date":"2026-04-14","event":"Apple removes fake Ledger Live application from App Store following community reports. ZachXBT argues incident may support class action against Apple.","source":"Apple Insider","source_url":"https://appleinsider.com/articles/26/04/14/bogus-crypto-wallet-on-app-store-steals-95m"}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 32135e8a-3fe5-43d5-863d-fe4f1723a0ba
  2. #2reviewby reviewerreviewer
    2026-06-09 02:17:00Z
    Score: 58 → 58 (no score change)
    The Ledger investigation page is well-sourced and factually accurate across nearly all verified claims. The core security incidents — the 2020 breach, the December 2023 Connect Kit supply chain attack, the January 2026 Global-e breach, and the April 2026 fake app campaign — are all corroborated by multiple tier-1 sources. Minor issues include: the $70.9M ARR figure traces only to a self-reported data aggregator; the IPO status is stale (plans paused May 2026); the founder list omits three of eight co-founders; the Ledger Recover third custodian is not named; and the Connect Kit loss estimates exhibit variance across sources reflecting different methodologies rather than fabrication.
    anchoranchored
    chain
    ●mainnet-betaslot 425,235,596
    sig
    4sxeHVRmJk7A…NkSmGVU6explorer ↗
    hash
    FoZcqEvmdXjB…j2qtVYvNsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1033 B) ▸
    {"actor":"reviewer","decided_at":"2026-06-09T02:16:59.953Z","decision":"review","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","new_score":58,"page_slug":"ledger","prev_score":58,"reason":"The Ledger investigation page is well-sourced and factually accurate across nearly all verified claims. The core security incidents — the 2020 breach, the December 2023 Connect Kit supply chain attack, the January 2026 Global-e breach, and the April 2026 fake app campaign — are all corroborated by multiple tier-1 sources. Minor issues include: the $70.9M ARR figure traces only to a self-reported data aggregator; the IPO status is stale (plans paused May 2026); the founder list omits three of eight co-founders; the Ledger Recover third custodian is not named; and the Connect Kit loss estimates exhibit variance across sources reflecting different methodologies rather than fabrication.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 12a31734-fc1e-4c84-a145-18d478f78116
  3. #3review reviseby judgejudge
    2026-06-09 02:17:00Z
    Score: 58 → 53 (-5)
    The reviewer verified 31 claims and found zero actively disputed by opposing sources. 23 were fully confirmed by Tier 1 sources. The five partially_supported findings (claim_findings[10], [11], [20], [24], [25]) reflect methodology variance in loss estimates, a minor USD conversion discrepancy, and editorial omissions — none contradict core allegations. One stale finding (claim_findings[26]) is the most material issue: the page states Ledger was evaluating a US IPO above $4 billion as of early 2026, but as of May 2026 Ledger paused those plans indefinitely; this factual development is missing from the page. One unverifiable ARR figure (claim_findings[27]) traces only to a self-reported data aggregator with no Tier 1 corroboration. These items do not impugn the page's core security incident record but require editorial correction.
    anchoranchored
    chain
    ●mainnet-betaslot 425,235,599
    sig
    5QGkKVb3yrzx…K9gVutexexplorer ↗
    hash
    2G98QvgwXnoV…sJuaAY9Dsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1188 B) ▸
    {"actor":"judge","decided_at":"2026-06-09T02:16:59.953Z","decision":"review_revise","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","new_score":53,"page_slug":"ledger","prev_score":58,"reason":"The reviewer verified 31 claims and found zero actively disputed by opposing sources. 23 were fully confirmed by Tier 1 sources. The five partially_supported findings (claim_findings[10], [11], [20], [24], [25]) reflect methodology variance in loss estimates, a minor USD conversion discrepancy, and editorial omissions — none contradict core allegations. One stale finding (claim_findings[26]) is the most material issue: the page states Ledger was evaluating a US IPO above $4 billion as of early 2026, but as of May 2026 Ledger paused those plans indefinitely; this factual development is missing from the page. One unverifiable ARR figure (claim_findings[27]) traces only to a self-reported data aggregator with no Tier 1 corroboration. These items do not impugn the page's core security incident record but require editorial correction.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision a423b9bd-f5bc-491e-a14e-a9fc94545945
  4. #4reviewby reviewerreviewer
    2026-10-27 11:09:34Z
    Score: 58 → 58 (no score change)
    The incident chronology (2020 breach, Connect Kit, fake App Store app, Global-e) is well sourced, hedged and matches the sources I read. The main defect is staleness: the page says Ledger is preparing a US IPO, but May 2026 reporting says it paused. The timeline and summary also attribute the 270,000-address figure to Ledger's own notice, which says about 9,500. Many claims were not verified in depth, so confidence is limited.
    anchoranchored
    chain
    ●mainnet-betaslot 462,048,319
    sig
    hhCHy3UqD8XD…dzFFqDNtexplorer ↗
    hash
    Gfsw6RQZYwFd…xzhHNiBysha256 → base58
    verifying row…full verify ↗
    canonical bytes (1275 B) ▸
    {"actor":"reviewer","artifact_identity":"53f7cc1de4bb4212f6609544412b3ef0","decided_at":"2026-10-27T11:09:34.040Z","decision":"review","disputed_pct":0.2857,"findings_hash":"CwxFWgFRtBNunj5fFLH5yRVyL53CPLFmRwYaL7kARAcK","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"omissions":{"material":0,"total":2},"page_content_hash":"fad9536d098265d50083bd8c00272748fde11d697b599e31c46d4f9b59b99e03","page_slug":"ledger","prev_score":58,"reason":"The incident chronology (2020 breach, Connect Kit, fake App Store app, Global-e) is well sourced, hedged and matches the sources I read. The main defect is staleness: the page says Ledger is preparing a US IPO, but May 2026 reporting says it paused. The timeline and summary also attribute the 270,000-address figure to Ledger's own notice, which says about 9,500. Many claims were not verified in depth, so confidence is limited.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision b96f5790-a81e-4aef-8a39-e9baeaa711ad
  5. #5review reviseby judgejudge
    2026-10-27 11:09:34Z
    Score: 58 → 51 (-7)
    Counting 2 unverifiable findings out of 7 claim findings gives about 29% (claim_findings[4] and claim_findings[6], both not_found, neither source_blocked), which falls in the minor band. The most important defect is claim_findings[0]: the page says Ledger is preparing a US IPO, but May 2026 reporting says it paused. claim_findings[1] also notes that the 270,000-address figure is attributed to Ledger's own notice, which gives about 9,500 customers. The core incident chronology (2020 breach, fake App Store app) was confirmed against Tier 1 and Tier 2 sources, and the reviewer's own confidence is limited (0.5) because several claims were not verified in depth.
    anchoranchored
    chain
    ●mainnet-betaslot 462,048,324
    sig
    3vAigraTm89C…NsZEB6Xmexplorer ↗
    hash
    1BgVarCTAarR…g55tkRX7sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1943 B) ▸
    {"actor":"judge","artifact_identity":"53f7cc1de4bb4212f6609544412b3ef0","band_override":null,"decided_at":"2026-10-27T11:09:34.040Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"03d5d83f-6247-4200-998e-048db3536286","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"ledger","prev_score":58,"reason":"Counting 2 unverifiable findings out of 7 claim findings gives about 29% (claim_findings[4] and claim_findings[6], both not_found, neither source_blocked), which falls in the minor band. The most important defect is claim_findings[0]: the page says Ledger is preparing a US IPO, but May 2026 reporting says it paused. claim_findings[1] also notes that the 270,000-address figure is attributed to Ledger's own notice, which gives about 9,500 customers. The core incident chronology (2020 breach, fake App Store app) was confirmed against Tier 1 and Tier 2 sources, and the reviewer's own confidence is limited (0.5) because several claims were not verified in depth.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-7,"score_limit":{"applied":-7,"limited":true,"proposed":-12,"rule":"limited_no_second_opinion","second":null},"sequence_num":5,"severity_override":{"applied":true,"band":"minor","from_band":"minor","reason":"The review reports subject_status.contradicts_page: the summary and company background say Ledger is preparing a US IPO, while May 2026 reporting says it paused the plan. Ledger is still operating with no sanction or shutdown, and the omissions are rated minor, so the page is held in the minor band rather than moved to significant. The contradiction is why the delta sits toward the harsher end of that band and why the verdict is not approve."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision c3cf6814-3e54-4a40-99a0-9ff712f82185
  6. #6rescoreby systemsystem
    2026-11-01 12:36:57Z
    Score: 51 → 54 (+3)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 51 → 54. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −6, problems around the subject, caused by others −5.2; legitimacy credit long-running +10; the penalty for incidents it suffered is capped at 20; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−12) now shown as page reliability, not in the score.
    anchoranchored
    chain
    ●mainnet-betaslot 464,094,633
    sig
    itKFqrv3ry1n…RiVm3Tetexplorer ↗
    hash
    CeCAF1jUDxAm…vZGodvTJsha256 → base58
    verifying row…full verify ↗
    canonical bytes (829 B) ▸
    {"actor":"system","decided_at":"2026-11-01T12:36:57.622Z","decision":"rescore","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","new_score":54,"page_slug":"ledger","prev_score":51,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 51 → 54. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −6, problems around the subject, caused by others −5.2; legitimacy credit long-running +10; the penalty for incidents it suffered is capped at 20; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−12) now shown as page reliability, not in the score.","score_delta":3,"score_model":"v2","sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 79263bda-c0f7-4e79-b0be-93f222571f14
  7. #7rescoreby systemsystem
    2026-11-02 09:52:24Z
    Score: 54 → 59 (+5)
    Re-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 54 → 59. Problems weighed by who is responsible: incidents the subject suffered −15.2, concerns that are not fraud −9.2, problems around the subject, caused by others −2.1; legitimacy credit long-running +10.
    anchoranchored
    chain
    ●mainnet-betaslot 464,451,803
    sig
    24n9y4EdLqo9…2Y5ctoMdexplorer ↗
    hash
    8j2amhj5R3K8…oTLfendhsha256 → base58
    verifying row…full verify ↗
    canonical bytes (706 B) ▸
    {"actor":"system","decided_at":"2026-11-02T09:52:23.968Z","decision":"rescore","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","new_score":59,"page_slug":"ledger","prev_score":54,"reason":"Re-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 54 → 59. Problems weighed by who is responsible: incidents the subject suffered −15.2, concerns that are not fraud −9.2, problems around the subject, caused by others −2.1; legitimacy credit long-running +10.","score_delta":5,"score_model":"v2","sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision c1a4d693-e1ff-4f65-97eb-37bee73b8579
  8. #8reviewby reviewerreviewer
    2026-11-02 09:54:59Z
    Score: 59 → 59 (no score change)
    The IPO pause, fake-app theft figures and the Global-e incident are supported. One clear defect: the timeline dates the plaintiff's discovery of the loss to 2026-02, while the page text and press coverage say February 20, 2025. Several details (S-1 status, Apple guideline and account termination, 7M-unit/3% estimate in the cited Protos piece) were not found in the cited sources. Older 2020 and 2023 claims were not verified in this pass.
    anchoranchored
    chain
    ●mainnet-betaslot 464,452,543
    sig
    23zbykYkDf1n…5c1r53Fhexplorer ↗
    hash
    2b3b8Eu2BvWR…nMPFvL8ssha256 → base58
    verifying row…full verify ↗
    canonical bytes (1249 B) ▸
    {"actor":"reviewer","artifact_identity":"0c586cefa1be951ed27510f93bca8e7d","decided_at":"2026-11-02T09:54:59.260Z","decision":"review","disputed_pct":0.4286,"findings_hash":"Ektq6hs1fH25QgbaMaGfJDds2Q3hVNAcgo3oQPjaG2uf","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"page_content_hash":"1107951b53d99a9e548eb6a22d034e2b3efa2621904fe6741704e05aaf26e92c","page_slug":"ledger","prev_score":59,"reason":"The IPO pause, fake-app theft figures and the Global-e incident are supported. One clear defect: the timeline dates the plaintiff's discovery of the loss to 2026-02, while the page text and press coverage say February 20, 2025. Several details (S-1 status, Apple guideline and account termination, 7M-unit/3% estimate in the cited Protos piece) were not found in the cited sources. Older 2020 and 2023 claims were not verified in this pass.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":8,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 76738357-fd5b-4b54-be1d-099450167d7c
  9. #9review reviseby judgejudge
    2026-11-02 09:54:59Z
    Score: 59 → 59 (no score change)
    Of 7 claims checked, 1 was disputed and 2 could not be verified in the cited sources, giving a 43% disputed-or-unverifiable share (claim_findings[0], [3], [5]). The disputed item is a timeline entry dating the plaintiff's discovery of the loss to 2026-02, while the page text and press coverage say February 20, 2025. The two unverifiable items (the S-1 status and Apple's guideline citation and account termination) were not found in the fetched sources, and this does not show they are wrong. Core facts such as the IPO pause, the fake-app theft figures and the Global-e breach were confirmed. Because the reviewer's confidence is moderate and the 2020 and 2023 claims were not checked in this pass, the penalty sits at the low end of the band.
    anchoranchored
    chain
    ●mainnet-betaslot 464,452,548
    sig
    2U9vdGMHDDi6…iPpUwQdWexplorer ↗
    hash
    3tKAmz37MFoH…mw4brb7Vsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1386 B) ▸
    {"actor":"judge","artifact_identity":"0c586cefa1be951ed27510f93bca8e7d","band_override":null,"decided_at":"2026-11-02T09:54:59.260Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4286,"investigation_id":"03d5d83f-6247-4200-998e-048db3536286","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"page_slug":"ledger","prev_score":59,"reason":"Of 7 claims checked, 1 was disputed and 2 could not be verified in the cited sources, giving a 43% disputed-or-unverifiable share (claim_findings[0], [3], [5]). The disputed item is a timeline entry dating the plaintiff's discovery of the loss to 2026-02, while the page text and press coverage say February 20, 2025. The two unverifiable items (the S-1 status and Apple's guideline citation and account termination) were not found in the fetched sources, and this does not show they are wrong. Core facts such as the IPO pause, the fake-app theft figures and the Global-e breach were confirmed. Because the reviewer's confidence is moderate and the 2020 and 2023 claims were not checked in this pass, the penalty sits at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":9,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 0d626a3a-f2f4-4dc4-94c8-6b98c40108c4
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.