thanks Myleschetty and HCP!  I believe my .wallet files are OK because multibit itself, multibit_recovery and other scripts seem to behave well managing the files. I understand hashcat does not manage the wallet, just the key. I believe my private key extracted is correct. I was wondering if there is a way to tell if a key has been corrupted (any parity, checksum, redundancy, ...). I'll keep trying in any case, thanks!

thanks keychainX! It seems powerful. I'm just learning how to use it while the computer is doing some mask attacks. I'll probably combine both approaches.

A couple of questions regarding MultiBit Classic wallet: I see many people complaining about corrupted MultiBit wallets not opening with the correct password. I *believe* my wallet files are ok because they load into MultiBit Classic for Mac or, when I extract keys o see transactions with other scripts, they do not complain, but:

... is there a way to be sure the wallet files have not been corrupted?
... is there the possibility that hascat (or other recovery scripts) is not able to open the wallet even if they find the correct password?

Thank you!

Thanks HCP and NotATether! I'm writing some masks for the passwords patterns I usually use and this will be very helpful.
I must say I'm quite impressed with hashcat capabilities.

Thanks NotATether, I've already obtained the multibit hash and installed hashcat, this will help me a lot to reduce the number of iterations
 

Thanks HCP! I'll give it a try. I hope the password is one of the variations of the passwords I've used in the last 7 years...

Thanks! I didn't know this fork.

Thanks for the tips!

Currently using macOS big sur in a macbook pro: python btcrecover.py --wallet wallets.key --tokenlist tokens/tokens.txt  --no-dupchecks

I'll try in Linux and with a GPU as soon as I can. I'm not really confident to find it by brute force :-(
I'm still reviewing old notebooks and backups for a clue of the password or seed.

Hi all,

I have an old (2014) MultiBit Classic wallet that I've recovered from an old Windows computer, with some BTCs inside.

I do have all the wallet files, including backups, keys, rolling backups, wallet-unenc-backup, etc.  All the files seem OK.
But everything (including unenc-backup files) is encrypted with a password that I'm unable to find. I do not have any seed words either...

I've tried the "multibit_recovery" scripts to open the files and for all files it request the password, including for the unenc-backup cipher files.

My last hope was to use the "btcrecover" script using passwords lists and tokens but it didn't work in a reasonable time with my normal passwords.
Of course I can try to run it for the following 5 years in a GPU, maybe BTC in 2026 will be worth ...

Any other ideas?

Thanks!