-
Notifications
You must be signed in to change notification settings - Fork 710
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blockchain.info not being cracked with correct password. #332
Comments
The code for btcrecover was last updated in 2017 |
Do you have any ideas how to solve this problem? What to research? It appears like most threads are 2+ years old on the topic |
No no idea, Actually Blockchain.com updated the version of their wallet and that's the reason btcrecover is not working. |
The hashes are different because they are different programs, they have made a hash to be used on itself. As for it not cracking, it may be because blockchain has changed its format. |
Same problem here. I tried lots of cracking for my wallet for which I really don't know the password with no luck and then tried to create a new account and try for a known main and second passwords - it doesn't work :( This is an empty wallet, it says version 3: Who would update the btcrecover to work with new blockchain wallets? I'll pay in bitcoin :) |
sorry but too late :P I found the problem and will create a merge request shortly |
the problem was related to this code |
pull request with the fix: #343 |
This has been merged and tested in my python 3 fork here https://github.com/3rdIteration/btcrecover/ |
I made a new wallet with the pw that I know works, and there is only 1 password and no mnemonic.
I installed PyCrypt with Python 2.7
I downloaded the wallet.aes.json file
I added the exact password to "token" and the "world_list" file, so i tried it with tokens and wordlists.
I tried with --utf8 and without
Ran the crack:
$ python btcrecover.py --wallet wallet.aes.json --tokenlist token --utf8
Starting btcrecover 0.17.10 on Python 2.7.16 64-bit, 21-bit unicodes, 64-bit ints
Wallet difficulty: 5,000 PBKDF2-SHA1 iterations
Using 4 worker threads
1 of 1 [##########################################################################################] 0:00:00,
Password search exhausted
Alternatively, I have extracted the hash from wallet.aes.json using john the ripper (blockchain2john.py) and btcrecover (extract-blockchain-main-data.py).
Interestingly the hashes are completely different, I am not sure if this is relevant information but I've tried JTR on the hash and that didn't produce any results (I probably did something wrong).
Any clues or ideas? Thanks in advance. Please let me know if you can crack this or have recently cracked a blockchain.info wallet. Thank you.
Password: Opera1.!
BTCrecover:
Yms6lkWKlsBkNyPGJEcDQf6ijZ/PaKHzlfA/kF9SP5FjYNaIEwAAi1f0Jw==
JTR: $blockchain$v2$5000$1040$9fcf68a1f395f03f905f523f916360d696458a96c0643723c624470341fea28dd5abf928bc726d72b7e56d71a1310df08681bd0f3a06f2526850f1bfa63f99bf8d4234807e0c44543c35e8605872bb4b9de8913e0a48ff941cb93048ac526b8d5fb8176b2c58300717d2dc86a25288cf8bd0b84f1de43df30ff080d15e6427e3076c5429dd529d9da878d5fe09bbfd44b451c1a573fe7173f6b823423788efe42206b2c84a314aed1eaa2645a1b582d0d81a1327fb62753a4a31e95925d575d59188ff396e5c6942512372ef5b456875ed414a398f1dee31b8b3db0a5ed10720c4076fd97a4b02bdbd021898d32bcad1c2d74061e4e4c2743e71829cab3acaf1a9d1e2059f4ff6e34cb12c8bc90957d73fb8e6809e0563415c7ce129b39334d4489021f34751871acbab9731e88405569d209dc1e54edd8f4f3a196088c22cf041b26119b736c578612947e8439a3465fcb93e4f07ac90cf9e8b0cb02aaeafb0bcddbd75944214733c880ef7598116681c2648e0dc08998b17b968dcca936690c63d78deea74456a6f4ab2d8a82123fdb1267d64559632b3da031f470de6cba34cfbd5e5cba3a4c01ccecb754f038b02bde88c29aacb9bb10023233fac87e0f5c8b78e1fc2bf462ee1974637e6c01a4cbaac1c4d4493ed0eefa5c2d0644f4839006720b3352bcc99257dd30e5bb2013a4a882936aeac51e4568e0071c036cbc0abe67301254c8b4bc4931b9573911d85ffe84907e3869e66ee39408ccd2b7ee8a168d78f6eb9d6c73105d9633c3a5cd451294cd091215a1dc747531e55dfb8c546438c46894bd5fa188b2434948420c31aeb72d9e6ab38a42ccca968dcad8e0592762f354dc305efb49651ceeed3bc19c5c17d2941ac0e1963f843267e399e64d0d7157b42931b0655a7a03af58876ee5d2a6bbaf31c7f9dc7d77b3f28b720933f263663af3b76276ed21022572c09955ceaa1aaaf228cdf8dd26a21537d685f24fc17839b14ed4d540308ac21645e6b868e556c7c5d99d28e7151d780f6b901df7d70c6cf173e0463d66f539119eecee56a13a80bd5a45b2ef38f3874c27372b0a25edd0ed3445e604586c6b3b16c9469f8b8f476d9ea3c2caf23cb3cd6a2f06413a1ba37de64eb58c6d1e58c12bc1bf4696888188c5a23ae773098569f8fd36a08a682ed52433a5a8ce46cb3d1a3205db4e9b32885e7fb9bdf4c0b3456deeb9be155ac400eee6e1cf6652561fdbbc9ebacdd749f9965158c135054fe4dae0d70d3bf201382edfffba6ef76780fee4d96d1608b282f5e779bd02915c830f01638793ca84d0856ab8113442efa0da6d17d4be503d3f83e1bd9131352154e3f43a35b28075308ddae48cbee9949e8b94cefa8eb51d5a2c35615156b6fd4a44c10bddb1dbc452870f4f8f475e11c301297afb3796728626c6aef8cf7c8de3f04025e4fba58807a319048d18c3b14941027
The text was updated successfully, but these errors were encountered: