The Amazon listing that looked official

February 2025. A holder in Denver searches "Trezor Safe 3" on Amazon. The top result is "Sold by TrezorOfficialStore, Ships from Amazon." Price is full MSRP. He buys it. The device arrives in shrink-wrapped Trezor packaging. During setup, Trezor Suite reports that the device authenticity check did not pass; he assumes it is a connection glitch, clicks past it, generates a new seed, funds it with $63,000 in BTC. Six weeks later, slow-drip withdrawals start — small amounts, evenly spaced, to addresses he doesn't recognize. Total loss over 30 days: $58,000.

How supply-chain attacks differ from secondhand traps

A supply-chain attack tampers with the device's firmware or its random number generator before the user sees it. The device generates "fresh" seed phrases on first boot — but the seed-generation process has been backdoored. The seed is in a deterministic range the operator can brute-force, or the device transmits the seed via a side channel during first connection to a computer.

This attack is rare, but counterfeit and tampered hardware wallets sold outside official channels have turned up more than once — devices that look right from the outside but run altered firmware or hardware. That is exactly why current devices ship with an authenticity check, and why the check only helps if you take its warning seriously.

The four-layer defense

  • Buy from the manufacturer's own website. Period. Marketplace listings, even ones that say "Sold by Trezor," can be gamed. The "Sold by" name can be a registered seller name that mimics the manufacturer. The shipping warehouse is Amazon's, but the goods came from a third party.
  • Treat every authenticity or firmware warning as a stop sign. Trezor Safe models run a device authenticity check in Trezor Suite, and the device itself warns on screen if it is running firmware Trezor did not sign. If you see either warning on a new device, do not generate a seed and do not fund it — contact Trezor support through trezor.io and return the device.
  • Run a "dust test" before funding seriously. Send a small amount, then check the address on a block explorer over the next few days. Unexpected outgoing transactions mean you have lost $50, not $50,000. Know its limit, though: a patient operator like the one in this case waits until the balance is worth taking, so a clean test does not clear a device that failed its authenticity check.
  • Use a passphrase on top of the seed phrase. A BIP-39 passphrase (the "25th word") is something only you know, kept separately from the seed card. If the seed alone leaks, the passphrase keeps the derived addresses out of reach. It cannot save you from firmware that is compromised itself, because you type the passphrase into that same device — which is why rule one comes first.

The economic frame

A hardware wallet costs $80–250. The portfolio it secures might be $50K–$5M. Buy through a marketplace for convenience or a small discount, and you expose yourself to a class of attacks that ordinary users cannot spot by looking at the device. The risk-adjusted price of buying from the manufacturer is the cheapest decision in the entire custody workflow.