btcrecover isn't recognizing my blockchain.com password, even though I know it's correct

Hey everyone, I’m dealing with an issue involving one of my wallets. I lost the password for my blockchain.com account, and I never wrote down a seed phrase. I have a good guess about what the password might be. I tried using btcrecover to access my wallet.aes.json file and ran a bunch of token lists, but no luck there. Recently, I logged into another blockchain account of mine successfully using the password I think is correct. So, I thought I’d test btcrecover on that second wallet with my token and password lists, which should have worked since I included the password in both. But btcrecover just finished searching without finding anything. This makes me wonder if all my attempts on the first wallet were pointless, since it looks like btcrecover isn’t recognizing the right password when it’s in the lists. Has anyone else run into this issue or have any advice? Both wallets were set up around 2015/16. I’d really appreciate any support. I just want to get btcrecover to recognize the correct password on the second wallet, so I can feel confident going back to the first one.

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.

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.

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

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: With this command: 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. Then these are the instructions I enter into terminal Here are the contents (as example) of my tokenlist file Results in this 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.

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.

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

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

Is the path correct? Because the error message is supposed to be Password search exhausted 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 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.

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.

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. 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 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.

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: Command line result: 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