Noitev's Lost Electrum Password: 1.8–1.9 BTC Recovered via Brute-Force Attack
ConstrainedWallet passphrase was unavailable — access required significant recovery effort.
On April 8, 2013, BitcoinTalk user Noitev reported losing access to an Electrum wallet holding approximately 1.8–1.9 BTC due to a forgotten password. The wallet configuration showed encryption was enabled ('use_encryption': True), yet Noitev claimed no recollection of ever setting a password, creating an internal contradiction typical of custody failures involving memory lapse or configuration drift.
The wallet address 15HC2A9VGFMRYEHy3e49pUTgmmcGR5sFco served as the public reference point. Noitev posted a bounty offering the funds exceeding 1 BTC to anyone capable of password recovery, and provided the wallet.dat file containing the encrypted seed data in base64 format—a high-risk disclosure that exposed the cryptographic material to potential attacks. Initial recovery steps failed: blank password attempts yielded no access, and the user confirmed they possessed no seed phrase backup.
Within 48 hours, on April 10, 2013, forum user 'stick' reported successful recovery via brute-force attack, describing the password as 'relatively easy' to crack. The attacker offered to return half the recovered funds to Noitev's original address upon proof of ownership. Electrum developer ThomasV confirmed coins had moved to address 3e255a71ee4665f55b3f9d8238a3f055d0637e81b076a7c8c72d18e5a2c95dda, documenting the transaction on the public blockchain. At April 2013 market rates (~$120 USD/BTC), the wallet represented roughly $216–$228 in fiat value.
The incident exposed a critical weakness in Electrum's threat model: AES encryption of the seed, while providing confidentiality, offered insufficient protection against weak user-selected passwords subjected to brute-force enumeration. The outcome represented partial recovery rather than total loss, conditional on the original owner's ability to prove address control and negotiate with an attacker.
| Stress condition | Passphrase unavailable |
| Custody system | Software wallet |
| Outcome | Constrained |
| Documentation | Present and interpretable |
| Year observed | 2013 |
| Country | unknown |
Why passphrases fail years after they are set
The failure mode documented consistently across observed cases is temporal: the passphrase is set with confidence, not used for an extended period, and then cannot be reproduced exactly when needed. A single character difference — different capitalization, an added space, a slightly different special character — produces a different wallet with a zero balance. The holder may be certain they remember the passphrase while being unable to produce the exact string that was originally set.
What makes this particularly difficult is that there is no signal at the moment of failure. A wrong passphrase does not produce an error message. It opens an empty wallet. The holder sees a zero balance and typically concludes the passphrase was wrong — but without knowing which part was wrong, or by how much.
Professional passphrase recovery services can attempt permutations when the holder has partial information: they remember the general structure, typical patterns they use for passwords, the approximate length, or that it included a specific word. Recovery from total non-recollection is not feasible.
The preventive action is to store a passphrase record — not with the seed phrase, which would defeat its security purpose, but in a separate secure location accessible to the holder and potentially a designated recovery person. A passphrase that exists only in memory has a time horizon: it will eventually be forgotten, and the timing is unpredictable.
Translate