Skip to main content

Search...

Popular searches

Ledger security incidents

Every recorded Ledger security incident, newest first, with severity, fix status and sources.

Timeline

2026

  1. Hardware implants in Ledger devices sold by CryptoBilis

    HighSupply chainReported losses: $86MMitigated

    Buyers of tampered units lost their recovery phrases at setup and, with them, their funds. The device design is not affected; the risk is in how the devices reached buyers.

  2. Ledger Ethereum app swap flow could sign a token approval in place of a payment

    LowFirmware vulnerabilityFixed

    Users swapping tokens through Ledger's Exchange app with Ethereum app 1.20.0 to 1.22.2 could, via a hostile swap provider, sign a token approval for the agreed amount to the swap's deposit address instead of a payment. Ledger states the permission moves no funds by itself and found no evidence of exploitation.

  3. Ledger Secure SDK flaw let a host change transaction details after on-screen review

    HighFirmware vulnerabilityFixed

    Users of Ledger device apps built on Secure SDK releases from August 2025 through v26.6.0 could, if a compromised host or web page controlled the connection, approve an operation shown correctly on screen and sign different parameters. Ledger states it has no evidence of exploitation against users.

  4. Ledger Monero app exposed Keccak state, letting a compromised host recover spend keys

    HighFirmware vulnerabilityFixed

    Monero holders using a Ledger Monero app older than 2.1.4 on a compromised computer could have their secret view and spend keys extracted without any prompt on the device while the app was open. Ledger states the issue is fixed in Monero app 2.1.4 and that the prerequisites considerably limit practical exploitability.

  5. Fake Ledger Live app in Apple's App Store

    HighTargeted phishingReported losses: $9.5MNot applicable

    Mac users who installed the fake app and entered their recovery phrase lost about $9.5 million in total, according to ZachXBT. Ledger states it never asks for the recovery phrase.

  6. Breach at e-commerce partner Global-e exposes Ledger.com customers' order data

    MediumCustomer data breachNot applicable

    Names, contact details, postal addresses and order details of an undisclosed number of Ledger.com customers who bought through Global-e were exposed, raising the risk of targeted phishing. Ledger states its systems, devices and customers' crypto assets were not affected.

2025

2023

  1. Ledger Connect Kit npm supply-chain attack

    HighSupply chainReported losses: $484K–$600KFixed

    Users of dApps that loaded the compromised library, with any wallet, could be drained by approving malicious transactions during a window of under two hours. Ledger devices and Ledger Live were not compromised, according to Ledger.

  2. Fake Ledger Live app in the Microsoft Store

    HighTargeted phishingReported losses: $768K–$770KNot applicable

    Windows users who installed the fake app from the Microsoft Store lost about $768,000–$770,000 in total, according to press reports citing ZachXBT.

2021

  1. Fake Ledger Nano X devices mailed to data breach victims

    HighTargeted phishingNot applicable

    Owners whose addresses were in the leaked database could receive a convincing counterfeit built to collect their recovery phrase. Anyone who followed the instructions would hand attackers control of their funds.

2020

  1. Ledger customer database breach

    MediumCustomer data breachNot applicable

    Names, postal addresses, phone numbers and email addresses of Ledger buyers became public, which identifies them as crypto holders. No device or seed compromise was reported, but the data was later used for phishing, including fake devices sent by mail.

  2. Ledger Nano X debug interface enabled supply-chain attacks (Kraken)

    HighHardware attackFixed

    A Nano X tampered with before first use could act as a keyboard on the owner's computer or hide transactions from the screen. Ledger states the Secure Element and user secrets were not affected and that firmware 1.2.4-2 fixes the issue.

  3. Ledger Bitcoin app SegWit fee overpayment vulnerability

    HighFirmware vulnerabilityFixed

    Users of the Ledger Bitcoin app and SegWit-capable forks before version 1.4.0 could lose funds to inflated fees if their computer's wallet software was compromised and they signed the same transaction twice. Ledger states the issue is fixed in Bitcoin app 1.4.0.

  4. Ledger Monero app spend key extraction (CVE-2020-6861)

    HighFirmware vulnerabilityFixed

    Monero holders using Ledger Monero app versions before 1.5.1 with a malicious or compromised Monero client could have their spend key extracted without any sign on the device. Ledger states the issue is fixed in Monero app 1.5.1.

2018

  1. wallet.fail at 35C3: Ledger Nano S MCU firmware and Ledger Blue PIN side channel

    HighHardware attackMitigated

    An attacker with physical access to a Nano S, combined with malware on the owner's computer, or one positioned within close radio range of a Ledger Blue during PIN entry, could undermine the device's protections in lab conditions. Ledger states the findings showed no practical vulnerability and that no seed or PIN was extracted from a stolen device.

  2. Ledger Nano S MCU firmware verification bypass

    HighFirmware vulnerabilityFixed

    An attacker who handled a Nano S on firmware 1.3.1 or earlier, before delivery or after setup, could install firmware that controlled or captured the recovery seed. Devices on firmware 1.4.1 are not affected, according to Ledger.

More entries do not mean a less secure brand: widely sold devices draw more published research and more targeted attacks, and some vendors disclose more than others.

Cite the tracker

WalletInsights. Hardware wallet security incident tracker. Last checked November 4, 2026. https://walletinsights.io/en/security-incidents/ledger/

Corrections and right of reply

Vendors, researchers and readers can send corrections or statements to security@walletinsights.io. We check them against the sources, update the entry and record the change in its log.