When Cold Wallets Fail: Ledger, Coldcard, Supply-Chain Attacks & Bitcoin Entropy

Recent hardware-wallet security incidents reveal why protecting Bitcoin requires more than keeping private keys offline. Explore supply-chain attacks, seed-generation entropy, and practical ways to secure your Bitcoin.

Research reviewed: October 11, 2026

Your Bitcoin Can Be Offline—and Still Be at Risk

Hardware wallets are among the most widely recommended tools for protecting Bitcoin. By keeping private keys away from everyday internet-connected computers, they reduce exposure to many common attacks.

But a hardware wallet is not a guarantee of security.

In 2026, two major incidents demonstrated how different weaknesses can threaten self-custody. A Coldcard firmware vulnerability exposed Bitcoin wallets created with insufficient randomness. Separately, Ledger began investigating cryptocurrency thefts associated with devices purchased through a reseller, with evidence emerging of physical hardware tampering.

These events do not mean Bitcoin’s cryptography has been broken. They reveal something more important: the security of your Bitcoin depends on how your keys are created, how your devices reach you, and how you verify what those devices are doing.

This lesson explains what happened, why entropy matters, and what ordinary Bitcoin users can do to reduce their risk.

1. Coldcard: When Randomness Failed

On July 30, 2026, Coinkite, the manufacturer of Coldcard hardware wallets, disclosed a serious vulnerability affecting seed generation.

Bitcoin wallets rely on secret information generated from randomness. If that randomness is sufficiently unpredictable, an attacker cannot feasibly reproduce the resulting private keys.

The affected Coldcard firmware did not always use the intended hardware random-number generator.

According to Coinkite’s technical investigation, a build and linking error caused the seed-generation path to resolve to Yasmarang, a general-purpose pseudorandom number generator included in MicroPython.

Yasmarang was not designed to provide the cryptographic unpredictability required for Bitcoin wallet seeds.

The issue was not caused by attackers remotely accessing Coldcard devices. Instead, attackers could exploit the limited possibilities of vulnerable seeds and reconstruct private keys offline.

Reports at the time linked the vulnerability to the theft of approximately 594 BTC from hundreds of addresses. Those figures represent reported on-chain activity rather than a complete, independently established victim count.

Which Coldcard wallets were affected?

Coinkite’s updated advisory identifies affected seed-generation firmware across multiple Coldcard models, including Mk2, Mk3, Mk4, Mk5, and Q.

The risk depends on the model, firmware version, how the seed was originally created, and whether independent entropy or a strong BIP-39 passphrase was used.

Coinkite reports that affected Mk4, Mk5, and Q seeds had approximately 72 bits of entropy rather than the expected 128 bits. Some earlier models experienced more severe weaknesses.

Important: Updating firmware does not repair a vulnerable seed that already exists.

Anyone concerned about an affected Coldcard wallet should consult Coinkite’s current security status and migration instructions before making changes. Moving funds requires creating a genuinely new, secure seed—not simply restoring the old one on updated hardware.

Official source: https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/

2. Ledger: A Different Kind of Hardware-Wallet Threat

In October 2026, Ledger began investigating reports of cryptocurrency thefts involving customers who purchased hardware wallets from the Southeast Asian reseller CryptoBilis.

Ledger requested that the reseller suspend sales and shipments while the investigation continued.

Subsequent reporting described evidence of an unauthorized hardware implant in at least one affected device.

This represents a different security problem from the Coldcard entropy failure.

Instead of exploiting predictable seed generation in otherwise untampered firmware, a supply-chain attacker may modify a physical product before the customer receives it.

A compromised device could potentially expose information during setup, even when the owner believes their keys are being created offline.

Investigators have reported suspected losses exceeding $86 million across multiple cryptocurrencies. These estimates remain provisional and should not be interpreted as confirmed losses attributable to a single proven attack mechanism.

Ledger has not established that all Ledger devices, its general manufacturing systems, or wallets purchased directly from Ledger were compromised.

What is a supply-chain attack?

A supply-chain attack occurs when an adversary interferes with a product or service somewhere between its creation and its eventual use.

For hardware wallets, possible threats include:

  • A modified device sold as authentic.
  • Unauthorized electronic components inserted into the hardware.
  • Malicious firmware or software distributed through an untrusted channel.
  • Packaging, instructions, or QR codes designed to redirect customers to fraudulent setup procedures.

The key lesson is that a device’s security depends partly on its origin and integrity.

Buying from an official source, following the manufacturer’s authenticity checks, and avoiding unexpected setup instructions can reduce risk. However, no single authenticity check should be treated as an absolute guarantee against sophisticated physical tampering.

3. What Is Bitcoin Entropy?

Entropy is a way of describing uncertainty or unpredictability.

Imagine selecting a secret number from only ten possibilities. An attacker could try all ten.

Now imagine selecting a number from an enormous range of equally likely possibilities.

The more unpredictable possibilities there are, the harder it becomes to guess the secret.

Bitcoin wallets use this principle to create cryptographic keys.

A standard 12-word BIP-39 recovery phrase represents 128 bits of initial entropy. A standard 24-word phrase represents 256 bits.

That does not mean the words themselves magically create security. They encode underlying secret information, along with a checksum.

If the underlying secret was predictable when generated, a perfectly valid-looking recovery phrase can still be insecure.

Why reduced entropy matters

A 128-bit secret has 2¹²⁸ possible values.

A 72-bit secret has 2⁷² possible values.

The 128-bit search space is approximately 72 quadrillion times larger.

A 72-bit secret is not automatically easy to crack. Practical attacks depend on the exact weakness, available information, and computational resources. But the reduction represents a substantial loss of security margin.

The Coldcard incident illustrates why a wallet’s seed-generation process deserves the same scrutiny as its physical hardware.

4. Can Ordinary People Generate Their Own Randomness?

Yes. One accessible method uses ordinary physical dice.

A fair six-sided die produces approximately 2.585 bits of entropy per independent roll.

That means 50 independent rolls contain about 129 bits of theoretical entropy, while 99 rolls contain approximately 256 bits.

Open-source tools such as SeedSigner support generating Bitcoin recovery phrases using physical dice rolls.

This can reduce reliance on a device’s internal random-number generator, provided the process is implemented correctly and the dice results remain private.

However, generating secure Bitcoin keys involves more than rolling dice.

The conversion algorithm must be correct. The device or software processing the results must be trustworthy. The recovery phrase must remain secret, and the final wallet must be tested before meaningful funds are transferred.

Never enter a real Bitcoin recovery phrase or private dice sequence into an online entropy checker, chatbot, or ordinary internet-connected computer.

For classroom demonstrations, use disposable example seeds that will never control real Bitcoin.

5. Meet SeedSigner: Open-Source Bitcoin Security

SeedSigner is an open-source, air-gapped Bitcoin signing project designed around inexpensive, widely available computing components.

Its approach combines several ideas:

Air-gapped operation: Transaction information can be exchanged using QR codes instead of a direct network connection.

User-generated entropy: Physical dice rolls or other supported methods can contribute the randomness used to create a seed.

Open-source software: The project’s implementation can be examined, tested, and improved by independent researchers.

Accessible hardware: A basic SeedSigner can be assembled using compatible Raspberry Pi hardware, a screen, and a camera.

SeedSigner also introduces important trade-offs. Some configurations do not retain the seed after power is removed, making recovery backups and careful operational procedures essential.

Open-source hardware and software can support transparency, but building a device yourself does not automatically make it secure.

For beginners, the first goal should be understanding and testing—not immediately transferring savings to an unfamiliar wallet.

Interested in building your own Bitcoin signing device? Explore our Beginner’s Guide to Building a SeedSigner to learn how open-source hardware, offline signing, and QR-code transactions work together.

Official project: https://github.com/SeedSigner/seedsigner

6. Seven Practical Ways to Protect Your Bitcoin

  1. Know where your wallet came from. Prefer manufacturer-approved purchasing channels and follow current authenticity guidance.
  2. Check official security advisories. Review affected firmware versions and migration instructions, especially when an incident is announced.
  3. Understand how your recovery phrase was generated. Learn whether your wallet uses hardware randomness, independent user entropy, or both.
  4. Never share your recovery phrase. No legitimate support agent, wallet manufacturer, or website needs your seed words to investigate a problem.
  5. Verify transaction details on the signing device. Confirm the recipient address and amount rather than trusting only the connected computer.
  6. Test recovery with small amounts. Understand how to restore your wallet before relying on it to protect significant funds.
  7. Consider stronger custody arrangements as your needs grow. Passphrases, multisignature wallets, and independently sourced signing devices can reduce some risks, but also introduce additional complexity and recovery responsibilities.

Security is not about using the most complicated setup. It is about understanding the risks and maintaining a system you can operate and recover reliably.

7. Classroom Exercise: Understanding Randomness Without Risking Bitcoin

This activity requires only a six-sided die, paper, and a calculator.

Part A: Predictability

Ask students to choose a number between 1 and 6. Discuss how many guesses an attacker would need to cover every possibility.

Part B: Increasing uncertainty

Roll a die five times and record the sequence. Compare how many possible five-roll sequences exist: 6⁵, or 7,776.

Part C: Scaling up

Calculate how many possible sequences exist for 50 independent rolls: 6⁵⁰.

Discuss why physical randomness can provide a powerful source of cryptographic entropy when correctly collected and processed.

Part D: Security engineering

Ask students whether 50 dice rolls alone guarantee a secure wallet.

The answer is no. Secure software, trustworthy hardware, private handling, correct conversion, and reliable backups still matter.

This exercise demonstrates the difference between understanding a security principle and implementing a complete security system.

8. The Bigger Lesson: Self-Custody Means Verifying Trust

The Coldcard and Ledger incidents demonstrate different weaknesses.

One concerned the generation of cryptographic secrets.

The other raised concerns about the integrity of devices distributed to customers.

Both illustrate why hardware-wallet security must be evaluated as a complete process, not simply a product feature.

Bitcoin gives individuals the ability to control their own funds without depending on a bank. That freedom creates opportunities for better security, but it also requires informed decisions.

You do not need to become a programmer or cryptographer to begin.

Start by learning how recovery phrases work, understanding where your hardware comes from, practicing safe backups, and verifying the instructions you follow.

For readers who want to go further, open-source projects such as SeedSigner provide an opportunity to explore the technology directly.

At NodeAxe, our goal is to make Bitcoin security understandable, practical, and accessible—from first-time wallet owners to students building their own hardware.

Continue Learning with NodeAxe

This article is part of the NodeAxe Security & Self-Custody learning series.

Related lesson: What Is a Bitcoin UTXO? Understanding How Bitcoin Really Moves

Coming next: Understanding Bitcoin Entropy: Dice, Randomness & Seed Phrases

Future project: Build and Explore a SeedSigner — An Introduction to Air-Gapped Bitcoin Signing

Sources and Further Reading

Editorial note: This article summarizes publicly reported incidents as of October 11, 2026. Ongoing investigations may change the findings. Readers should consult official manufacturer advisories before taking security-sensitive actions. Educational content only; not individualized financial or security advice.