ForgotWalletPassword.com

Format guide · legacy wallets · MultiBit

MultiBit Classic is one of the fastest wallet formats to crack.

MultiBit was one of the most popular Bitcoin wallets of the early 2010s, and its files still sit on old hard drives everywhere. There are two very different products: Classic, with an encryption that’s essentially theatre, and HD, with genuinely strong scrypt. Knowing which one you have changes everything.

By Robbert Bink · ~6 min read · Published 6 August 2026 · Last reviewed: 14 August 2026

Short answer

MultiBit Classic’s .key backup files are encrypted with just 3 MD5 iterations — exceptionally weak by modern standards, checked at up to ~1.8 million guesses per second on one CPU. The main .wallet file uses scrypt and is roughly a thousand times slower; MultiBit HD uses scrypt too. A Classic .key backup is one of the most recoverable cases that exist.

Which wallets use this format?

The MultiBit wallet file exists in two editions, and only MultiBit software produces them:

  • MultiBit Classic*.key key backups use a triple-MD5 scheme (exceptionally fast to crack); the main *.wallet file uses scrypt like HD
  • MultiBit HD — a mbhd.wallet.aes scrypt-based keystore with a 12–24-word backup phrase (a much harder, different story)

Both are discontinued; support and maintenance ended on 26 July 2017. The files still sit on old hard drives everywhere, which is exactly why this guide exists.

Classic vs HD: two completely different wallets

MultiBit ClassicMultiBit HD
File*.wallet + *.key backups — ~/.multibit / %APPDATA%\MultiBitmbhd.wallet.aes~/.multibit-hd / %APPDATA%\MultiBitHD
Key derivation.key backup: 3× MD5 · .wallet: scrypt N=16384, r=8, p=1scrypt N=16384, r=8, p=1
Measured speed~464,000 – 1,810,000 guesses/sec for the .key backup (CPU); ~510/sec for the .wallet file~123 – 510 guesses/sec (CPU)
DiscontinuedJuly 2017July 2017

Speeds are published btcrecover measurements (i7-10700K / Ryzen 9 9950X, 2026): btcrecover.readthedocs.io/Benchmarks. The gap between the .key backup and the scrypt-based files — roughly three to four orders of magnitude — is what a real key-derivation function buys you.

Which file do you have? The three MultiBit formats

MultiBit left behind three different file types, and they are not interchangeable. The file name and location tell you which one you have:

*.wallet — MultiBit Classic, the main wallet file
Files like default.wallet or mywallet.wallet in ~/.multibit (macOS/Linux) or %APPDATA%\MultiBit (Windows). Encrypted with the bitcoinj scrypt scheme — far slower per guess than the .key backup. If you have a .key backup for this wallet, use it.
*.key — MultiBit Classic, private-key backup
Timestamped files like walletname-20140407200743.key in the key-backup folder next to your wallet. Encrypted with the 3×MD5 scheme — exceptionally fast to test. This is the file btcrecover works with most reliably — if you have one, use it.
mbhd.wallet.aes — MultiBit HD
The encrypted HD wallet, stored per wallet in ~/.multibit-hd/<wallet-id> or %APPDATA%\MultiBitHD\<wallet-id>. Protected by scrypt (N=16384, r=8, p=1) — a completely different, much harder recovery story. The 12–24-word backup phrase restores it without the password.

You do not need the MultiBit app to read any of these — they are plain data files. btcrecover reads the Classic .key backups and the HD .wallet.aes directly, and can also run against the Classic .wallet file itself — but the .key backup is strongly preferred because it is much faster. hashcat mode 27700 or the multibit2john extractor are alternative routes for the .wallet. This page covers the password angle; for the complete MultiBit walkthrough — version identification, HD seed recovery, export and migration — see the dedicated guide at multibit.online.

What the 3×MD5 .key backup means for you

MD5 is not designed for password storage; hashing it three times changes almost nothing. The practical translation:

  • a 6-character lowercase password: found in minutes, even random;
  • an 8-character letters+digits password: hours to days;
  • a 10-character patterned password (a word, a date, your habits): very reachable with a memory-driven token list;
  • a random 12+ character password: still hard — MD5 being fast doesn’t shrink the search space, it just makes every guess cheap.

If this is your situation, the expectation is unusually good. The 68-place search checklist may even find the password before any cracking starts.

Getting the file out of a dead app

MultiBit’s software is abandoned and its websites are long gone, but the files are plain data — you don’t need the app to recover:

  1. 1
    Locate the .wallet, .key or mbhd.wallet.aes file (paths above; the OS-wide methods in how to find your wallet file help).
  2. 2
    Copy it somewhere safe — never work on the original. (The copy rules.)
  3. 3
    Prefer the key-backup files if you have them (MultiBit Classic): btcrecover reads the key-backup folder (e.g. %appdata%\MultiBit\multibit-data\key-backup) more reliably than the main .wallet file. For MultiBit HD, point it at mbhd.wallet.aes.
  4. 4
    Feed the copy to btcrecover — the .key backup is its native MultiBit Classic input (btcrecover can also read the .wallet file directly, but .key is far faster; hashcat mode 27700 or the JtR multibit format are alternatives) — with token lists built from your memory.
  5. 5
    On success, the private keys are yours again — sweep them into a modern wallet you control.

The full tool workflow — token lists, masks, and the all-important safe usage rules — is on offline recovery tools.

HD: a note

If your wallet is MultiBit HD (scrypt), the easy wins are gone. The same feasibility framework as every other scrypt wallet applies: an old patterned password with good memory clues is still recoverable; a random password is not, for anyone. Run the calculator before you decide how far to go.

Next step

Identify which MultiBit you have (file location is usually enough — see the three formats above), secure the file, then either work the checklist or go straight to the tools — btcrecover handles both Classic and HD.

Frequently asked questions

How fast is MultiBit Classic to crack?

Extremely fast for the .key backup: the 3×MD5 derivation is checked around a million times per second on one CPU, which is why Classic is one of the fastest common encrypted wallet formats to test. The .wallet and HD formats use scrypt and are far slower.

Which file do I need for a MultiBit recovery?

The key-backup folder’s .key file for Classic (the fast path), the .wallet file for Classic, or the mbhd.wallet.aes file for MultiBit HD. The three formats use completely different encryption, so identify the file before you start.

Which tools read MultiBit files?

The Classic .key backup is btcrecover’s fastest direct/data-extract path; btcrecover can also read the Classic .wallet file directly, though it is much slower — hashcat 27700 or the John/multibit2john route are alternatives that require extraction first; MultiBit HD (mbhd.wallet.aes) uses a btcrecover extract/direct workflow depending on setup, with hashcat 22700 also applying.

Sources & references

  1. btcrecover — performance benchmarks
  2. btcrecover — password recovery quick start (MultiBit Classic .key backups, HD mbhd.wallet.aes)

Cite this page

APA: Bink, R. (2026). MultiBit Classic is one of the fastest wallet formats to crack. ForgotWalletPassword.com. https://forgotwalletpassword.com/multibit-wallet-password-recovery

Markdown: [MultiBit Classic is one of the fastest wallet formats to crack.](https://forgotwalletpassword.com/multibit-wallet-password-recovery)

Missing something, or spot an error? Tell us — every correction is checked and applied.
Was this guide helpful?

Keep going — it’s all free

Not sure what you lost or what’s possible?

Take the quick diagnosis for a first verdict — it stops early when the answer is already clear — then work the search checklist. Everything here is informative, runs offline, and is free to use.