Don't buy "wallet.dat" files with lost passwords. EXCHANGE THEM!

[cashmax]

So, any of these have been actually opened? Ever?

All wallet passwords are supposed to be long or very complex to build. As far as I know, only one wallet with more than 30 bitcoins was opened.

Yes this is true statement if you talk about Bitcoin in 2020, in 20k price range.  All of the wallets (most of them anyway) are from 2010-sh period when BTC was at $200 , password standards were a bit easier 10 yrs ago as compute power potential was a LOT less than today, so considering all this, I'm really surprised that besides all those fake wallets, non of the real ones were actually cracked.

[MrSapien]

I would really want to know if someone with a mining farm actually tested with hashcat,and if there would be any results post them here.

[walletrecovery]

Hi.

Take a look at this page: https://allprivatekeys.com/wallet.dat; you can buy "wallet.dat" files with lost passwords.

If you want to buy there, Ok, it seems good to me, you are free to do it (some think it is a scam).

But, if you already have one of those advertised there and want to exchange it for one of mine (in the list below), don't you think it's a better idea?

The conditions are as follows:
     - Your "wallet.dat" file must be one of those advertised on the website indicated above.
     - Your file "wallet.dat" should NOT be in the list of those that I already have.
     - If you meet these two conditions, send me a private message with a link where I can download your "wallet.dat" indicating which one it is and which one of mine you want and I will reply to you. It is exchanged one by one, or one by several, with a similar balance or value.
     - Please use this address to check that the files are virus free: https://virusdesk.kaspersky.com.

...

It is not necessary to exchange wallets, but to exchange information about the dictionaries with which these wallets have already been verified.

[DN_Broker]

What I don't understand is, when I check some of those address, it seems there are some activities on it. How can it be, if the persons really lost their password and continue to receive money there ?
Well, maybe worth though to give a try... Where to find the wallet.dat of those address?

[mikecolins]

Hey guys, what do you think about combining cracking power and making different hashcat attacks together in parallel?

Benchmark of my setup:
~/hashcat -m 11300 -b
Hashmode: 11300 - Bitcoin/Litecoin wallet.dat (Iterations: 200459)

Speed.#1.........:    10716 H/s (66.11ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1
Speed.#2.........:    11148 H/s (63.59ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1
Speed.#3.........:    11092 H/s (64.11ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1
Speed.#4.........:     3863 H/s (80.94ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#5.........:     3827 H/s (81.85ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#6.........:     3830 H/s (81.87ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#7.........:     3790 H/s (82.58ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1
Speed.#*.........:    48265 H/s

All we need to share is a wallet hash in hashcat format.

[MA40]

Wow!

I congratulate you mikecolins for the speed you get.

If I could get something like that ...

Hey guys, what do you think about combining cracking power and making different hashcat attacks together in parallel?

That would be perfect; the problem is trust. How to trust someone you don't know?

A greeting.

[mikecolins]

Great question!
I don't really have an answer.
To be fair we should think about trust only when we'll get to the point of actual transfer BTC out of cracked wallet.
For now, to start cracking i need only wallet hashes which doesn't reveal any private keys.

Let's crack first and then think about trust

[N1OTC]

Hi everyone!

About a week ago I started working on wallet.data files. Even though I got a private key and it was password protected.
I only set 2 TITANV GPUs on the break to test.

The thing works!

What I am sharing now is for skeptics that it is not impossible to do!


Time.Started.....: Wed Jan 06 21:42:24 2021 (4 hours, 38 mins)
Time.Estimated...: Sat Jan 09 13:32:21 2021 (2 days, 11 hours)
Guess.Mask.......: ?a?a?a?a?a [5]
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........:    17248 H/s (10.09ms) @ Accel:2 Loops:128 Thr:1024 Vec:1
Speed.#2.........:    16426 H/s (11.25ms) @ Accel:2 Loops:128 Thr:1024 Vec:1
Speed.#*.........:    33673 H/s
Recovered........: 0/1 (0.00%) Digests
Progress.........: 562626560/7737809375 (7.27%)
Rejected.........: 0/562626560 (0.00%)
Restore.Point....: 5570560/81450625 (6.84%)
Restore.Sub.#1...: Salt:0 Amplifier:49-50 Iteration:84096-84224
Restore.Sub.#2...: Salt:0 Amplifier:60-61 Iteration:102400-102528
Candidates.#1....: HQl`4 -> HvPRL
Candidates.#2....: Z8_&a -> Z<4(2
Hardware.Mon.#1..: Temp: 77c Fan:100% Util: 99% Core:1402MHz Mem: 850MHz Bus:16
Hardware.Mon.#2..: Temp: 74c Fan:100% Util: 99% Core:1402MHz Mem: 850MHz Bus:16


At the moment it seems that I am going for a 5 word experiment and the number of possible variations = 7737809375.
It can also be seen that there are only 2 days 11 hours left.
The 1,2,3,4 word option had already been tested and it wasn’t that hard.
If the password is not 5 words, I will continue to look for the 6,7,8,9,10 ... character options.
Since it would be hard enough with 2GPU there I will already be using a 40 X RTX3090 GPU.
I think in about a couple of weeks you will have quite a bit of BTC and the rest of the altcoin.

[yangxin325]

Hi everyone!

About a week ago I started working on wallet.data files. Even though I got a private key and it was password protected.
I only set 2 TITANV GPUs on the break to test.

The thing works!

What I am sharing now is for skeptics that it is not impossible to do!


Time.Started.....: Wed Jan 06 21:42:24 2021 (4 hours, 38 mins)
Time.Estimated...: Sat Jan 09 13:32:21 2021 (2 days, 11 hours)
Guess.Mask.......: ?a?a?a?a?a [5]
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........:    17248 H/s (10.09ms) @ Accel:2 Loops:128 Thr:1024 Vec:1
Speed.#2.........:    16426 H/s (11.25ms) @ Accel:2 Loops:128 Thr:1024 Vec:1
Speed.#*.........:    33673 H/s
Recovered........: 0/1 (0.00%) Digests
Progress.........: 562626560/7737809375 (7.27%)
Rejected.........: 0/562626560 (0.00%)
Restore.Point....: 5570560/81450625 (6.84%)
Restore.Sub.#1...: Salt:0 Amplifier:49-50 Iteration:84096-84224
Restore.Sub.#2...: Salt:0 Amplifier:60-61 Iteration:102400-102528
Candidates.#1....: HQl`4 -> HvPRL
Candidates.#2....: Z8_&a -> Z<4(2
Hardware.Mon.#1..: Temp: 77c Fan:100% Util: 99% Core:1402MHz Mem: 850MHz Bus:16
Hardware.Mon.#2..: Temp: 74c Fan:100% Util: 99% Core:1402MHz Mem: 850MHz Bus:16


At the moment it seems that I am going for a 5 word experiment and the number of possible variations = 7737809375.
It can also be seen that there are only 2 days 11 hours left.
The 1,2,3,4 word option had already been tested and it wasn’t that hard.
If the password is not 5 words, I will continue to look for the 6,7,8,9,10 ... character options.
Since it would be hard enough with 2GPU there I will already be using a 40 X RTX3090 GPU.
I think in about a couple of weeks you will have quite a bit of BTC and the rest of the altcoin.

I suggest you use more than 11 passwords to crack the password, most of the wallet files in this post were exchanged to me, at least in the past 3 years or more, the low number of passwords should have been tried, no sense.

[hashingpool]

I was following this topic for a while and decided now to jump in.
I don't know if I am allowed to post link here so I will provide it through private messaging.

I am sitting here on an old wallet.dat with 50 BTC.
After reading all the comments in this thread I decided to set up a solution to share wallet hashes (not the wallet file).
This solution also splits the brute force tasks among a hashcat connected network of computers.

The only knowledge required is to be able to install python (as well as 2 extensions) to run the client.
It downloads by itself the necessary files (hashcat, the hash files and, if necessary the dictionary files) and share online the resources with the others.

For me the wallet is lost, so if peoples are interest to jump in, they only need to contact me and I'll configure them an account to share the resources.

If we are able to find the password, I will share the 50BTC to all involved participants.

[mikecolins]

I was following this topic for a while and decided now to jump in.
I don't know if I am allowed to post link here so I will provide it through private messaging.

I am sitting here on an old wallet.dat with 50 BTC.
After reading all the comments in this thread I decided to set up a solution to share wallet hashes (not the wallet file).
This solution also splits the brute force tasks among a hashcat connected network of computers.

The only knowledge required is to be able to install python (as well as 2 extensions) to run the client.
It downloads by itself the necessary files (hashcat, the hash files and, if necessary the dictionary files) and share online the resources with the others.

For me the wallet is lost, so if peoples are interest to jump in, they only need to contact me and I'll configure them an account to share the resources.

If we are able to find the password, I will share the 50BTC to all involved participants.

Hey, it's definitely bad idea to share resources with someone you don't trust.
A better idea might be to share dictionaries and open private (known to specific people) hashcat brain server to the internet.
It will reject password candidates based on attack type and it's position. Of course one who attempt to guess a password should not send password hashes to the brain server, but only attack positions (--brain-client-features=2) otherwise network bandwidth and brain server resources will become a bottleneck.
I don't know if there are some kind of vulnerabilities in brain server, and if it's secure to open it to the internet, but it may be a solution to distributing the cracking power.

I'm interested in contributing in such process, so PMs are welcome by the way of making this happen we could learn to work with each other and build a trust.

[hashingpool]

Well, actually, only the wallet hash is shared. Correct me if I'm wrong but it can't be exploited to recreate a wallet.dat file.
Actually, I didn't configure hashcat brain. For a bruteforce attack, it is not necessary.
I don't believe brute force attacks are the way to process but let see how it goes.
Meanwhile, I'll try to configure a dictionary attack with brain and prince to check if it goes better.

[mikecolins]

It's not a problem of sharing wallet.dat hash itself, the problem is to share cracking resources with someone you don't trust.

For the reference: https://github.com/hashcat/hashcat/blob/master/docs/hashcat-brain.md
Just a simple example:
you run an attack on some hash (no matter which type 3 or 0):
1. hashcat -m 11300 -a 0 myholywallet.hash some_dictionary.txt -r very_cool_rules.rule
2. it fails, and you decide to make another attack then another and another
3. you execute again attack #1 because you've already forgot about it
4. hashcat brain checks if it already done it in it's database, and if so - rejects all password candidates.
5. You earn the time of not doing the same work twice (or more)

[hashingpool]

Thanks for the heads up.
I was under the impression hashcat brain was necessary to check if a hash had been already cracked. In our case, we work on a very limited number of hashes (actually, 1 ). This is why I didn't see hashcat brain as a necessary. If it can help, I will still implement it on my server asap.

What do you mean with "sharing cracking resources with someone you don't trust" ?
I might be a bit naive but what can really happen ? Other than not being paid if the password is found.
Actually, it would be a really bad move.
I am sure many peoples are in this situation (owning a wallet file without its password) and if we can build a system allowing to better/faster find those passwords it would/could be really profitable for everybody.
Just my opinion.

[hashingpool]

I only wanted to say the persons who contacted me per PM.
I am actually limited to 1 PM per hour (I guess this is a new member limitation).

[N1OTC]

I Started the search from a character because I don't know the length of the password.
But I have to put an entire farm over five characters on it to have a chance.
I put together the program and did a test on my own Bitcoin wallet which was 4 characters.
He finished with him in about a few minutes and who wrote the correct password.
And then I started it live and now I’m walking at five characters.

[N1OTC]

Hi! #MA40

Why is the download link not available?

[N1OTC]

#MA40

It has been successfully downloaded.

I also have some wallet .dat in my possession if you want to replace it.

Discord we can talk here is my server availability.

https://discord.gg/7WR2egY8yx

[MA40]

I also have some wallet .dat in my possession if you want to replace it.

Hello N1OTC.

What do you mean "replace it"?

A greeting.

[mikecolins]

I also have some wallet .dat in my possession if you want to replace it.

Hello N1OTC.

What do you mean "replace it"?

A greeting.

Probably he means "exchange" and not replace.