Cracking metamask hash

[dbgdbg]

Works like a charm, thank you big time. Will try to compile my own version aswell, if any problems appear i shall return to this post.

[cyclone]

You're welcome, and glad you got it figured out.

[chpost]

@cyclone said in Cracking metamask hash:

Keep in mind that hashcat v7.x recently added support for their own metamask wallet hash with dynamic iterations which is not compatible with the widely used 26620 kernel which I released back in March, 2024.

I guess, it is compatible, but hash string should be changed from

$metamask$600000$...$...$...

to

$metamask$rounds=600000$...$...$...

[cyclone]

@chpost It's not compatible as is, but yes, if you reparse the hash like your example, it will work.

[Silver0666]

Hello all members and @cyclone, Happy New Year. Greeting.
Regarding the metamask_decryptor, I have some ideas to upgrade it. I tried to use it to crack my old wallet.
At first, I used hashcat but 'Token Length Exception' error was occupied so I tried to use your decryptor.
But its speed is a bit slow and it's because yours use only CPU, not GPU. If you use CUDA, it would be better to speed up.
Also, we can add mask options like hashcat. Sorry for my suggestions but I really appreciate your tools.
Please let me know if you have some solutions for my sugesttions.
Thanks

[cyclone]

It is better to use hashcat to recover the wallet password, then use metamask_decryptor to recover the seed phrase. If you're having issues with getting hashcat to work, make sure to use metamask_extractor to properly extract the hash. Several users have run into issues getting hashcat and metamask hashes to work on Windows, so trying yours with hashcat on linux is worth a shot. I have hashcat with my custom 26620 metamask kernel hosted on github which is compatible with the metamask_extractor.
https://github.com/cyclone-github/hashcat

[Silver0666]

Hi @cyclone, Long time no see. How are you today?
Regarding the Metamask Vault Decryptor, I can see 5430.89 h/s speed in the example screen. But when I test it on my side, I can see only about 82 h/s speed.

You can see my PC's spec in the uploaded screen. which device and OS did you use to test it on your side?

[cyclone]

@Silver0666
I develop and test on Debian linux. Rig specs are listed here:
https://github.com/cyclone-github/hashgen-testing/tree/main/benchmarks

The speed difference you're seeing is likely due to the Metamask version of your wallet. The older 10k iteration pbkdf2 are much faster to run than the newer 600k iteration pbkdf2 vaults.

From the GitHub README:
https://github.com/cyclone-github/metamask_pwn

Example vaults supported:
* Old vault format: {"data": "","iv": "","salt": ""}
* New vault format: {"data": "","iv": "","keyMetadata": {"algorithm": "PBKDF2","params": {"iterations": }},"salt": ""}

For greater speed, you should use my hashcat_26620_kernel on the newer Metamask vaults.
https://github.com/cyclone-github/hashcat_26620_kernel

[Silver0666]

Okay, make sense. it sounds like you used iteration=10000 version in your test. All right!
As you know, it would be faster if I use hashcat. But when I try to use it, I can see "Token length is overflow" error. It seems like my wallet's salt's length is too large. Do you have any insight to resolve this issue?

[cyclone]

@Silver0666
I've run into this before as well. You can either modify the hashcat kernel to allow longer tokens, or use hashcat's metamask2hashcat.py to generate a "short" -m 26610 hash.

https://github.com/hashcat/hashcat/blob/master/tools/metamask2hashcat.py