Hardware wallets: what they protect against, and the ways people still lose funds

A hardware wallet is often described as making your crypto safe. It does something considerably more specific than that, and the gap between the specific thing and the general claim is where people lose money while believing they are protected.

The one problem it solves

A hardware wallet generates and stores your private key inside a dedicated device, and performs signing there. The key never exists in readable form on your computer or phone.

This defeats an entire category of attack. Malware that reads files, logs keystrokes, or scrapes memory on your computer cannot obtain a key that was never present on it. Even on a fully compromised machine, the attacker can see what you are doing but cannot sign a transaction without the device, and the device requires physical confirmation.

That is a genuinely large improvement, and it is the whole of what the hardware provides.

What it does not solve: approving the wrong thing

The device signs what you confirm. If you confirm a transaction that sends your funds to an attacker, the hardware wallet will faithfully produce a valid signature for it.

This is the dominant failure mode and it has nothing to do with key security. A convincing interface asks you to approve something, the screen shows a transaction you do not fully understand, and you press the button. The device did its job perfectly. Reading what is actually displayed on the device screen — not what the website says it is — is the only defence, and it is the step people skip because the website already told them what to expect.

What it does not solve: token approvals

On networks that support them, an approval grants a contract permission to move a token on your behalf, sometimes without limit and sometimes indefinitely. That permission persists after the transaction that granted it.

A hardware wallet will happily sign an unlimited approval, because signing is what it does. The funds can then be moved later without any further interaction from you or the device. Reviewing and revoking approvals is separate hygiene that hardware does not perform.

What it does not solve: the seed phrase

The device protects the key from your computer. It does not protect the seed phrase from you.

The phrase is generated during setup and written down by hand, and from that moment it is a plain-text copy of every key the device holds. Photographing it, typing it into anything, or storing it in a cloud service converts a hardware-protected wallet into a software-protected one without changing anything about the device. Any request to enter the phrase into a website or app is an attempt to do exactly this, and there is no legitimate version of that request. Our glossary entry explains why the phrase outranks any individual key.

What it does not solve: loss

Self-custody removes the custodian, which removes both the custodian’s risk and the custodian’s recovery process. A lost device with a safely stored phrase is an inconvenience. A lost device with a lost phrase is a permanent loss with no appeal, no support line and no mechanism of any kind.

This is a real trade and it should be made deliberately rather than absorbed as a side effect of following advice. Our comparison of who actually holds your crypto covers the custodial side of the same decision.

The accurate summary

A hardware wallet moves your private key out of reach of software on your computer. It does not verify that a transaction is one you meant to make, does not manage standing permissions you have granted, does not protect a phrase you have handled carelessly, and does not offer recovery if you lose both. It is a strong solution to one problem and no solution at all to the four most common ways people are actually parted from their funds.

The supply chain is part of the threat model

A hardware wallet is only trustworthy if it is the device the manufacturer built. Buying from a third-party marketplace or accepting an unsolicited device introduces the possibility of tampering, and the attack does not require sophistication: a device that arrives with a seed phrase already written in the box is a device whose keys someone else generated.

The rules that follow are short. Buy from the manufacturer directly. Generate the seed on the device yourself during setup rather than accepting one supplied with it. Verify the device using whatever attestation the manufacturer provides. A device that came with a phrase is compromised regardless of how convincing the packaging is.

Blind signing is the gap that remains

The device screen is your defence, and on complex transactions it may not be able to display what you are approving in meaningful terms. Some interactions present as an opaque payload the device shows as data rather than as a human-readable action.

Approving something you cannot read is the crypto equivalent of signing a blank contract. Where a device or interface can decode a transaction into plain terms, that capability is worth more than any specification on the box. Where it cannot, the honest response is to treat the interaction as high risk rather than to click through it — which is the opposite of what a well-designed prompt encourages.

What to do with the phrase, concretely

The advice usually stops at “keep it safe”, which is not actionable. Two properties actually matter and they pull against each other: the phrase must survive the loss of your home, and it must not be readable by anyone who finds it.

Redundancy addresses the first — more than one copy, in more than one physical place, on a medium that survives water and fire. Concealment addresses the second, and a copy stored where a burglar would look is not a backup, it is a delay. Splitting a phrase across locations is sometimes suggested and is easy to get wrong: a naive split can reduce the search space for an attacker holding one part while adding a new way for you to lose access permanently.

Whatever scheme you choose, test the recovery before it matters. A backup that has never been restored is a hypothesis, not a backup.