Bitcoin Wallets & Self-Custody

Ledger Security: Complete Analysis

Jan 26, 2026 · 28 min read · Updated Latest correction
A narrow black signing device with a partly opened steel swivel cover rests on charcoal suede.

Ledger Security: A Complete Analysis of the World’s Largest Hardware Wallet Maker

Ledger has sold more hardware wallets than any other manufacturer: more than eight million devices, by its own count (November 2026), since the company was founded in Paris in 2014. That market dominance makes Ledger’s security posture a matter of broad importance: millions of users trust their bitcoin to Ledger’s architecture. This analysis examines Ledger’s security model, its track record of incidents, the ongoing debates around its design philosophy, and what current and prospective users should understand.

Updated 7 November 2026: the timeline now includes the October 2026 hidden implant found in a Ledger sold by an authorised reseller, and the January 2026 Global-e leak is described as Ledger and Global-e reported it. The chip details follow Ledger’s current specifications (EAL6+ on every model except the Nano X), Ledger’s app is called Ledger Wallet (Ledger Live until October 2025), and the advice on Recover no longer suggests skipping firmware updates.

Ledger’s Security Architecture

Ledger’s hardware wallets (the Nano S Plus, Nano X, Nano Gen5, Flex and Stax) share a common security architecture built around a certified secure element chip.

Secure Element (Common Criteria certified): Ledger uses STMicroelectronics secure element chips from the ST33 series. The ST33K1M5 in the Nano S Plus, Nano Gen5, Flex and Stax is certified CC EAL6+; the older ST33J2M0 in the Nano X is certified EAL5+, one level below. These chips are the same class used in passports and bank cards. The secure element stores private keys and performs all cryptographic operations in an isolated environment. It is designed to resist physical attacks including decapping, power analysis, and fault injection. This is a genuine security advantage — the secure element is hardened silicon, not a general-purpose microcontroller.

BOLOS Operating System: Ledger developed its own operating system called BOLOS (Blockchain Open Ledger Operating System) that runs on the secure element. BOLOS provides application isolation, meaning each cryptocurrency app runs in its own sandbox. A vulnerability in the Ethereum app, for example, should not compromise the Bitcoin app. BOLOS also handles the secure display pipeline, ensuring what you see on screen is what the secure element is actually signing.

Proprietary firmware: The firmware running on Ledger’s secure element is proprietary and closed-source. Ledger argues that the secure element manufacturer’s NDA prevents them from open-sourcing this code, and that the Common Criteria certification process provides equivalent assurance through third-party auditing. This is the central tension in Ledger’s security story, and we will examine it in detail below.

For a broader view of how different wallet architectures compare, our lesson Hardware Wallets Explained covers the design tradeoffs, from secure element chips to air-gapped signing.

The Closed-Source Debate

Ledger’s firmware for the secure element is not open source. This is a fundamental philosophical divide between Ledger and competitors like Trezor, Coldcard, and Blockstream Jade, all of which publish their firmware source code.

Ledger’s position is straightforward: the secure element NDA restricts disclosure, and the Common Criteria certification means the code has been audited by accredited labs. They argue that publishing source code for a secure element could actually reduce security by giving attackers a roadmap.

The counterargument is equally direct: users cannot verify what the firmware does. The certification audits functionality and resistance to specific attack classes, but it does not audit for intentional backdoors or privacy violations. Users must trust Ledger’s engineering team and the certification lab — they cannot verify for themselves. In Bitcoin’s ethos of “don’t trust, verify,” this is a significant gap.

The Ledger Recover incident in 2023 (detailed below) brought this debate to a sharp point: firmware running on the secure element was updated to include functionality that could export seed phrase fragments over the internet. Because the firmware is closed-source, users had no way to inspect or object to this capability before it shipped. The deeper implications of open versus closed source are explored in our article on the ethics of open source in Bitcoin hardware security.

Timeline of Security Incidents

Ledger's incidents drawn as nested layers around the chip that holds your keys, from the farthest from it to the closest. Your name and address, nowhere near the device: in 2020 Ledger's own shop database leaked about 272,000 customers' names, home addresses and phone numbers, published on a hacker forum in December 2020, and phishing and threats followed; in January 2026 Global-e, Ledger's payments partner, lost names and contact details from Ledger.com orders. The software around it, on your computer: in December 2023 Connect Kit, a library web apps use to talk to a Ledger, was poisoned and tricked people into signing transactions that emptied their wallets. Inside the device but outside the chip: in October 2026 a part hidden in genuine devices sold through a reseller read the 24 words off the screen during setup and sent them to the attacker. The code on the chip: in May 2023 Recover, an opt-in service, showed that an update can make the chip send out encrypted pieces of your seed: a question of trust, not an attack. At the centre, your keys inside the chip: no public case of keys taken out of a locked Ledger's secure element.
No incident has taken keys out of a Ledger’s chip. They hit what surrounds it: customer data, the software you sign with, a device opened before it reached its buyer, and the trust you place in code you can’t read.

2020 Database Breach

In June 2020, an unauthorized party used an API key to copy data from Ledger’s e-commerce and marketing database; a researcher taking part in Ledger’s bug bounty reported the leak on 14 July. Ledger disclosed that about one million email addresses had been taken, along with the names, postal addresses and phone numbers of about 9,500 customers.

In December 2020, a copy of the database was dumped publicly on RaidForums. Besides the email addresses, it held the full personal details — including names, physical mailing addresses, and phone numbers — of about 272,000 customers who had purchased devices. This was catastrophic. Ledger customers’ home addresses were now publicly linked to their ownership of cryptocurrency hardware wallets. The consequences were immediate and severe.

A second, separate 2020 leak came to light in January 2021: rogue members of the support team at Shopify, the platform behind Ledger’s online store, had exported Ledger customer records in April and June 2020. Ledger said about 292,000 customers were affected; 93% of the records matched the first leak, but about 20,000 customers were new.

Post-Breach Phishing and Physical Threats

Following the data dump, Ledger users were targeted by sophisticated phishing campaigns. Attackers sent emails and physical mail that impersonated Ledger, including fake replacement devices preloaded with modified firmware. Some users reported receiving physical threats and extortion attempts at their home addresses. At least one case of a violent home robbery targeting a known crypto holder was linked to the leaked data.

This incident illustrated a risk unique to hardware wallet manufacturers: the customer database itself is a high-value target. Knowing that someone bought a hardware wallet means they likely hold significant cryptocurrency. The combination of name, home address, and email provides everything an attacker needs for targeted phishing or physical coercion. Understanding how these threats overlap with chain analysis techniques is covered in our privacy and chain analysis guide.

May 2023: Ledger Recover Controversy

In May 2023, Ledger announced Ledger Recover, an optional paid service built into its firmware. If you sign up and approve it on the device, it encrypts your seed, splits it into three fragments held by three separate companies (Ledger, Coincover and EscrowTech), and lets you recover with two of them after an identity check.

Four steps of Ledger Recover. 1, you opt in: you pay, prove who you are, then enter your PIN and approve on the device. 2, the device's chip encrypts your seed and splits it into three pieces. 3, three companies, Ledger, Coincover and EscrowTech, each keep one piece, and none has the whole seed. 4, to recover, you pass identity checks, then two of the three pieces, normally Ledger's and Coincover's, go back to a Ledger device, which rebuilds your seed. The debate: critics say the code that can send these pieces out is on every updated Ledger and you can't read it; Ledger says it runs only after you sign up, enter your PIN and approve on the device.
Recover sends three encrypted pieces of your seed to three companies; any two rebuild it. It runs only if you sign up and approve it on the device. The worry is that the code able to do it ships on every updated Ledger, and nobody outside Ledger can read it.

The backlash was immediate and intense. The core objection: the firmware update proved that Ledger’s secure element firmware could extract and transmit seed phrase material over the internet. Even though Recover was opt-in, the capability existed in the firmware running on every updated device. Users who did not opt in to Recover still had firmware on their secure element that was technically capable of exporting their seed.

Ledger’s CTO publicly stated that this capability had always existed in theory — that any firmware update could potentially include such functionality — and that users had always been trusting Ledger not to do this. Many users found this argument alarming rather than reassuring. It highlighted the fundamental limitation of closed-source firmware: you cannot verify what it does, and Ledger had just demonstrated a willingness to add seed export functionality.

Ledger replied that Recover is opt-in and needs your PIN and approval on the device. It later committed to open-sourcing portions of the Recover protocol and accelerating its open-source roadmap, but the core secure element firmware remains closed as of November 2026. In principle any hardware wallet’s firmware could be changed to export a seed; the debate is over how much you can verify, which open-source firmware makes easier.

December 2023: Connect Kit Supply Chain Attack

In December 2023, a former Ledger employee fell victim to a phishing attack that compromised their credentials for Ledger’s npm package repository. The attacker injected malicious code into the Ledger Connect Kit — a JavaScript library used by decentralized applications (dApps) to connect to Ledger devices. The malicious version redirected transaction approvals to the attacker’s wallet, draining users who signed blind on affected dApps. Early reports counted $484,000; on 20 December Ledger put the total at approximately $600,000. Ledger’s incident report says about five hours passed from the compromise of the npm account to the complete fix, and that funds were drained for under two hours of that time.

This attack did not compromise the hardware wallet itself or the secure element. It targeted the software supply chain around the device. But it demonstrated that Ledger’s security perimeter extends far beyond the hardware, and a single compromised employee credential could impact users across the ecosystem. The broader implications of supply chain attacks on hardware wallets are discussed in our analysis of side-channel and supply chain attack risks.

January 2026 Global-e Third-Party Breach

On 5 January 2026, Ledger customers were told that Global-e, the payments partner that acts as merchant of record for orders on Ledger.com, had found that an unknown party copied order data from its systems. The data included customer names and contact details, such as postal and email addresses and phone numbers, along with order details. Global-e did not say how many people were affected. Ledger said its own systems were not breached, that no payment information was involved, and that Global-e has no access to customers’ recovery phrases. Still, it reopened the same fundamental wound: Ledger customers’ home addresses were again in the hands of attackers.

This third leak of customer data, the second through a partner rather than Ledger’s own systems, underscored that the customer data problem is structural, not incidental. Any company that ships physical products holds customer data across several partners, any of which can be compromised.

October 2026: Hidden Implant in a Device From an Authorised Reseller

On 10 October 2026 Ledger confirmed that a device sold by CryptoBilis, an authorised reseller of Ledger and Trezor in Southeast Asia, contained an unauthorised hardware implant. According to Ledger’s security team, the implant “reads the data shown on the screen” during setup, decodes the 24 recovery words and sends them out over a mobile (LTE) connection. Ledger says the attackers had bought genuine devices, opened them, fitted the hidden parts and put them back into distribution through resellers in the region, and that it found no compromised units when it screened its own stock. On 30 October Trezor said it had a credible report, not yet examined in its lab, of a similar implant in a Trezor Safe 5 bought from the same reseller.

The implant didn’t break Ledger’s chip or code: it read the recovery words off the screen as the device showed them. That’s why the maker’s authenticity check can’t catch every physical change, and why our advice is to buy new from the maker’s own store, not from resellers or marketplaces. If you bought a device from CryptoBilis, follow the steps in our advisory: don’t set it up, or move your funds to a new seed made on a different device.

Inside a tampered Ledger during setup. The screen shows your 24 recovery words. A hidden part, added after the device left Ledger, reads the screen and sends the 24 words to the attacker over a mobile network. The secure element next to it is genuine and untouched. Genuine Check, in the Ledger app, checks the secure element's signature with Ledger's servers, so it passes because the chip is real; it can't detect a part added next to the chip. The check proves the chip, not the whole device: buy new from Ledger's own store, so nobody in between had the box.
The implant never touched the chip: it read the words off the screen. That is why Genuine Check, which tests the chip, still passes. Buying new from Ledger’s own store keeps anyone in between from opening the box.

Physical Security Analysis

Setting aside the data breach and firmware controversies, Ledger’s physical device security is strong. The secure element provides genuine protection against physical extraction attacks. An attacker who steals a locked Ledger device faces serious obstacles:

  • The PIN is enforced by the secure element: three wrong PINs in a row reset the device and erase its keys, which your written recovery words restore
  • The secure element resists physical probing, power analysis and fault injection, certified EAL6+ (EAL5+ on the Nano X)
  • Extracting keys from the ST33 secure element without the PIN would require nation-state-level resources and is not a practical attack for ordinary thieves
Someone steals your Ledger, locked with your PIN, and tries two things. Guessing the PIN: after three wrong PINs in a row the device resets and erases its keys. Attacking the chip by probing, power analysis or fault injection: the secure element is certified to resist them, EAL6+, or EAL5+ on the Nano X. Meanwhile you restore your wallet on a new device from your words on paper or metal, and the thief gets nothing. The PIN and the chip protect the device; your written words protect your bitcoin.
A thief gets three guesses at your PIN, then the keys are gone. Attacks on the chip itself meet a secure element certified to resist them, and your words on paper or metal bring your wallet back on a new device.

This is meaningfully different from wallets built on general-purpose microcontrollers (like older Trezor models), which are more vulnerable to physical extraction via voltage glitching. The secure element is a real security feature, not marketing.

Supply Chain Security Concerns

Ledger devices are manufactured and shipped from multiple locations, passing through various logistics partners. Given the repeated customer data breaches, attackers know exactly who is receiving Ledger devices and where. This creates a targeted supply chain risk: intercepting a specific person’s shipment and replacing it with a modified device.

That risk is no longer theoretical: in October 2026 a hidden implant that copied the recovery words was found in a Ledger sold through an authorised reseller (see the timeline above).

Ledger implements anti-tampering measures: a cryptographic attestation check verifies the device is genuine. When you connect a new Ledger to the Ledger Wallet app (formerly Ledger Live), its Genuine Check confirms the device’s authenticity with Ledger’s servers. This catches a counterfeit device, but it relies on the closed-source attestation process working correctly and on the user actually running the check, and Ledger itself says the check can’t detect hardware added beside a genuine chip, such as a spying implant. The defence that removes the middle link is buying new from Ledger’s own store, ledger.com, never from marketplaces or second-hand.

The Ledger Recover Debate in Detail

Ledger Recover deserves deeper examination because it represents a philosophical shift in hardware wallet design. Traditional hardware wallets follow a simple principle: private keys are generated on the device and never leave the device. Recover breaks this principle by design — it exports seed material, albeit encrypted and fragmented, to third-party custodians.

Ledger’s argument for Recover is pragmatic: most people lose access to their Bitcoin not through theft but through lost or damaged seed backups. A custodial recovery option, gated by identity verification, saves more funds than it risks. This is probably true at a statistical level for the broader market.

The Bitcoin community’s objection is principled: the entire point of self-custody is eliminating third-party trust. Recover reintroduces it. Worse, the capability exists in the firmware whether or not you opt in, which means you are trusting Ledger not to activate it without consent (or not to be compelled by a government to activate it).

For users who want seed backup solutions that do not involve firmware-level export capabilities, multisig configurations offer a more trust-minimized approach. Our article on multisig security architecture and recovery protocols covers these alternatives.

Comparison with Open-Source Alternatives

Understanding Ledger’s position requires comparing it with the open-source alternatives:

Trezor (Safe 3, Safe 5, Safe 7): Open-source firmware, and Trezor publishes hardware design files. Each model has a secure element (Infineon OPTIGA Trust M, certified EAL6+), and the firmware that talks to it is open source, unlike Ledger’s. Trezor chose a chip that is “NDA-free”, which lets it publish all of its own code; the Safe 7 adds a second chip, TROPIC01, which Trezor presents as independently auditable. The tradeoff is that Trezor’s older models without a secure element were vulnerable to physical extraction attacks that Ledger devices resisted. Trezor Safe devices make a 20-word SLIP-39 backup by default.

Coldcard Mk5 and Q: The Mk5 replaced the Mk4. Both use two secure elements from different makers (Microchip ATECC608 and Maxim DS28C36B), and every Coldcard is Bitcoin-only. The firmware is public on GitHub under the MIT licence with the “Commons Clause”: you can read, build and modify it but not sell it, which makes it “source-available” rather than open source in the strict sense. A firmware flaw disclosed in July 2026 made some Coldcard seeds guessable; see our Coldcard advisory.

Blockstream Jade: Open-source firmware. Instead of a hardware secure element, it uses a “virtual secure element”: the device encrypts your keys and a blind oracle server run by Blockstream (or one you host yourself) holds part of what’s needed to unlock them, without learning the key. A different approach to the same problem.

Foundation Passport: The Passport Core, an open-source, air-gapped, Bitcoin-only device with a secure element, is no longer sold. Foundation now sells the Passport Prime, which we have not reviewed.

The pattern is clear: it is possible to use a secure element while keeping the wallet’s own firmware open source. Ledger’s claim that the NDA prevents open sourcing is increasingly undermined by competitors who have found ways to use secure elements with open-source code. For a deeper comparison, see our 2026 hardware wallet buying guide.

Risk Mitigation for Current Ledger Users

If you already own and use a Ledger device, here are concrete steps to reduce your risk exposure:

  • Assume your purchase data has been compromised. If you bought directly from Ledger at any point, operate under the assumption that your name and address are known to attackers. Be vigilant about phishing emails, text messages, and physical mail claiming to be from Ledger.
  • Never enter your seed phrase into any software or website. Ledger will never ask you to do this. Any email, app, or website requesting your seed phrase is a scam. This is the single most common attack vector against Ledger users.
  • Keep your firmware up to date. Install updates only through the Ledger Wallet app. Older firmware without the Recover code also lacks later security fixes, so skipping updates trades a theoretical risk for known ones; if Recover’s existence worries you, the passphrase and multisig steps below address it without leaving you on old firmware.
  • Use a passphrase. A BIP39 passphrase is an extra secret of your choice that you add to your 24 words. It opens a separate set of accounts with new addresses, so it only protects the coins you send there: your current balance stays on the accounts your 24 words open on their own until you move it. Even if the Recover functionality were activated on your device, it would back up your 24 words, not your passphrase: Ledger does not store or back up passphrases. Anyone who got the 24 words alone could not open the accounts behind your passphrase. Keep an offline copy, exactly as typed and apart from your 24 words, and test it with a small amount before you move the rest: a forgotten or mistyped passphrase locks you out of the funds.
  • Consider migrating to a multisig setup. If your Ledger is one key in a 2-of-3 multisig, a compromise of the Ledger alone does not compromise your funds. This is the strongest mitigation available. Our guide on multisig wallet configurations covers practical implementation.
  • Use Sparrow or Electrum instead of the Ledger Wallet app. Ledger Wallet (formerly Ledger Live) connects to Ledger’s servers to look up the addresses derived from your xpub (the xpub itself stays on your computer, but it reveals all your addresses and balances to anyone who holds it). Using Sparrow with your own Bitcoin node removes that lookup.
  • Check where your device came from. If you bought it from CryptoBilis, or from any seller other than Ledger itself, read our CryptoBilis advisory. For your next device, buy new from ledger.com.
Three setups, and what happens if someone gets your Ledger's 24 words. The seed alone: one key is needed and it leaked, so they can spend it all, since anyone with the words can restore your wallet on any device. With a passphrase: the passphrase is needed too, so the wallet behind it stays shut; Ledger doesn't store or back up passphrases, and if you forget yours you are locked out too. A 2-of-3 multisig with your Ledger as one key and two other devices as the others: two keys are needed and one leaked, which is not enough to spend; use the other two keys to move your coins to a new setup. Either one stops a single leaked seed from emptying your savings; learn it with a small amount before you rely on it.
A passphrase or a multisig setup means the 24 words alone can’t empty your savings. That holds whether the words leak through a misused backup or a found sheet of paper. A device tampered with before it reached you is a different case: move your funds to a new seed made on a different device.

Should You Still Buy a Ledger?

This is where analysis meets opinion, and reasonable people disagree. Here is a balanced assessment:

Arguments in favor: The secure element provides best-in-class physical security. The devices are well-built, user-friendly, and widely supported by third-party software. Ledger has a large security team and the resources to respond to vulnerabilities quickly. For users who accept the closed-source tradeoff and want the strongest protection against physical device theft, Ledger remains a strong option.

Arguments against: Three customer data breaches in six years is a pattern, not a fluke. The Recover firmware controversy demonstrated that Ledger is willing to add seed export capabilities to the secure element, and the closed-source firmware means users cannot verify what future updates will do. The supply chain attack on the Connect Kit showed that Ledger’s security extends beyond the device into a broad attack surface, and the October 2026 reseller implant showed how much depends on where a device was bought (that risk applies to every brand). Open-source alternatives now match or exceed Ledger’s security in most categories except physical tamper resistance of the secure element — and even that gap is narrowing.

The bottom line: If you prioritize physical security and ease of use, and you accept the trust model of closed-source firmware, a Ledger device is a reasonable choice. If you prioritize verifiability, transparency, and alignment with Bitcoin’s “don’t trust, verify” ethos, the open-source alternatives are a better fit. Either way, the device you choose matters less than how you use it — proper seed backup, passphrase usage, and operational security practices are where most wallet security is actually won or lost. Our guide on cold storage and risk management architecture covers these foundational practices.

Part of our free Bitcoin course: This topic is covered in depth in Ledger vs Trezor and Beyond: Choosing the Best Hardware Wallet from the Bitcoin Wallets & Self-Custody course.

Frequently Asked Questions

Has the Ledger secure element ever been cracked?

No known public attack has successfully extracted private keys from a locked Ledger device’s secure element through physical means. Security researchers have demonstrated attacks around the secure element: the wallet.fail team showed attacks on the Nano S, whose screen and buttons ran through the non-secure MCU, and Kraken Security Labs showed supply-chain attacks on the Nano X’s non-secure chip, which handles USB (the Bad Ledger and Blind Ledger attacks), but extracting keys from the ST33 secure element without the PIN has not been publicly achieved. This does not mean it is impossible — state-level actors may have unpublished capabilities — but it has not been demonstrated in the public security research community. The October 2026 implant found in a device sold by an authorised reseller didn’t crack the chip either: it read the recovery words off the screen during setup.

Is Ledger Recover mandatory?

No. Ledger Recover is opt-in and requires the user to actively subscribe to the service, provide identity documents, and confirm the setup on-device. It is not enabled by default. However, the firmware code that enables the seed export capability has shipped in Ledger’s firmware since mid-2023 (version 2.2.1 on the Nano X). The distinction is between the capability existing in the code and the feature being activated by the user. Staying on older firmware to avoid it means missing later security fixes; if the capability concerns you, a passphrase or a multisig setup is the better answer.

Should I be worried about my data from the 2020 breach?

Yes, and permanently. The 2020 database was published publicly and is now permanently available. If your purchase information was in that database, your name, email, physical address, and the fact that you own cryptocurrency hardware are known. This data does not expire. The January 2026 Global-e leak exposed names and contact details from Ledger.com orders again. You should treat any communication claiming to be from Ledger with extreme suspicion, use a PO box or forwarding address for any future crypto-related purchases, and consider the physical security implications of being a known hardware wallet owner.

Can I use a Ledger device without the Ledger Wallet app?

Yes. Ledger devices work with Sparrow Wallet, Electrum and other third-party wallet software, so you can manage your bitcoin entirely without Ledger Wallet (called Ledger Live until October 2025). The primary advantage of using third-party software is privacy: Ledger Wallet looks up the addresses derived from your xpub on Ledger’s servers (the xpub itself stays on your computer), so those servers see which addresses you check. Sparrow connected to your own Bitcoin node removes that lookup. The only tasks that currently require Ledger Wallet are firmware updates and installing apps on the device.

How does Ledger compare to Trezor for physical security?

Ledger has historically held an advantage in physical security because every Ledger has a secure element (EAL6+ today, EAL5+ on the Nano X). Older Trezor models (One, Model T) use general-purpose microcontrollers that are vulnerable to voltage glitching, allowing physical extraction of the seed if an attacker has the device. The Trezor Safe 3, Safe 5 and Safe 7 added a secure element (Infineon OPTIGA Trust M, certified EAL6+), closing most of this gap. The key remaining difference is that Trezor’s firmware, including the code that talks to the secure element, is open source, while Ledger’s is not. For detailed comparisons across all major devices, see our hardware wallet comparison chart.

Filed under: Bitcoin Wallets & Self-Custody

Continue Reading

← Back to All Articles