Guide

Hardware wallets: Understanding the risks of self-custody

Hardware wallets reduce key exposure, but seed generation, backups and transaction checks still matter. Learn the limits and how to read a security advisory.

By Bradley Hughes6 min readUpdated Oct 22, 2026

In this guide · 7 sections
  1. What a hardware wallet actually does
  2. What does a seed backup protect?
  3. The gap that a firmware bug exposed
  4. What this changes for a self-custody checklist
  5. Reducing single points of failure further
  6. Which check should you make next?
  7. Reader questions

A hardware wallet reduces the exposure of private keys to a connected computer, but it does not remove every way to lose crypto. The remaining risks include an unsafe seed, a deceptive transaction, a compromised backup and mistakes during recovery. Understanding those boundaries helps you choose the right check before moving funds.

Correction, October 22, 2026: This guide previously described the Coldcard incident as a deterministic software fallback, overstated protection from remote attacks and assumed all affected users had followed the same backup process. Those claims have been corrected against the manufacturer’s published security record. The original publication date is preserved.

What a hardware wallet actually does

A hardware wallet generates and stores private keys on a device with no persistent internet connection, so the keys never touch a computer or phone that could be compromised remotely. Transactions are signed on the device itself and only the signed transaction, not the key, ever leaves it. That separation reduces exposure to malware on the connected computer. Holding keys yourself also changes your dependence on a custodian, but does not make the device, its firmware or every transaction safe.

Popular models in 2026 include Bitcoin-only, fully open-source devices built for air-gapped operation, alongside more broadly compatible devices that work across third-party wallet software.

The signing process itself is the part that makes this work in practice, and it is worth understanding rather than taking on faith. When a user wants to send bitcoin, the transaction details are constructed on a connected computer or phone, but the actual cryptographic signature that authorizes spending the funds is created entirely inside the hardware wallet, using the private key that never leaves the device.

The connected computer sends the unsigned transaction to the hardware wallet, the wallet displays the transaction details on its own screen for the user to verify, the user physically confirms it on the device, and only the resulting signature, mathematically tied to that specific transaction and useless for anything else, gets sent back out.

Even if the connected computer is fully compromised by malware, an attacker controlling it can see what the user is doing and potentially trick them into approving a malicious transaction, while direct key extraction from that computer is limited by the separation. This assumes the signing device and firmware work as intended; it is not a guarantee against every physical, firmware or supply chain attack.

What does a seed backup protect?

The private key itself is derived from a seed phrase, typically 12 or 24 words, generated when the device is first set up. Losing that phrase means losing access to the funds permanently if the device is also lost or destroyed; exposing it to anyone else means they can drain the wallet regardless of whether they ever touch the physical device.

The standard practice by 2026 is to stamp, engrave or etch the seed words into metal plates rather than writing them on paper, so the backup survives fire, flood and general corrosion. This part of the self-custody model is well understood and, when followed, genuinely effective against the risks it targets.

The gap that a firmware bug exposed

A backup preserves access to the seed you actually generated. It cannot repair a seed that was predictable at creation. A secure generation process needs sufficient unpredictable input and correct handling of that input. A sequence of ordinary looking recovery words does not let a user assess those properties by sight. Keep the distinction between seed quality and backup durability: they answer different failure modes.

According to the COLDCARD security status, a firmware defect weakened seed generation in the July 2026 incident. Attackers reconstructed affected keys offline; that is different from remotely taking over the devices. The manufacturer says fixed firmware corrects future generation but does not repair an already affected seed. Follow its model and firmware specific migration guidance, including its stated independent dice exception, rather than assuming that installing an update alone resolves exposure.

The security record does not establish that every reported loss had the same cause or that every affected user followed identical backup practices. This guide therefore does not repeat an aggregate loss estimate as a diagnosis of an individual wallet. If your device might be affected, establish the model, firmware history and seed generation method before selecting the manufacturer’s applicable instructions.

What this changes for a self-custody checklist

The practical lesson is not that self-custody is unsafe, but that it has a supply-chain dependency most holders never think to check: the firmware that generated the seed in the first place. A responsible self-custody practice includes comparing the device and firmware history with the manufacturer’s advisory and verifying updates before generating a new seed. For an existing seed, follow the advisory’s affected-seed criteria and its independent dice exception. Do not turn a firmware version alone into a diagnosis.

If the advisory identifies your seed as affected and no stated exception applies, follow its migration instructions; installing fixed firmware does not repair that seed. Self-custody reduces reliance on a custodian for keys. It does not remove the need to verify the tools doing the custody.

Reducing single points of failure further

For holdings large enough to justify the added complexity, multisignature setups address a related but distinct risk: what happens if one seed, one device, or one backup location is compromised, lost, or coerced out of its owner, regardless of how well that seed was generated. A multisig wallet requires signatures from more than one independent key to authorize a transaction, commonly configured so that any two of three separately stored keys, or three of five, are sufficient.

That structure means a single point of failure, a stolen device, a burgled safe, a firmware flaw affecting one specific hardware model, is no longer enough on its own to move funds, since an attacker would need to compromise multiple independent keys, ideally generated on different hardware from different manufacturers and stored in different physical locations, to succeed.

The tradeoff is operational complexity: more devices to maintain, more backups to manage, and a genuine risk of self-inflicted lockout if too many of the required keys become inaccessible at once.

That tradeoff is why multisig tends to make sense for larger holdings or shared custody arrangements rather than as a default recommendation for every bitcoin holder, but it is the most direct answer available to the exact class of problem the Coldcard incident illustrated: a single device, however carefully backed up, is still a single point of failure if something about it was flawed from the start.

Which check should you make next?

If you are choosing a custody approach, compare the responsibilities in our hot, cold and hardware wallet guide. If you already have a security warning for a particular model, read the manufacturer’s current advisory before importing a seed or moving funds. Keep recovery words out of websites, support chats and screenshots. A claimed support agent does not need them to identify a firmware version.

Reader questions

Does a firmware update make an affected seed safe?

Not necessarily. Correcting future seed generation does not change the keys of an existing wallet. Follow the actual advisory for your model and seed history.

Can a metal backup stop someone who already knows my seed?

No. Metal improves physical durability; it does not revoke someone else’s ability to derive the keys from the same recovery information.

Does a hardware wallet prove the transaction on its screen is sensible?

No. The device can help you inspect and authorize transaction details, but you still need to check the recipient and the action you are approving. A transaction you intentionally confirm can still send funds to the wrong person.

Evidence

Sources and further reading