Ability to download old Blockchain.info wallet

[BitcoinOtter]

Hello, everyone.

A few weeks back I realized that I had two old Blockchain.info wallets tied to my email that I must have opened in 2012 or 2012. I honestly doubt there’s anything there but dust, but I’d love to download both wallets and let a password cracker run on them for fun.

I’ve read a few guides on how people were able to use dev tools in their browser to download their blockchain wallet file in the past, but it looks like they changed the website slightly. Does anyone know a way I can download a copy of my password protected wallet to I have access it locally?


Thanks for your help. 

[1714479210]

1714479210

[1714479210]

1714479210

[1714479210]

1714479210

[1714479210]

1714479210

[nc50lc]

I’ve read a few guides on how people were able to use dev tools in their browser to download their blockchain wallet file in the past,

Yes, but that was in the past and it's uncertain if it'll work today even if your wallet is old.
It wont work in newer wallets.

It requires your WalletID and the step is simple; type their URL with your walletID like this: blockchain.info/wallet/<WalletID>?format=json
For example: blockchain.info/wallet/aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa?format=json

Does anyone know a way I can download a copy of my password protected wallet to I have access it locally?

The old BTCRecover's extract script didn't work in my test which I remember working in the paste few years.
Here's the script if you're interested bu as I've mentioned, it failed with "HTTP Error 403" in my test.
Link: github.com/gurnec/btcrecover/blob/master/extract-scripts/download-blockchain-wallet.py

AFAIK, you should've received it in those email as an attachment, try to search for old email sent by Blockchain(dot)info.

[BlackBoss_]

You can try these pages from blockchain.com
Forgot password
https://login.blockchain.com/wallet/forgot-password
New HD:
https://login.blockchain.com/#/recover
Reset 2FA:
https://login.blockchain.com/#/reset-2fa

Reminder for your wallet ID if you still have access to two emails used to register those wallets.
https://login.blockchain.com/#/reminder

Watch this video to brute force your wallet passwords. If you remember some characters in your passwords, it can help the brute force process faster.
https://www.youtube.com/watch?v=rMtW8vIHHek

[delfastTions]

The situation that OP described is typical for those early users of this Blockchain.info wallet.  And the desire to see if there is some Satoshi left on old abandoned wallets is also typical.  

Lately I have been very interested in the question of whether wallet users somehow manage to receive from Blockchain.com old backup copies of Wallet.aes.json files, which, according to their documents, are stored in the databases of this service for each wallet as at the time of its creation, and every time you exit the Wallet.  Are there any lucky people among our forum users to whom the Blockchain.com support re-sent the original archived file Wallet.aes.json, or does the support in principle consider this a violation of security protocols and does not send anything to anyone.

For wallets created before 2016, the relevant question is how to find out the private key of your wallet from Wallet.aes.json (the password for which can be known to the user either exactly, or part of the password, or several options).
The procedure for finding out the private key is also  It’s quite confusing and not very simple, in my opinion. I still don’t understand whether BTCrecover still copes with this task or whether it’s not always capable of extracting the private key in WIF format.

I think many of our forum users will be grateful if our colleagues  will share their experience in these matters.

[BitcoinOtter]

Thank you all for your help.

I wasn't able to use the extract script, but using the dev tools I was able to extract two payloads that look like

Code:

{"pbkdf2_iterations":5000,"version":3,"payload":"jshhfjsagfhsjdgfasukdfgsuafgudfgsauyfguhfusag"}

I saved both as .txt files and now I'll start reading about bruteforcing my old passwords.

I've noticed btcrecover (https://github.com/gurnec/btcrecover) hasn't been updated in years. Is this still the right git repository to use or should I pivot to https://github.com/3rdIteration/btcrecover ?


Edit: I also noticed this message from Blockchain. Now that I've extracted my file, would I be impacted by this with BTCRecover?

"Important Note Some older blockchain.com wallets (2014-2015 era at least, perhaps more) have a bug where some private keys were incorrectly encoded and saved to the wallet file... (Basically if the hex encoded private key included any leading zeroes, these were left off, leading to private keys that are less than 32 bytes... The current blockchain.com simply rejects these as invalid and assumes an incorrect password...) The symptoms of this are that your wallet may have correctly worked until about 2015/2016"

Thanks, I'll keep you all posted.
----------------------------------
Edit2: I was able to remember my Main Wallet Password and Second Password for one of the two wallets! Sadly, while I could see all of my old transactions, there was nothing left.

Now to figure out how to brute force the main password for my second wallet...

[nc50lc]

I wasn't able to use the extract script, but using the dev tools I was able to extract two payloads that look like

Code:

{"pbkdf2_iterations":5000,"version":3,"payload":"jshhfjsagfhsjdgfasukdfgsuafgudfgsauyfguhfusag"}

I didn't expected that to work, really.
It's good to know that the "URL trick" to get the wallet.aes.json's contents still works in old wallets with associated email.
Usually, it'll request for email authorization but wont show the payload even after refresh.

Edit: I also noticed this message from Blockchain. Now that I've extracted my file, would I be impacted by this with BTCRecover?

"Important Note Some older blockchain.com wallets (2014-2015 era at least, perhaps more) have a bug where some private keys were incorrectly encoded and saved to the wallet file... (Basically if the hex encoded private key included any leading zeroes, these were left off, leading to private keys that are less than 32 bytes... The current blockchain.com simply rejects these as invalid and assumes an incorrect password...) The symptoms of this are that your wallet may have correctly worked until about 2015/2016"

Since you're using BTCRecover where there are separate decryption scheme for old and new wallets,
it may still work in your old wallet because the buggy code is still applied there.
Link: github.com/3rdIteration/btcrecover/blob/master/btcrecover/btcrpass.py#L2027-L2036