BTCRecover says my blockchain.com password as wrong even though I know its right

[Hurley27]

Hi,

I have a problem with one wallet. I lost the blockchain.com password and a seed phrase was never created, but I have a fair idea of what the password could be. I used btcrecover to get the wallet.aes.json file and run a few token lists on it to no success. However, I recently tried another blockchain account of mine and I was able to access it with password. Out of curiosity, I ran btcrecover on the second wallet with token lists and password lists which should both have found the password - as I entered it in both lists - but btcrecover finished the search without finding the password. That makes me think that all of the searches I have run on the first wallet were wasted as btcrecover seems not to acknowledge the correct password even when it is in the lists. Is anyone familiar with this problem or have any recommendations? Both wallets were created in 2015/16. I would greatly appreciate any help on this. I would love to get btcrecover to register the right password on the second wallet so I know it works and can be confident in running the searches on the first wallet.

[1714491708]

1714491708

[1714491708]

1714491708

[1714491708]

1714491708

[1714491708]

1714491708

[1714491708]

1714491708

[Findingnemo]

While I checked, BTCrecoverer has similar kind of issue since 2019 and the developer is no more updating anything for the past 7 years this is likely to be persists.

Password search exhausted for known password

Try running listpass which still works.

If you still can't able to recover then try walletrecoveryservices their services which is the only legitimate recovering service that exists here.

[NotATether]

While I checked, BTCrecoverer has similar kind of issue since 2019 and the developer is no more updating anything for the past 7 years this is likely to be persists.

Password search exhausted for known password

Try running listpass which still works.

Your linked Github issue points to an old fork of btcrecover which is no longer updated. Op should try this fork: https://github.com/3rdIteration/btcrecover which has probably solved this old problem but I don't know for sure whether they did.

[Yamane_Keto]

I think you have set up your tokenlist wrongly, you need to read the details how-to-do-it https://github.com/3rdIteration/btcrecover/blob/master/docs/tokenlist_file.md

Set up the tokenlist well and try it with a simple list containing the required password and you will not get this error.

start will simple list like

Code:

Cairo
Beetlejuice beetlejuice Betelgeuse betelgeuse
correct_password

[nc50lc]

-snip- I would love to get btcrecover to register the right password on the second wallet so I know it works and can be confident in running the searches on the first wallet.

This would require you to post the info that you've fed to BTCRecover, not the actual characters but similar setup so we can tell if there's something wrong with the setup.

As for BTCRecover's integrity on bruteforcing Blockchain Wallet's Password:
Their test wallets, "blockchain-v0.0-wallet.aes.json" and "blockchain-v2.0-wallet.aes.json" both work with the password: "btcr-test-password";
Their test wallets are in this folder: github.com/3rdIteration/btcrecover/tree/master/btcrecover/test/test-wallets
I've used this easy tokenlist for this test:

Code:

%2a
^1^btcr-test-pass
wo

With this command:

Code:

btcrecover.py --wallet blockchain-v0.0-wallet.aes.json --token blockchain-wallet.token.txt

My not-old-version wallet.aes.json wallet works as well.

[Hurley27]

-snip- I would love to get btcrecover to register the right password on the second wallet so I know it works and can be confident in running the searches on the first wallet.

This would require you to post the info that you've fed to BTCRecover, not the actual characters but similar setup so we can tell if there's something wrong with the setup.

As for BTCRecover's integrity on bruteforcing Blockchain Wallet's Password:
Their test wallets, "blockchain-v0.0-wallet.aes.json" and "blockchain-v2.0-wallet.aes.json" both work with the password: "btcr-test-password";
Their test wallets are in this folder: github.com/3rdIteration/btcrecover/tree/master/btcrecover/test/test-wallets
I've used this easy tokenlist for this test:

Code:

%2a
^1^btcr-test-pass
wo

With this command:

Code:

btcrecover.py --wallet blockchain-v0.0-wallet.aes.json --token blockchain-wallet.token.txt

My not-old-version wallet.aes.json wallet works as well.

Hi, thanks for the response.
Ok what I will do is post the wallet file here as copied from browser. This makes up my wallet.aes.json file. When I contacted 3rditeration on GitHub he tells me the format is wrong but doesn't tell me what is the right format.

Code:

    "payload": "{\"payload\":\"RcAFIuhShojFSv1rY62LqXCbzEl0UerZM9drNhThXgxyXnn9r9preCtL3fdqiIpVw0UjBG1UXNcgUwobTB8ntmBb3AonPceOzGsROb2oxyNBUZbhO44TDACopN78mPIrfe8kp6plMQ4LOLfhbaRaq48v8rm5\/LUVM2uD6jcSuHLAoKF4ZnGqaZx66cUGeek9bqMYY8fPGYUVFhFPDYP5oyhjvLH+q2on45mBRI7s87TwQcUFuKLSOhF8K6YorfuhcWvLNCQ\/UORHLEKwWKsfWKLVKRuzDOgZpcv+F8e\/ZpPFFEUwPVrmS1tuCvi8AbvJIPNBLVAdmZq9HRlOjdP5XuVdTXMHsFcklrULm1LVX3a0fPe33\/e\/e3UY74+jndo2uDMRz8YEL7Wf1PUoR1pmMhHF1bmRUtwrcFozGwxsHHcnar7z92TiZHoJkBAb7fxt\/LMb4fyKJkocA\/IM23VRgLTIE0W\/UNhvK7IRwUHFtw8G25gOBIBD46J4aE8YXYJluvfCXLUjunDBIIvV6vp2FBT1ujkCznGdd017G0h8zki9r4CTFg14DSVb61Q1E2226PcEqFBrvBAPh6R\/KXoqPoI+mPPhsKtelQVwne1zdQGiOLBjC6lOHaSegvC2SmWo2m50tHv2SSa728LR3Up2Gm6revLHgHrdBRnrK8XjJh0\/n99AIOi\/TuYAOw15C5c88uWrdfIWl+1Xd1GFr55fJez6q\/zB7DJDk+RqU6vHOH+htZLLWXELgp93vGMCq3SVw6yUNzRSronmXJPmIbDxEZ97H6b6B+o9LWDVMgYHrHYjpmrIjjocAizTD6Rs1lJqEpSJO01R+PVeBL6v44PiPhnLuqozVSAslS\/jT90YprX9+rcSh7UPN7Bv2Lrh24+LRucvHwy5xGj7K7yxwofTItO0saxfYc8H1vtd1CJ7M\/3NEFZrxWaefyRRFuX0\/bFfyTwtDRih3N6AL6FPWXNSRzMrw+dBC+M7yBWsuhBUPJ2GBzPCQfFWzuJMWEVFTPTq+8Mqwg\/2qM6L+TQ8cuchRriQfDqT4eu3Vv9+l0VoYqDLXwMpl+zQI4JyFtwWGAF42jY0RnelcgViG264zlIjrb+gBuH9XNBV692xYa7CBcUbtA9dfQqOGTnRCk08yi+aMpt9HMaAtPlTpgOJdtAO29lvY0ZAGgFaU4gZm2oTbBSk8qr+bqUZcNDFVFioRuPdurXleI5K8QFUkG8XdQcvw6AT06QSuKP4aCw4+52+Qg7T0C7qrdMb4UIon7HbDJu7eG0S6Cb\/AfC2dttnzXL0oiTwQkJ\/8ke7lo58VbcJnXMb0ZMPvNJgm0GKPzOjiyG0l8VrIdv4bh5Ru0dnk4sGcrQpbaygHTKazMogvMexyZcf+lxYI1q7QzeGqqYL5e4v7WHy74DHP+T4KO7JR3n1gZE7q8\/Gp5mY4a3HT5ps+huBn3OHQq8W+pYIZn6aM\/vBJWLjkfIqp8Rj8sRWbcUxdls\/73qZL1Dd4eU2CQmOad4EyY1NoKP3zQ7h3YpB1Gqx2EUvGb6lmo5H61AoifaNbIfvi9h9OkFed1pNgyszOrvNPGcWk0wFQ4wUCcp2ifBuSIX1yNntOgaiJsDeNpd6ypze4PN89BX7js7nJi85Y7Tk9WZXpg4StBHz3HplfIfPL447TdYWfMnxVG6\/jKJ5zyPmdIdE4gRWo1bGV7mJ6hZO5cGVdunF05JTpVxBHPVcywpofVnUG\/qCflnDMft1yjMWNRwUjDqzjJrGZTwgfx1AT91gkwXZc\/hBREqa4IGhZH8\/HKp2xFqovqCFFfs4+Eoy\/C00J0gRZZ2OllP+q2G2N24wrbH9U5kSXyOnDqSKqoz3G+nn0fb44urM9Vi\/EKfNFZFZi1gsrgxjPfbRcalH3gamZnbuUiwxlmbLPWCD3M6u0EbG6AV\/0GYcTHnNdvaYhjyfvgouJ0OBaiNjpcgzCrSwZKcNzJeOHI6YwWiWE1siJS3VkBtja0RgF8pGbGF9UfCBYzpVAEZqEHg\/SZfkVMxrzUiIkyKSUB9md6A1k\/LrqxZBZxflWPtD7BcVsexjz7DDSyaUSsVcncorsy\/1mTkaFI8Xh7SgA8D4vWburao8WJCyJHJesxTZh9KmdusPG2UuNDw\/yul+gevMfFde75tErsGHKcCQWBIzGbHWaB0U2mQ2WKlgtu5xaLZwje9rBs\/oKGxv4Btc\/9ir4AwcbZrckhLpV82UDcBtlKfRIf1eqN0Y83RREnHiKN6wX\/RRW\/GrlEd8MoYxyIjy1L5Gvqw\/1SJWZa2vGbQjun6sQoidwoc\/\/MoDam3Uy1yZAPsyYFPkVH0itUEBV85KfQAoGmROJs7b+31O+imrAgBXOLttLp\/0A4bPWKcL2EPlUAjyo\/yhvxjVbso+ZoQKVdiu+JO2jauGtaLERlPJ0bR31vLbDC8uZsR1FyTJhTuP+MsttYpXsSLw4ObOfF4MYu6YTMOQo9IIPlYqpianDnKGhbIyYN9D9igfnAHvWySjSCJfrMxVAzODkOgbaVLsbbZylJUuigbRateuJkgNEfVrARiWghL8SFMUP8SSATpIeeg2sF5X48QGMUAnrKnih2BGD1Fgled4oxwMoVHIYUJuBsmgqDe\/ZNhpAHTV9M5Ov6Uhd\/FAhFn1Y04ngdwYpw4=\",\"pbkdf2_iterations\":5000,\"version\":4}"

Then these are the instructions I enter into terminal

Code:

python3 btcrecover.py --wallet wallet.aes.json  --tokenlist test.txt

Here are the contents (as example) of my tokenlist file

Code:

^1^Davi
stump steel 
Hull hull
42
. !

Results in this

Code:

2024-04-19 05:23:43 : Using 8 worker threads
711 of 711 [#####################################################################################################################################################################################] 0:00:00, 

All possible passwords (as specified in your tokenlist or passwordlist) have been checked and none are correct for this wallet. You could consider trying again with a different password list or expanded tokenlist...

However I know for certain that one of the combos from this list generates a password that is correct as ive used it to login the web wallet. For some reason it doesn't find a working password.

[Hurley27]

I think you have set up your tokenlist wrongly, you need to read the details how-to-do-it https://github.com/3rdIteration/btcrecover/blob/master/docs/tokenlist_file.md

Set up the tokenlist well and try it with a simple list containing the required password and you will not get this error.

start will simple list like

Code:

Cairo
Beetlejuice beetlejuice Betelgeuse betelgeuse
correct_password

Thanks for the response. I have also created a tokenlist where the only entry is the correct password - which I have tested multiple times to log into the wallet online and on my phone - and it still doesn't work.

[Hurley27]

While I checked, BTCrecoverer has similar kind of issue since 2019 and the developer is no more updating anything for the past 7 years this is likely to be persists.

Password search exhausted for known password

Try running listpass which still works.

Your linked Github issue points to an old fork of btcrecover which is no longer updated. Op should try this fork: https://github.com/3rdIteration/btcrecover which has probably solved this old problem but I don't know for sure whether they did.

Thanks. 3rditeration is the fork ive been using all along. I even left a post on the issues tab.

[Hurley27]

While I checked, BTCrecoverer has similar kind of issue since 2019 and the developer is no more updating anything for the past 7 years this is likely to be persists.

Password search exhausted for known password

Try running listpass which still works.

If you still can't able to recover then try walletrecoveryservices their services which is the only legitimate recovering service that exists here.

Thanks. There's a newer fork where a different developer maintains btcrecover.

[Yamane_Keto]

Then these are the instructions I enter into terminal

Code:

python3 btcrecover.py --wallet wallet.aes.json  --tokenlist test.txt

Is the path correct? Because the error message is supposed to be Password search exhausted

Code:

cd Downloads\btcrecover-master
python btcrecover.py --wallet wallet.aes.json --tokenlist test.txt 

At least now your problem is in the setup, you need to make sure that you have chosen the correct wallet file, the correct tokenlist file.

[Hurley27]

Then these are the instructions I enter into terminal

Code:

python3 btcrecover.py --wallet wallet.aes.json  --tokenlist test.txt

Is the path correct? Because the error message is supposed to be Password search exhausted

Code:

cd Downloads\btcrecover-master
python btcrecover.py --wallet wallet.aes.json --tokenlist test.txt 

At least now your problem is in the setup, you need to make sure that you have chosen the correct wallet file, the correct tokenlist file.

Yes the paths are correct. I'm on Mac so the full line with the path is as follows

Code:

hurley@Damiens-Air btcrecover-master % python3.12 btcrecover.py --wallet wallet.aes.json  --tokenlist test.txt 

both files are also correct. I have never seen password search exhausted. I think that comes up with gurnec's version of btcrecover - the older pre-2019 versions.

[nc50lc]

-snip-

Ok what I will do is post the wallet file here as copied from browser. This makes up my wallet.aes.json file. When I contacted 3rditeration on GitHub he tells me the format is wrong but doesn't tell me what is the right format.

Code:

    "payload": "{\"payload\":\"RcAFIu...4ngdwYpw4=\",\"pbkdf2_iterations\":5000,\"version\":4}"

Hmm, if I use this format with my own and test payloads, 3rdIteration's BTCRecover detects that it's not in the correct format.
It's reading the backslash in the quotation \" as part of the base64 string payload.
Are you sure that it's pointing to correct wallet.aes.json file during those attempts? Because you should see an error with that wallet file.
You can retry it with absolute path to the wallet.aes.json file to be sure.

Then, try to create two separate wallet.aes.json files with your payload, then bruteforce those instead:

• One containing just the base64 string payload (from RcAF... to ...Ypw4=) and take note of it as as "v0.0" format.
• And another in this format: {"pbkdf2_iterations":5000,"version":4,"payload":"RcAF......Ypw4="}.
  (Do not put quotation marks outside: "{contents}" should be {contents})

[Hurley27]

-snip-

Ok what I will do is post the wallet file here as copied from browser. This makes up my wallet.aes.json file. When I contacted 3rditeration on GitHub he tells me the format is wrong but doesn't tell me what is the right format.

Code:

    "payload": "{\"payload\":\"RcAFIu...4ngdwYpw4=\",\"pbkdf2_iterations\":5000,\"version\":4}"

Hmm, if I use this format with my own and test payloads, 3rdIteration's BTCRecover detects that it's not in the correct format.
It's reading the backslash in the quotation \" as part of the base64 string payload.
Are you sure that it's pointing to correct wallet.aes.json file during those attempts? Because you should see an error with that wallet file.
You can retry it with absolute path to the wallet.aes.json file to be sure.

Then, try to create two separate wallet.aes.json files with your payload, then bruteforce those instead:

• One containing just the base64 string payload (from RcAF... to ...Ypw4=) and take note of it as as "v0.0" format.
• And another in this format: {"pbkdf2_iterations":5000,"version":4,"payload":"RcAF......Ypw4="}.
  (Do not put quotation marks outside: "{contents}" should be {contents})

Thanks for the suggestions. I have tried the v0.0 format but btcrecover finds errors. The other format you suggested again ran but did not find the password. I am completely baffled by this as every time after it runs I go to the blockchain site and log into the wallet with the password. I just do not understand how it runs without finding the password. Is it an issue of it not finding certain characters in the password? My password contains a single fullstop but is otherwise alphanumeric. Does that have any impact? I'm legitimately baffled here.

[Hurley27]

I just used --listpass and it shows the correct password. I just don't know why it doesn't acknowledge it as being the right password for the wallet.

[nc50lc]

-snip-

I just do not understand how it runs without finding the password. Is it an issue of it not finding certain characters in the password? My password contains a single fullstop but is otherwise alphanumeric. Does that have any impact? I'm legitimately baffled here.

I just used --listpass and it shows the correct password. I just don't know why it doesn't acknowledge it as being the right password for the wallet.

You can try your current setup with BRCRecover's test wallets from: ...\btcrecover\test\test-wallets
Particularly, "blockchain-v4.0-wallet.aes.json" and/or other blockchain web wallet test wallets, the common password used in test wallets is: btcr-test-password
You may also check other passwords in "test_passwords.py" script.

If it somehow failed to find v4.0 Blockchain wallet's password despite being in the list (--listpass), then there's something wrong with your setup.
If it can find the password, then it may be your wallet or something else that you've missed.

I have tried the v0.0 format but btcrecover finds errors. -snip-

Is the '.json' file only contains the payload (including the "=" at the end of the string) without anything else?
Because it should be accepted even if the wallet isn't actually v0.0, but it'll show false-negative result despite having a good token file.

[Hurley27]

-snip-

I just do not understand how it runs without finding the password. Is it an issue of it not finding certain characters in the password? My password contains a single fullstop but is otherwise alphanumeric. Does that have any impact? I'm legitimately baffled here.

I just used --listpass and it shows the correct password. I just don't know why it doesn't acknowledge it as being the right password for the wallet.

You can try your current setup with BRCRecover's test wallets from: ...\btcrecover\test\test-wallets
Particularly, "blockchain-v4.0-wallet.aes.json" and/or other blockchain web wallet test wallets, the common password used in test wallets is: btcr-test-password
You may also check other passwords in "test_passwords.py" script.

If it somehow failed to find v4.0 Blockchain wallet's password despite being in the list (--listpass), then there's something wrong with your setup.
If it can find the password, then it may be your wallet or something else that you've missed.

I have tried the v0.0 format but btcrecover finds errors. -snip-

Is the '.json' file only contains the payload (including the "=" at the end of the string) without anything else?
Because it should be accepted even if the wallet isn't actually v0.0, but it'll show false-negative result despite having a good token file.

I tried the test wallet and password from the repo and it worked returning the password. Which baffles me even more. When I try the v0.0 format this is the return message I get

Code:

Starting btcrecover 1.13.0-Cryptoguide on Python 3.12.3 64-bit, 21-bit unicodes, 64-bit ints
Error: unrecognized wallet format; heuristic parser(s) reported:
    WalletPywallet: Unrecognized pywallet format (can't find mkey)
    WalletMultiBitHD: MultiBit HD wallet files must be named mbhd.wallet.aes
    WalletElectrum2: Expecting property name enclosed in double quotes: line 1 column 2 (char 1)
    WalletBlockchain: Incorrect padding

Do you mind if I send you the code or the json files as I have formatted them? Along with the password so you can check? I can also send the raw wallet data/wallet id/pass so you can see the login works but for some reason btcrecover doesn't recognise the password when run on the json file. I just am totally confused by this.

[nc50lc]

-snip-

Do you mind if I send you the code or the json files as I have formatted them? Along with the password so you can check? I can also send the raw wallet data/wallet id/pass so you can see the login works but for some reason btcrecover doesn't recognise the password when run on the json file. I just am totally confused by this.

I don't mind testing the "wallet.aes.json" + "token file" as long as the bitcoins are already swept to another wallet of yours;
Otherwise, please don't send me those if it's still funded.

As for the full login credentials, it would be more beneficial if you coordinate with BTCRecover's developer instead, for him to find a fix to that possible bug.

[Hurley27]

-snip-

Do you mind if I send you the code or the json files as I have formatted them? Along with the password so you can check? I can also send the raw wallet data/wallet id/pass so you can see the login works but for some reason btcrecover doesn't recognise the password when run on the json file. I just am totally confused by this.

I don't mind testing the "wallet.aes.json" + "token file" as long as the bitcoins are already swept to another wallet of yours;
Otherwise, please don't send me those if it's still funded.

As for the full login credentials, it would be more beneficial if you coordinate with BTCRecover's developer instead, for him to find a fix to that possible bug.

Thank you. He hasn't offered much in the way of assistance to be honest. Just keeps saying the format is wrong and everything he said to do, I have already done. I'll send both wallet files - the 4.0 and 0.0 along with the token list. I will also send the json as copied from network/response in the browser web dev so maybe you can see something in the payload that I can't. I really appreciate this. And no worries all wallets have been defunded other than the one I'm trying to recover.

[nc50lc]

-snip- I will also send the json as copied from network/response in the browser web dev so maybe you can see something in the payload that I can't. I really appreciate this. And no worries all wallets have been defunded other than the one I'm trying to recover.

I didn't expected that it would be this fast but your "full json script" with the exact token file contents (copy-paste) perfectly worked in my setup.

Command:

Code:

btcrecover.py --wallet hurley27-wallet.aes.full.json --token hurley27-token.txt --dsw

Command line result:

Code:

Starting btcrecover 1.12.0-Cryptoguide on Python 3.10.2 64-bit, 21-bit unicodes, 64-bit ints
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*                     Note for Blockchain.com Wallets...                *
*                                                                       *
*   Writing all `possibly matched` and fully matched Passwords &        *
*   Decrypted blocks to  possible_passwords.log
*   This can be disabled with the --disablesavepossiblematches argument *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Wallet Type: btcrpass.WalletBlockchain
Wallet difficulty: 5,000 PBKDF2-SHA1 iterations
2024-04-21 20:39:43 : Using 8 worker threads
19758 of 139599 [#####---------------------------------] 0:00:27, ETA:  0:02:46

If this tool helped you to recover funds, please consider donating 1% of what you recovered, in your crypto of choice to:
-snip-

Password found: 'xxxxxxx7.'

So, it may be your OS, python version, dependencies or character formatting; testing it in another machine is worth the try.
But overall, BTCRecover should work in normal circumstances.

The other formats didn't worked and my best guess is your wallet file may be specifically formatted that way as I saw some "extra" stuffs that aren't in BTCRecover's or my test wallets.
So using the payload alone might have caused the errors, I'm not a Blockchain(.info/.com) developer so I can't tell.

[Hurley27]

-snip- I will also send the json as copied from network/response in the browser web dev so maybe you can see something in the payload that I can't. I really appreciate this. And no worries all wallets have been defunded other than the one I'm trying to recover.

I didn't expected that it would be this fast but your "full json script" with the exact token file contents (copy-paste) perfectly worked in my setup.

Command:

Code:

btcrecover.py --wallet hurley27-wallet.aes.full.json --token hurley27-token.txt --dsw

Command line result:

Code:

Starting btcrecover 1.12.0-Cryptoguide on Python 3.10.2 64-bit, 21-bit unicodes, 64-bit ints
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*                     Note for Blockchain.com Wallets...                *
*                                                                       *
*   Writing all `possibly matched` and fully matched Passwords &        *
*   Decrypted blocks to  possible_passwords.log
*   This can be disabled with the --disablesavepossiblematches argument *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Wallet Type: btcrpass.WalletBlockchain
Wallet difficulty: 5,000 PBKDF2-SHA1 iterations
2024-04-21 20:39:43 : Using 8 worker threads
19758 of 139599 [#####---------------------------------] 0:00:27, ETA:  0:02:46

If this tool helped you to recover funds, please consider donating 1% of what you recovered, in your crypto of choice to:
-snip-

Password found: 'xxxxxxx7.'

So, it may be your OS, python version, dependencies or character formatting; testing it in another machine is worth the try.
But overall, BTCRecover should work in normal circumstances.

The other formats didn't worked and my best guess is your wallet file may be specifically formatted that way as I saw some "extra" stuffs that aren't in BTCRecover's or my test wallets.
So using the payload alone might have caused the errors, I'm not a Blockchain(.info/.com) developer so I can't tell.

wow. that is insane lol. thanks a million. I am running on python 3.12 so maybe that is why. Will definitely try on another machine to see what is going on. I appreciate your help. just my luck over here it seems