From Trezor Wiki
Revision as of 11:11, 4 July 2018 by Sipak (talk | contribs) (What if my computer that runs my bitcoin wallet is stolen?)
Jump to: navigation, search

Security threats[edit]

What happens if my Trezor gets stolen?[edit]

  • Can the thieves take all my coins?
  • Is there some way to recover my account once I get a new Trezor?

The short answers:

  • No. Each Trezor has a PIN code to prevent misuse in case of a physical theft.
  • Yes. See Recovery.

Just how easy (or hard) is it to get some bitcoins out of a stolen Trezor?

Brute forcing the Trezor PIN[edit]

Your Trezor is protected by a PIN code, which can be up to 9 digits between 1 and 9. There are 6561 possible 4 digit PINs for the Trezor. If you choose a good PIN, it will take hundreds of thousands of guesses to guess your PIN. Each time you enter a wrong PIN, the wait time increases by a power of 2. After the first few failures, you have to wait several seconds before you'll be able to try another PIN. Even just trying the top 20 PINs would take about 6 days(150 hours). Trying 30 PINs would take around 17 years. Trying 100 random PINs would take a VERY LONG time.

The number of PIN entry failures is stored in the Trezor's memory. This means that power cycling the Trezor won't magically make the wait time go to zero again. The best you can do by turning the Trezor on and off again is make the timer start over again.

Reflashing the Trezor with evil firmware[edit]

Official Trezor firmware is signed by the SatoshiLabs master key. Installing unofficial firmware on the Trezor is possible, but doing so will wipe the device storage and Trezor will show a warning every time it starts. Reprogramming the bootloader is impossible because all Trezors ship with their secure programming fuse blown.

Inspect the Trezors memory with an electron microscope[edit]

You might imagine yourself dissolving the Trezor CPU in acid, finding the reprogramming fuse, repairing it, and then loading evil firmware on the Trezor. I'm no science fiction author, but my guess is -- this might be possible. However, the Cortex M3 is a sensitive multilayer chip. The components inside are much smaller than those fake eBay amps. Chances are, all you'd end up doing is destroying the chip. Even if you succeeded in doing so, this will be a costly and time-consuming task. In the end, the bitcoins will be gone already because the original owner will have changed their recovery seed upon discovering that their Trezor was stolen.

Evil maid attack - replace the Trezor with a fake[edit]

It might be possible for an evil ninja, or your little brother, to steal your Trezor and replace it with a fake Trezor. If the fake Trezor was embedded with a wireless transmitter, then the fake Trezor could wirelessly transmit any PIN it received. The attacker would then have full access to your funds.

If you are concerned about such an attack, it is a good idea to sign the back of your Trezor with a permanent pen. Don't forget to check the signature before each use.

The Trezor's chassis is sealed using ultrasound. Opening the Trezor without destroying the case is nearly impossible.

What if my computer that runs my bitcoin wallet is stolen?[edit]

If your computer gets stolen, just plug your Trezor to another computer and you'll get your account balance and transaction history. Might your Trezor get lost as well, simply use your recovery seed to restore your wallet on a new Trezor device or a Trezor compatible wallet software, see Apps.

What happens if my recovery seed is stolen?[edit]

You need to keep your recovery seed safe from theft. If your recovery seed is stolen and you haven’t set a passphrase protection, then your bitcoins can be stolen as well. However, if you like, Trezor can protect against recovery seed theft with a passphrase, and therefore eliminate this risk.

What happens if the SatoshiLabs servers are hacked and the firmware signing key is stolen?[edit]

First off, this won't happen ;). The SatoshiLabs master key is kept very safe. However, you don't need to rely on the SatoshiLabs signature. You can verify the build yourself. Our hope is that a few trusted Trezor users will make a habit of verifying firmware checksums. If you are concerned about this, we suggest making a habit of checking our blog or social news channels such as Reddit before applying any updates. If there ever was a problem with the firmware not matching the source code, you can be sure someone will have written about it.

You don't need to worry about the firmware being updated by a computer virus. Your Trezor will ask you to manually confirm the update before anything is written to the Trezor's memory.

What happens if the SatoshiLabs shuts down?[edit]

There are no such plans because we love bitcoin, but even if we had to close down, there's nothing to worry about. You can use your Trezor together with other BIP32, BIP39 and BIP44 compatible wallets. Since our code is opensource, developers from around the world can maintain it and add new functionalities.

What if I run the Trezor recovery process on an infected computer?[edit]

During the Trezor recovery process you are asked to enter your recovery seed into the computer with the words in a random order. By default, the Trezor uses a 24-word recovery seed.

If your computer has a key-logger installed on it, then the randomly ordered words may be stolen. One might try to re-arrange these words until they found the correct word ordering. They can check the order of the words, by generating a bitcoin address using each ordering and checking if the address belongs to you.

There are 24! possible orderings of a 24-word seed. That is 620448401733239439360000 possible orderings.

Each 24 word Trezor recovery seed is verified with an 8 bit checksum. Using the checksum to eliminate invalid seeds, you can reduce the search space by a factor of 256. This gives us a search space of:

24! ÷ 256 = 2423626569270466560000

Going from Trezor recovery seed to public bitcoin address takes 2 × 2048 iterations of PBKDF2, which in turn uses SHA-512. All in all, going from a potential Trezor recovery seed to a bitcoin address, is slightly more difficult than running SHA-512 8096 times.

To summarize, in order to check all possible orderings in a 24-word seed, you need to run SHA-512:

24! ÷ 256 × 8096 = 19621680704813697269760000 times

The bitcoin network is capable of preforming 176 537 883 000 000 000 iterations of SHA-256 each second.

If we wave our hands a bit, we can claim that SHA-512 and SHA-256 are the same difficulty (which they aren't but let's pretend they are). Therefore, it should take somewhere around half of:

(24! ÷ 256 × 8096) ÷ 176 537 883 000 000 000 ÷ 60 ÷ 60 ÷ 24 ÷ 365 = 3.5 years

for the ENTIRE BITCOIN NETWORK to crack the seed. If you have that kind of hashing power, you'd make better money mining at Slush Pool than trying to steal bitcoins. :-) On a normal botnet cracking a Trezor seed would take millennia.

NoteThis does not apply to the Advanced Recovery method, during which you do not input the seed words on the computer. More information is available in the User Manual.

Why is the device not covered in epoxy?[edit]

There are three reasons why one should use epoxy:

  • First is to increase the durability of the device. We feel that Trezor is durable enough even without the epoxy.
  • Second, to obfuscate components you are using in your design. This is not needed as the design is open source.
  • Thirdly, to make access to the MCU harder. If you are highly motivated, epoxy will just slow you down, not stop you. Also, MCU has a disabled JTAG, so there is no need to block access to MCU pins.

Why didn’t you use Secure Element or Secure Chip?[edit]

We want to keep Trezor as open as possible (both firmware and hardware are completely open-source and available on our GitHub). If we used Secure Element, we would limit hobbyist and hackers in creating their own clones, because you cannot use Secure Element in your design unless you sign a non-disclosure agreement with the vendor. By using standard off-the-shelf components, we make that really easy. We are aware of Secure Element’s advantages, but we are trying to fix most disadvantages of generic MCU in the software (see below).

What’s up with the side channel attacks?[edit]

Side channel attacked described by Jochen Hoenicke were fixed by rewriting all crypto functions to use constant time. Jochen did almost all of the fixing and we’ve been collaborating ever since on various security and non-security related improvements. We love our community! Also, we ask PIN before every operation involving a private key (e.g. generating of the public key), so even if there was some side channel attack left, you would still need to know the PIN to trigger it.

How about MCU glitching?[edit]

We did our best to protect the MCU against glitching (e.g. when we check the PIN, we first increase the PIN failure count, write it to flash, verify that write was OK, then check whether the PIN was correct and if it was correct then we reset the PIN failure count). That way you cannot glitch the PIN increase write.

What if the RNG is flawed?[edit]

Trezor uses randomness from both its own internal Random Number Generator (RNG) and from the host computer. The device then combines this randomness by XOR-ing, making sure that even if the entropy supplied by one source is flawed, it will still remain truly random.

What doesn't Trezor protect against (yet)?[edit]


If you wish to make a payment to someone on the Internet, you need to know their bitcoin address. Unlike Trezor, computers are not necessarily secure and it is possible that the bitcoin address displayed on your screen has been maliciously modified.

To be safe, we recommend confirming the recipient's bitcoin address through a second channel, such as SMS, a phone call, or an in-person meeting.

When receiving funds, you can guarantee that you are providing safe receiving addresses by using the Show on Trezor feature. Using this feature you can easily check to see if the receiving address has not been changed on a potentially compromised computer.

Like Trezor? Get one here!