Skip to main content

Search...

Popular searches

Ledger Donjon bypasses Trezor Safe 3 supply-chain protections

TrezorHigh

Who is affected

An attacker with lab equipment could turn a Safe 3 into a device running malicious firmware that still passes authenticity checks, then sell it to a victim. Devices bought from official sources and the Safe 5 are not affected, according to Trezor.

What happened

On 12 March 2025 Ledger Donjon, the security team of Trezor’s competitor Ledger, published an evaluation of the Trezor Safe 3. According to Ledger, the researchers desoldered the device’s STM32-based microcontroller, used voltage glitching to lower its readout protection and read its flash memory. This let them extract a per-device secret and run modified firmware while the device still passed Trezor’s authenticity check. Ledger names biased seed entropy and manipulated signature nonces as the risks of such firmware.

Trezor’s security portal records the report as received on 12 November 2024. Trezor states that Donjon “successfully reused a previously known attack” to bypass some supply-chain countermeasures in the Safe 3, and that the Safe 5 is not affected because it uses a newer microcontroller. A Trezor spokesperson told Cointelegraph the researchers could not extract private keys or PINs, and Trezor said no user action is required. Asked whether a firmware update could fix it, Trezor answered “Unfortunately not”; neither company has explained how the findings were addressed.

The attack is a supply-chain scenario: it needs the device in hand and the chip removed from the board before the device reaches its owner.

What to do: buy only from Trezor or an official reseller.

SecurityFault Injection

Fault injection disturbs a chip's voltage, clock or electromagnetic environment so that it skips a security check or leaks data.

Read full definition
HardwareFirmware

Firmware is the software that runs on a hardware wallet itself: it generates keys, shows transaction details on the screen and signs.

Read full definition
SecurityEntropy

Entropy is the randomness used to generate secure cryptographic keys or seeds in blockchain and cryptocurrency systems.

Read full definition
TransactionNonce

A nonce is a sequential number in a blockchain transaction that ensures transactions from the same account process in order and prevents replay attacks.

Read full definition
BlockchainPrivate Key

A private key is the secret number that proves ownership of a crypto address and signs its transactions. Whoever has it controls the funds.

SecurityPIN Protection

PIN Protection is a security feature that requires a personal identification number (PIN) to access a cryptocurrency wallet or device, preventing unauthorized access.

Read full definition
HardwareFirmware Update

Firmware Update installs new low-level software on a hardware wallet to fix bugs, enhance security, or add features in cryptocurrency devices.

Read full definition

Sources

Independent reporting and research this entry was checked against.

  1. Trezor — Ledger Donjon's Trezor Safe 3 evaluation (security portal)
  2. Ledger — Why Secure Elements make a crucial difference to hardware wallet security (12 Mar 2025)
  3. The Block — Trezor discloses potential vulnerability in older Safe 3 wallets following research by rival Ledger (13 Mar 2025)
  4. Cointelegraph — Ledger helps competitor Trezor resolve security vulnerability (Mar 2025)
  5. ForkLog — Ledger identifies vulnerability in Trezor wallets (Mar 2025)

Learn more

Guides on protecting yourself against this type of incident (Hardware attack) and the glossary terms that describe it.

Cite this entry

WalletInsights. “Ledger Donjon bypasses Trezor Safe 3 supply-chain protections”. Hardware wallet security incident tracker. Last verified November 3, 2026. https://walletinsights.io/en/security-incidents/ledger-donjon-trezor-safe-3-glitching-2025/

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.