Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 3 min read

The secure chip passed. The device was still compromised

On 18 November, Ledger published an update on what it calls a hardware implant incident. Criminals tampered with genuine Ledger devices at the end of the distribution chain, before they reached buyers. Ledger has confirm

On 18 November, Ledger published an update on what it calls a hardware implant incident. Criminals tampered with genuine Ledger devices at the end of the distribution chain, before they reached buyers. Ledger has confirmed cases in Southeast Asia and Berlin and is investigating reports of two units in Dubai.

Two details from that update matter for anyone who builds or runs crypto infrastructure:

  • every confirmed device has the same physical modification, built to capture the recovery phrase during setup
  • Ledger reports no flaw in its secure chip or operating system, and no confirmed case involving a device bought on ledger.com

So the cryptography held. The device was still compromised.

What the implant did

According to researchers quoted by Bitcoin Magazine, opened units contained a small chip, an eSIM and a cellular module hidden inside the case. The implant read the 24-word phrase from the screen during setup and sent it out over a mobile network. The same report says the device's genuineness check cannot detect an added component while the original secure chip is intact.

That is the key engineering point. An attestation check answers one question: does this secure element hold a key signed by the manufacturer? It says nothing about what else sits on the board between the chip and the screen.

The trust boundary is wider than the chip

We usually draw the hardware wallet threat model around the secure element. This incident shows the boundary also includes:

  • the board and everything wired to the display
  • the distribution path from factory to buyer
  • the setup moment, when the secret is shown on screen

If you work on software supply chains, the pattern is familiar. A valid signature on a package proves who published it, not that every step before you was clean. That is why we built npm-install-audit to look at what a project will run before npm install, instead of trusting that the repository is fine because it looks official. Hardware needs the same habit: verify the path, not only the badge.

What builders and teams can do

Procurement is part of key management. For a team treasury, record where each signing device was bought, when, and through which channel. Buy from the manufacturer's own store. Treat a marketplace or a third-party reseller as an untrusted path.

Diversify signers. A 2 of 3 multisig with devices from different manufacturers, bought through separate channels, means one tampered device cannot move funds alone. This is the control that still works when an attestation check passes.

Do not migrate secrets off a doubted device. Ledger's guidance is direct: do not reuse the current recovery phrase or passphrase, because a tampered device can capture both. Create a brand new phrase on a new device and move funds to it.

Test before you trust. After setting up a new signer, send a small amount, check the receiving address on the device screen, then move the rest.

Monitor. Watch your treasury addresses for outgoing transactions you did not initiate. An implant that phones home turns into a drain later, and early alerts shorten the window.

For people who are not engineers

We turned this into a short open checklist in English and Spanish: where to buy, what to do with a device you doubt, how to move funds, and when multisig is worth it. Sources are linked and the text is CC BY 4.0, so feel free to reuse it:

If you bought a Ledger from a third party in Southeast Asia, in Berlin since January 2026, or in Dubai, Ledger asks you to contact Ledger Support. For a limited time it can arrange a physical inspection, including X-ray analysis.

Sources

What does your team use to track where its signing devices came from?

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.