Crack my bitcoin wallet address and get 0.155 btc + 0.5BTC

[ImHash]

There is a service thread called lost password recovery for wallets or similar to that, if you search in forum "recover lost wallet password" there is a newbie or member I think with green trust, you send them partial info about your wallet and they will find your password.

[1713457113]

1713457113

[1713457113]

1713457113

[1713457113]

1713457113

[Butense]

I've reached out to a couple recovery services too.  Btw, all i care about is getting the password, doesn't matter who came up with it or from where.  If you come up with it indirectly, that person will get the bounty and they can then forward it part of it to whoever actually cracked it.  I may raise it to 1btc soon

[bets21]

weird for me,...OP want someone cracking the address and pay 0.5 btc for balance $194 in the wallet ? pay $600 for $194

[Checlets]

weird for me,...OP want someone cracking the address and pay 0.5 btc for balance $194 in the wallet ? pay $600 for $194

The part that we would gain access to has 0.155 btc there's another part that he'll recover 3 btc from so yeah the initial .155 btc + .5 btc is .655 btc he's offering to pay to be able to keep the other 2.5btc

[leonair]

I knew some encrypted wallet that has been retrieved again with the help of a script but can I get some bounty too if he really helps you with this? What version of bitcoin qt are using way back in 2013?

[lighpulsar07]

Have you try all possible passwords that you can think? Is your password have birthdate, symbols, case sensitive letters like this: LiGhPuLsAr07? Try to search you old passwords list in your computer i might be there or try to remember the most used password you used in 2013 and also how long is your password to bruteforce it? how many characters?

EDIT: did you save your wallet password on your computer?

[ncsupanda]

I'm sure there are a lot of people here trying to use btcrecover to attempt this on their own - and surely there are more people stuck on extracting some information from what you've provided.
If using btcrecover the following information is needed for --data-extract.


Partial Bitcoin Core encrypted master key, salt, iter_count, and crc in base64:

Code:

YmM64LYAAfzSnXMMKY3nU446Bwnk/bc42KxhtbA8WC1yQhTQfmbCYGrk/L44AQAA5o2b

You can generate this by editing the extract scripts included in that tool. Excerpt from extract-bitcoincore-mkey-from-pywallet.py.

encrypted_master_keytest = "3ce2900d6c2df58a1cfa9ea1755a1599e0b60001fcd29d730c298de7538e3a0709e4fdb738d8ac61b5b03c582d724214" #Hardcode from OP
saltnumber = "d07e66c2606ae4fc" #Hardcode from OP

encrypted_master_key = base64.b16decode(encrypted_master_keytest, True)  # True means allow lowercase
salt                 = base64.b16decode(saltnumber, True)
iter_count           = int(80062)

print("Partial Bitcoin Core encrypted master key, salt, iter_count, and crc in base64:", file=sys.stderr)

# Only include the last two AES blocks (last 32 bytes) of the 48-byte encrypted master key
bytes = b"bc:" + encrypted_master_key[-32:] + salt + struct.pack("<I", iter_count)
crc_bytes = struct.pack("<I", zlib.crc32(bytes) & 0xffffffff)

print(base64.b64encode(bytes + crc_bytes))

If you've made it this far, then the issue is likely your amount of computing power; without either having a large amount of GPUs or a more defined tokens list / logic, then you cannot move forward.

You can try a command such as the following:

Code:

C:\python27\python btcrecover.py --data-extract --enable-gpu  --tokenlist tokens.txt --typos 3 --typos-capslock --typos-swap --typos-repeat --pause

Hopefully we can help recover this for the OP. If I've made any mistakes above please let me know. Thanks.

EDIT:

Adding link to the btcrecover github as credit is due to them.
https://github.com/gurnec/btcrecover

[AppleBTC]

If someone manage to crack open the wallet, i think that person would just withdraw all the bitcoin out of the wallet.

[SopaXT]

Could you create a wallet with one of the passphrases given as example, so that I can test my bruteforce script (please publish it in the same format)? Thanks.

[ncsupanda]

If someone manage to crack open the wallet, i think that person would just withdraw all the bitcoin out of the wallet.

The user hasn't provided the wallet file - the best you can do with this method is discover their password via bruteforce. What you are not doing is calculating their privatekey.

[kolloh]

I'm sure there are a lot of people here trying to use btcrecover to attempt this on their own - and surely there are more people stuck on extracting some information from what you've provided.
If using btcrecover the following information is needed for --data-extract.


Partial Bitcoin Core encrypted master key, salt, iter_count, and crc in base64:

Code:

YmM64LYAAfzSnXMMKY3nU446Bwnk/bc42KxhtbA8WC1yQhTQfmbCYGrk/L44AQAA5o2b

You can generate this by editing the extract scripts included in that tool. Excerpt from extract-bitcoincore-mkey-from-pywallet.py.

encrypted_master_keytest = "3ce2900d6c2df58a1cfa9ea1755a1599e0b60001fcd29d730c298de7538e3a0709e4fdb738d8ac61b5b03c582d724214" #Hardcode from OP
saltnumber = "d07e66c2606ae4fc" #Hardcode from OP

encrypted_master_key = base64.b16decode(encrypted_master_keytest, True)  # True means allow lowercase
salt                 = base64.b16decode(saltnumber, True)
iter_count           = int(80062)

print("Partial Bitcoin Core encrypted master key, salt, iter_count, and crc in base64:", file=sys.stderr)

# Only include the last two AES blocks (last 32 bytes) of the 48-byte encrypted master key
bytes = b"bc:" + encrypted_master_key[-32:] + salt + struct.pack("<I", iter_count)
crc_bytes = struct.pack("<I", zlib.crc32(bytes) & 0xffffffff)

print(base64.b64encode(bytes + crc_bytes))

If you've made it this far, then the issue is likely your amount of computing power; without either having a large amount of GPUs or a more defined tokens list / logic, then you cannot move forward.

You can try a command such as the following:

Code:

C:\python27\python btcrecover.py --data-extract --enable-gpu  --tokenlist tokens.txt --typos 3 --typos-capslock --typos-swap --typos-repeat --pause

Hopefully we can help recover this for the OP. If I've made any mistakes above please let me know. Thanks.

EDIT:

Adding link to the btcrecover github as credit is due to them.
https://github.com/gurnec/btcrecover

Thanks for the info in this post. It was useful for me as this is the first time I am messing with btcrecover.

It definitely takes quite some time to brute force passwords though especially without any definitive information about what the password might be. I'll see if I can come up with anything though.

[Jude Austin]

Any luck?

I'm sure there are a lot of people here trying to use btcrecover to attempt this on their own - and surely there are more people stuck on extracting some information from what you've provided.
If using btcrecover the following information is needed for --data-extract.


Partial Bitcoin Core encrypted master key, salt, iter_count, and crc in base64:

Code:

YmM64LYAAfzSnXMMKY3nU446Bwnk/bc42KxhtbA8WC1yQhTQfmbCYGrk/L44AQAA5o2b

You can generate this by editing the extract scripts included in that tool. Excerpt from extract-bitcoincore-mkey-from-pywallet.py.

encrypted_master_keytest = "3ce2900d6c2df58a1cfa9ea1755a1599e0b60001fcd29d730c298de7538e3a0709e4fdb738d8ac61b5b03c582d724214" #Hardcode from OP
saltnumber = "d07e66c2606ae4fc" #Hardcode from OP

encrypted_master_key = base64.b16decode(encrypted_master_keytest, True)  # True means allow lowercase
salt                 = base64.b16decode(saltnumber, True)
iter_count           = int(80062)

print("Partial Bitcoin Core encrypted master key, salt, iter_count, and crc in base64:", file=sys.stderr)

# Only include the last two AES blocks (last 32 bytes) of the 48-byte encrypted master key
bytes = b"bc:" + encrypted_master_key[-32:] + salt + struct.pack("<I", iter_count)
crc_bytes = struct.pack("<I", zlib.crc32(bytes) & 0xffffffff)

print(base64.b64encode(bytes + crc_bytes))

If you've made it this far, then the issue is likely your amount of computing power; without either having a large amount of GPUs or a more defined tokens list / logic, then you cannot move forward.

You can try a command such as the following:

Code:

C:\python27\python btcrecover.py --data-extract --enable-gpu  --tokenlist tokens.txt --typos 3 --typos-capslock --typos-swap --typos-repeat --pause

Hopefully we can help recover this for the OP. If I've made any mistakes above please let me know. Thanks.

EDIT:

Adding link to the btcrecover github as credit is due to them.
https://github.com/gurnec/btcrecover

Thanks for the info in this post. It was useful for me as this is the first time I am messing with btcrecover.

It definitely takes quite some time to brute force passwords though especially without any definitive information about what the password might be. I'll see if I can come up with anything though.

[Butense]

anyone have any luck?

[kolloh]

anyone have any luck?

No luck here, unfortunately. It would help if you had a bit more of an idea of the password or its length. Longer passwords are likely not gonna be possible to find without a better idea of the password.

[reee]

Butense, can you pass your wallet.dat into this script? https://github.com/stricture/hashstack-server-plugin-hashcat/blob/master/scrapers/bitcoin2hashcat.py

syntax should be: bitcoin_hash.py wallet.dat > wallet.hash

then post here the content of the wallet.hash file, it should be a string like this: $bitcoin$96$d011a1b6a8d675b7a36d0cd2efaca32a9f8dc1d57d6d01a58399ea04e703e8bbb44899039326f7a00f171a7bbc854a54$16$1563277210780230$158555$96$628835426818227243334570448571536352510740823233055715845322741625407685873076027233865346542174$66$625882875480513751851333441623702852811440775888122046360561760525

It's useful to pass the info to hashcat in the correct syntax.

However, cracking speed seem very slow with this algorithm, so brute force is impossible (except for very short passwords). The only realistic possibility is try possible variations of the list of password you posted in the first post.

[reee]

Question: would it be feasible to crack an 8 char password given a-z A-Z 0-9?  I'm just curious, i don't remember the actual length. 

I tried it with hashcat, it says that extimated time is 3years and 61 days, however i'm using a laptop GPU with an hashpower on this algorithm of 110 H/s. Probabiy a modern desktop GPU can reach 1000 H/s or something similar. So, if your password is really 8 char or lower, it would take some month with a good GPU, and probably a few week/day if you use some rack of GPU (amazon offers something similar). But if your password is something like 10 char it would take many longer.

[Mikanoshi]

I can reach 10500 P/s in btcrecover on my GTX 1080, but even with an incomplete set of chars from the example passwords [Fromage243Md96?P15hyqz7TiltQus8!fjpOknwc0] it will take years to crack 8 chars.
Hashcat gives 8000 P/s (but not for this hash, I was trying to crack wallet with 1 BTC and unknown 11 char pwd in it that has 122023 hash iterations, so with 80062 speed should be around 12k P/s).
Longest sample pwd is 17 characters, bruteforcers can't event start bruting such passwords, either something overflows or it eats all the RAM Good luck bruteforcing that

it says that extimated time is 3years and 61 days

Mine too, which must be incorrect, it should be around 32 years for my charset according to http://calc.opensecurityresearch.com/
a-zA-Z0-9 will take 700 years on 10k P/s.

Session..........: hashcat
Status...........: Running
Hash.Type........: Bitcoin/Litecoin wallet.dat
Hash.Target......: $bitcoin$96$6b6178c1803c946cdc62b2eccfbb121443cf006...0b6573
Time.Started.....: Thu Jun 15 06:34:28 2017 (15 secs)
Time.Estimated...: Sat Aug 15 16:21:23 2020 (3 years, 61 days)
Guess.Mask.......: ?1?1?1?1?1?1?1?1 [8]
Guess.Charset....: -1 Fromage243Md96??P15hyqz7TiltQus8!fjpOknwc0, -2 Undefined, -3 Undefined, -4 Undefined
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....:     8006 H/s (85.79ms)
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0/7984925229121 (0.00%)
Rejected.........: 0/0 (0.00%)
Restore.Point....: 0/194754273881 (0.00%)
Candidates.#1....: sarinane -> s5F84501
HWMon.Dev.#1.....: Temp: 57c Fan: 33% Util:100% Core:2062MHz Mem:5005MHz Bus:16

[abhinav_thakur01]

Bruteforcing , dictionary attack or whatever you may try seems to be far away from practical and chances of getting any luck is also less. I generally use third party applications due to which synchronising becomes no longer a problem. However, I will do a research and give it a shot in my spare time.

[rishab2019]

Hello bro,

I can help you regarding recovery of the wallet.email me:-rishab2019@gmail.com

[restypots]

looks great like rootOS encrypt developer .Such no any idea to confirming .looking for third party