Bruteforce wallet

[rizzler]

Hi

I am running btcrecover since a while back on my linux machine. I had lost the password which i do not remember with the following command and i wonder if there is any faster way of doing this ?

python3.7 btcrecover.py --wallet wallets/wallet_1 --no-dupchecks --no-eta

Wallet Type: btcrpass.WalletElectrum28
Wallet difficulty: 1024 PBKDF2-SHA512 iterations + ECC
2023-01-28 02:56:27 : Using 2 worker threads
| 1070011680  elapsed: 15 days, 13:23:13  rate: 796.03  P/s

TOKENS FILE

Code:

#--help
## --wallet wallets

###########################################################################
# This is a comment, btcrecover ignores everything after a # sign         #
# To automatically load a tokenlist save it as btcrecover-tokens-auto.txt #
# We can add arguments in the token by writing #-- only on the first line.#
#                                                                         #
# Just copy this file and your wallet.dat in btcrecover-master folder     #
#            Arguments are: --help, --wallet, --listpass and more         #
# All arguments can be found in btcrecover.py --help                      # 
# Run btcrecover without extra aguments (since they are in this file)     #
# so only write in CMD: C:\Python27\python btcrecover.py                  #
###########################################################################
#            Testing the Tokenlist                                        #
# Change #--help on line 1 of this file to #--listpass                    #
#                               and run btcrecover.py                     #
#                                                                         #
#            Running the Brute-Force                                      #
# replace #--listpass above with: #--wallet wallet.dat                    #
#                                                                         #
# You can never use --listpass and --wallet at the same time              #
# When using --listpass make sure you delete --wallet wallet.dat          #
# And if you use --wallet wallet.dat make sure you delete --listpass      #
#                                                                         #
########################################################################### 
#----The most used wildcards, only use them to finetune the tokenlist!----#
###########################################################################
# (space + # = #) (%S = $) (%% = %) (%^ = ^) (%s = 1 single space)        #
# The + sign = only try passwords with the following token in it.         #
# The ^ sign = try following token only in the begin of password          #
# %d = 1 digit(0-9) %2d = 2 digits(00-99) %1,3d = 1,2 or 3 digits (0-999) #
# ^r1^ ^r2^ ^r3^ = Relative position of token                             #
# The $ sign at the end of a token = token is at the end of password      #
# A space between tokens = OR                                             #
# (%a = a-z) (%A = A-Z) (%1,3in = 1,2 or 3 digits or a-Z)                 #
# (%y = symbol !@#$) (%P = Anything)                                      #
###########################################################################

%1,25in

[1714253230]

1714253230

[digaran]

Is that 796 passwords per second or 796k p/s? Did you really spend 15 days trying to crack a wallet and now are asking for faster methods? Wow. You should move this topic to project development : https://bitcointalk.org/index.php?board=12.0  in here mostly bitcoin client/software related stuff is discussed and some people don't visit this board too much. I have seen pass finders with millions/ trillions per sec.

[rizzler]

796 sadly enough.

I was questioning if i started the bruteforce the right way when i looked at it or if there is any other way?

it is looking for the password between 1 and 25 characters right ?

[nc50lc]

Knowing nothing about the password will render your bruteforce a waste of time and resources.
At least for now, try %1,8in, or a reasonable range of characters.
Then if there's no result, you can be certain that it's not a 1~8 alpha numeric characters.

But for it to be feasible, you should at least provide any possible characters/words to minimize the search for random alpha-numeric characters.

[rizzler]

Knowing nothing about the password will render your bruteforce a waste of time and resources.
At least for now, try %1,8in, or a reasonable range of characters.
Then if there's no result, you can be certain that it's not a 1~8 alpha numeric characters.

But for it to be feasible, you should at least provide any possible characters/words to minimize the search for random alpha-numeric characters.

How long should i let that run ?

[nc50lc]

-snip-

How long should i let that run ?

I did some rough estimation to give you a "reasonable range" like I suggested and the result is you can only search up to 5.
With a token of %1,5in; you'll exhaust that within 2 weeks at that speed.
%1,6in will take about 2 years, more will be impossible.
The bottom-line is, using random character search for the whole password wont work for long passwords.

As I previously mentioned, it's pointless unless you can remember a good portion of your password.

[DaveF]

Outside of what nc50lc said that unless you have more information this is probably a pointless waste since unless you are lucky, like winning the lottery lucky, finding a block with an old antminer S1 lucky it's not going to happen.

BUT if you want to do it, there is always the throw more hardware at the problem fix. More & faster cores will get you well....more. And don't forget using a GPU.

Still pointless and the odds of you getting it are insanely and pointlessly low, but you can get more speed if you want.

-Dave

[o_e_l_e_o]

796 sadly enough.

Electrum wallets are hardened with 1024 rounds of PBKDF2 as it says to slow down brute forcing, but even so, 796 is very slow. I can get about 15 kP/s off the bat without any optimizations.

I was questioning if i started the bruteforce the right way when i looked at it or if there is any other way?

Do you have a decent GPU? You can try adding the --enable-opencl argument to your command, provided you have installed the necessary dependencies: https://btcrecover.readthedocs.io/en/latest/GPU_Acceleration/

it is looking for the password between 1 and 25 characters right ?

Correct. That will look for every combination of between 1 and 25 lowercase letters, uppercase letters, and numbers. It is hard to overstate how futile such a search is.

[rizzler]

thanks everyone

I am running 8 K/ps right now with  %1,8in

How long should i give it ?

[o_e_l_e_o]

You are still wasting your time.

As I said above, you are searching all lowercase, all uppercase, and all digits. This is 26 + 26 + 10 = 62 possibilities for each character. So for 8 characters, that is 62⁸ possibilities. Divide that number by 8,000, and that gives you how many seconds it will take you to exhaust the search space. That works out at 865 years. (In reality it will be another 15 or so years more than that since you are searching for strings shorter than 8 characters as well.) This is also assuming that you did not use any symbols or spaces in your password either.

You will need to have some idea of what your password might be, otherwise you are wasting your time. Alternatively, did you not back up your seed phrase?

[rizzler]

You are still wasting your time.

As I said above, you are searching all lowercase, all uppercase, and all digits. This is 26 + 26 + 10 = 62 possibilities for each character. So for 8 characters, that is 62⁸ possibilities. Divide that number by 8,000, and that gives you how many seconds it will take you to exhaust the search space. That works out at 865 years. (In reality it will be another 15 or so years more than that since you are searching for strings shorter than 8 characters as well.) This is also assuming that you did not use any symbols or spaces in your password either.

You will need to have some idea of what your password might be, otherwise you are wasting your time. Alternatively, did you not back up your seed phrase?

no. someone randomly hit my keyboard and lockedit away. it could be "as" or "asd" in the beginning because they hit that part och they keyboard... how could i add to the tokens file for example if i want it to check  with "as" or "asd" in the beginning ort "qwe" or all 3 of these ?

[LoyceV]

did you not back up your seed phrase?

no. someone randomly hit my keyboard[/quote]
That's now how seed phrases work. Electrum will ask you to enter it again, to make sure you stored it.

it could be "as" or "asd" in the beginning because they hit that part och they keyboard...

That doesn't make sense either: you have to enter the same password twice to set it.

Who is this "someone" who randomly hit your keyboard while the only copy of your wallet was on your screen?

[rizzler]

did you not back up your seed phrase?

no. someone randomly hit my keyboard

That's now how seed phrases work. Electrum will ask you to enter it again, to make sure you stored it.

it could be "as" or "asd" in the beginning because they hit that part och they keyboard...

That doesn't make sense either: you have to enter the same password twice to set it.

Who is this "someone" who randomly hit your keyboard while the only copy of your wallet was on your screen?
[/quote]

long story short. someone thougt they would do a funny but they really managed to change the password :/

[LoyceV]

long story short. someone thougt they would do a funny but they really managed to change the password :/

Lesson learned: don't let anyone touch your computer. If you really don't have the seed words, you were just waiting for the moment your hard drive failed to lose your wallet. Maybe you can recover an older version from your disk using recovery software.

[rizzler]

long story short. someone thougt they would do a funny but they really managed to change the password :/

Lesson learned: don't let anyone touch your computer. If you really don't have the seed words, you were just waiting for the moment your hard drive failed to lose your wallet. Maybe you can recover an older version from your disk using recovery software.

I had the erlier password in keepass but i tried recovering keepass files but they are corrupted. is it possible to recover old keepass files and open them ? :/

[serveria.com]

Hi

I am running btcrecover since a while back on my linux machine. I had lost the password which i do not remember with the following command and i wonder if there is any faster way of doing this ?

python3.7 btcrecover.py --wallet wallets/wallet_1 --no-dupchecks --no-eta

Wallet Type: btcrpass.WalletElectrum28
Wallet difficulty: 1024 PBKDF2-SHA512 iterations + ECC
2023-01-28 02:56:27 : Using 2 worker threads
| 1070011680  elapsed: 15 days, 13:23:13  rate: 796.03  P/s

TOKENS FILE

Code:

#--help
## --wallet wallets

###########################################################################
# This is a comment, btcrecover ignores everything after a # sign         #
# To automatically load a tokenlist save it as btcrecover-tokens-auto.txt #
# We can add arguments in the token by writing #-- only on the first line.#
#                                                                         #
# Just copy this file and your wallet.dat in btcrecover-master folder     #
#            Arguments are: --help, --wallet, --listpass and more         #
# All arguments can be found in btcrecover.py --help                      # 
# Run btcrecover without extra aguments (since they are in this file)     #
# so only write in CMD: C:\Python27\python btcrecover.py                  #
###########################################################################
#            Testing the Tokenlist                                        #
# Change #--help on line 1 of this file to #--listpass                    #
#                               and run btcrecover.py                     #
#                                                                         #
#            Running the Brute-Force                                      #
# replace #--listpass above with: #--wallet wallet.dat                    #
#                                                                         #
# You can never use --listpass and --wallet at the same time              #
# When using --listpass make sure you delete --wallet wallet.dat          #
# And if you use --wallet wallet.dat make sure you delete --listpass      #
#                                                                         #
########################################################################### 
#----The most used wildcards, only use them to finetune the tokenlist!----#
###########################################################################
# (space + # = #) (%S = $) (%% = %) (%^ = ^) (%s = 1 single space)        #
# The + sign = only try passwords with the following token in it.         #
# The ^ sign = try following token only in the begin of password          #
# %d = 1 digit(0-9) %2d = 2 digits(00-99) %1,3d = 1,2 or 3 digits (0-999) #
# ^r1^ ^r2^ ^r3^ = Relative position of token                             #
# The $ sign at the end of a token = token is at the end of password      #
# A space between tokens = OR                                             #
# (%a = a-z) (%A = A-Z) (%1,3in = 1,2 or 3 digits or a-Z)                 #
# (%y = symbol !@#$) (%P = Anything)                                      #
###########################################################################

%1,25in

It could run faster but only if you remember some information about your password (like a number of characters, presence of certain letters/digits/special characters), perhaps you could also include a text file containing your passwords you use for another websites/wallets (it's possible you reused the password from some other website).

[rizzler]

Hi

I am running btcrecover since a while back on my linux machine. I had lost the password which i do not remember with the following command and i wonder if there is any faster way of doing this ?

python3.7 btcrecover.py --wallet wallets/wallet_1 --no-dupchecks --no-eta

Wallet Type: btcrpass.WalletElectrum28
Wallet difficulty: 1024 PBKDF2-SHA512 iterations + ECC
2023-01-28 02:56:27 : Using 2 worker threads
| 1070011680  elapsed: 15 days, 13:23:13  rate: 796.03  P/s

TOKENS FILE

Code:

#--help
## --wallet wallets

###########################################################################
# This is a comment, btcrecover ignores everything after a # sign         #
# To automatically load a tokenlist save it as btcrecover-tokens-auto.txt #
# We can add arguments in the token by writing #-- only on the first line.#
#                                                                         #
# Just copy this file and your wallet.dat in btcrecover-master folder     #
#            Arguments are: --help, --wallet, --listpass and more         #
# All arguments can be found in btcrecover.py --help                      # 
# Run btcrecover without extra aguments (since they are in this file)     #
# so only write in CMD: C:\Python27\python btcrecover.py                  #
###########################################################################
#            Testing the Tokenlist                                        #
# Change #--help on line 1 of this file to #--listpass                    #
#                               and run btcrecover.py                     #
#                                                                         #
#            Running the Brute-Force                                      #
# replace #--listpass above with: #--wallet wallet.dat                    #
#                                                                         #
# You can never use --listpass and --wallet at the same time              #
# When using --listpass make sure you delete --wallet wallet.dat          #
# And if you use --wallet wallet.dat make sure you delete --listpass      #
#                                                                         #
########################################################################### 
#----The most used wildcards, only use them to finetune the tokenlist!----#
###########################################################################
# (space + # = #) (%S = $) (%% = %) (%^ = ^) (%s = 1 single space)        #
# The + sign = only try passwords with the following token in it.         #
# The ^ sign = try following token only in the begin of password          #
# %d = 1 digit(0-9) %2d = 2 digits(00-99) %1,3d = 1,2 or 3 digits (0-999) #
# ^r1^ ^r2^ ^r3^ = Relative position of token                             #
# The $ sign at the end of a token = token is at the end of password      #
# A space between tokens = OR                                             #
# (%a = a-z) (%A = A-Z) (%1,3in = 1,2 or 3 digits or a-Z)                 #
# (%y = symbol !@#$) (%P = Anything)                                      #
###########################################################################

%1,25in

It could run faster but only if you remember some information about your password (like a number of characters, presence of certain letters/digits/special characters), perhaps you could also include a text file containing your passwords you use for another websites/wallets (it's possible you reused the password from some other website).

How do i put something in the tokens file if it might have been "as" or "asd" that is pressent in the password?

[o_e_l_e_o]

no. someone randomly hit my keyboard and lockedit away. it could be "as" or "asd" in the beginning because they hit that part och they keyboard... how could i add to the tokens file for example if i want it to check  with "as" or "asd" in the beginning ort "qwe" or all 3 of these ?

Something like the following:

Code:

+ ^%1,3[qweasd]
%0,3n

This will try every combination of between 1 and 3 characters from the set "qweasd", followed by between 0 and 3 lowercase letters or digits. At 8 kP/s, you should be able to search that in around 30 minutes.


Your story makes no sense, though. To change a password in Electrum, you have to first enter the current password, then enter the new password twice. This cannot be achieved by someone randomly hitting the keyboard, nor can it be achieved by someone who does not already know your password. Are you sure this is your wallet file?

[nc50lc]

I had the erlier password in keepass but i tried recovering keepass files but they are corrupted. is it possible to recover old keepass files and open them ? :/

Do not waste your time recovering it from the corrupted files.
You old password will not help you recover the current password, that is unless you made a backup of the wallet file before the password has changed.