<p>I'm not sure on the specifics of this particular model, but usually the way these work is the encryption key is stored on a hardware security module, which is a physical chip that performs the encryption and decryption of the data given the right password.</p>
<p>To my knowledge you cannot make a copy of this physical chip, and once your attempts at entering the password run out, the chip will permanently wipe its copy of the encryption key. This chip is the thing that is checking your password, so it's this chip you would have to somehow duplicate.</p>
<p>With a lot of effort, you could probably desolder the flash memory chips and attempt to make a copy of the encrypted data itself. However, this encrypted data is generally protected with a 256-bit AES key (with has nothing to do with your password), of which the only copy was on the encryption chip, which the chip wiped when your password attempts ran out. So, this would be pointless.</p>

CC BY-SA 4.0
2021-01-24T17:24:45.183Z
2021-01-24T17:24:45.183Z
ieatpizza
<p>A <a href="https://www.nytimes.com/2021/01/12/technology/bitcoin-passwords-wallets-fortunes.html" rel="nofollow noreferrer">NY Times article</a> recently ran a story of Stefan Thomas who has $220 million worth of Bitcoin locked up in an encrypted hard drive:</p>
<blockquote>
<p>Stefan Thomas, a German-born programmer living in San Francisco, has
two guesses left to figure out a password that is worth, as of this
week, about $220 million.</p>
<p>The password will let him unlock a small hard drive, known as an
IronKey, which contains the private keys to a digital wallet that
holds 7,002 Bitcoin.</p>
</blockquote>
<p>I am familiar <a href="https://bitcoin.stackexchange.com/questions/3313/are-there-bitcoin-password-crackers-i-can-use-to-recover-forgotten-passwords">with this discussion</a> on SE which analyzes possible vectors to retrieve the actual PK using brute force. However, in this specific case we are trying to retrieve the password, not of the actual Bitcoin wallet but of the hard drive. Once the password to the hard drive is found, the PK would be known automatically. The main issue is that the hard drive will self destruct after 10 failed password attempts (8 attempts have been tried so far in Stefan Thomas's case).</p>
<p>What possible vectors are available to retrieve Bitcoin in this case? My first thought was to copy the contents of the hard drive to many different drives and try to brute force each copy separately. This way when one hard drive self destructs you can always continue brute forcing on the other. Obviously, this won't be cheap but it might be worthwhile depending on how much Bitcoin is at stake. However, there might be something specifically about IronKey that prevents copying?</p>
<p>Is copying hard drive an effective/feasible strategy? If not, what other possible vectors should one consider to tackle this problem?</p>
<p>Thanks</p>

CC BY-SA 4.0
2021-01-25T02:58:08.130Z
This isn't a hard drive; it's more something like a USB stick, but one that was specifically designed to be secure.
Pieter Wuille
<bitcoin-core><security><private-key><wallet-recovery>
Recover $220 Million Worth of Bitcoin Locked in a Self Destructing Hard Drive
David Lynch
# Recover $220 Million Worth of Bitcoin Locked in a Self Destructing Hard Drive

(Asked by: username_0 on 2021-01-24)

A [NY Times article](https://www.nytimes.com/2021/01/12/technology/bitcoin-passwords-wallets-fortunes.html) recently ran a story of Stefan Thomas who has $220 million worth of Bitcoin locked up in an encrypted hard drive:

> Stefan Thomas, a German-born programmer living in San Francisco, has
> two guesses left to figure out a password that is worth, as of this
> week, about $220 million.
>
> The password will let him unlock a small hard drive, known as an
> IronKey, which contains the private keys to a digital wallet that
> holds 7,002 Bitcoin.

I am familiar [with this discussion](https://bitcoin.stackexchange.com/questions/3313/are-there-bitcoin-password-crackers-i-can-use-to-recover-forgotten-passwords) on SE which analyzes possible vectors to retrieve the actual PK using brute force. However, in this specific case we are trying to retrieve the password, not of the actual Bitcoin wallet but of the hard drive. Once the password to the hard drive is found, the PK would be known automatically. The main issue is that the hard drive will self destruct after 10 failed password attempts (8 attempts have been tried so far in Stefan Thomas's case).

What possible vectors are available to retrieve Bitcoin in this case? My first thought was to copy the contents of the hard drive to many different drives and try to brute force each copy separately. This way when one hard drive self destructs you can always continue brute forcing on the other. Obviously, this won't be cheap but it might be worthwhile depending on how much Bitcoin is at stake. However, there might be something specifically about IronKey that prevents copying?

Is copying hard drive an effective/feasible strategy? If not, what other possible vectors should one consider to tackle this problem?

Thanks

**Tags:** bitcoin-core, security, private-key, wallet-recovery

> **Comments:**
> **username_1**: This isn't a hard drive; it's more something like a USB stick, but one that was specifically designed to be secure.  

---

## 1 answers

### Answer by username_2 on 2021-01-24. Score: 1

I'm not sure on the specifics of this particular model, but usually the way these work is the encryption key is stored on a hardware security module, which is a physical chip that performs the encryption and decryption of the data given the right password.

To my knowledge you cannot make a copy of this physical chip, and once your attempts at entering the password run out, the chip will permanently wipe its copy of the encryption key. This chip is the thing that is checking your password, so it's this chip you would have to somehow duplicate.

With a lot of effort, you could probably desolder the flash memory chips and attempt to make a copy of the encrypted data itself. However, this encrypted data is generally protected with a 256-bit AES key (with has nothing to do with your password), of which the only copy was on the encryption chip, which the chip wiped when your password attempts ran out. So, this would be pointless.


---

