GitHub script for bruteforcing privatekeys

bL4nkcode

copper member

Activity: 2142

Merit: 1305

Limited in number. Limitless in potential.

Quote from: nikolai7711 on June 26, 2021, 01:55:28 AM

What's your opinion about it?

If it's really that working and higher the probability, then there's no users on this forum, and bitcoin price won't go up such the current price.

No one will use a system that it flawed mainly for financial related software.

pooya87

legendary

Activity: 3472

Merit: 10611

Quote from: nikolai7711 on June 26, 2021, 01:55:28 AM

What's your opinion about it?

My opinion is that you should try to make an honest living instead of trying to rob others. I don't think stealing is legal anywhere in the world either.

Apart from that others already mentioned that it is not possible to find a private key that was used before at random. The code is written in such a stupid way too which is why it can only check 26k keys/sec instead of something like 100 million key/sec which is understandable because a developer who has a better understanding of how to write code and understanding of basic cryptography knows making such a tool is a complete waste of time so only newbies with no understanding of anything do it...

khaled0111

legendary

Activity: 2702

Merit: 3045

Top Crypto Casino

Quote from: nikolai7711 on June 26, 2021, 01:55:28 AM

But when i input other wallet like with the next letter priv key 1184cd2cdd640ca42cfc3a091c51d549b2f016d454b2774019c2b2d2e08529fe ,it doesn't find anything for days.

You got it wrong! You have to add the public address to the "riches.txt" file not the private key. If you have the private key then why do you need this tool in first place!
Anyway, you are wasting your time and resources as it's almost impossible to find a valid pk for a loaded address.
Changing a single character doesn't make it any easier. Public addresses are generated from private keys through one-way hash functions and even changing a single bit in the input (private key) will result in a completely different output (publik key).

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Test.js already has the privateKeyHex: 1184cd2cdd640ca42cfc3a091c51d549b2f016d454b2774019c2b2d2e08529fd in the code.
Unlike "generator.js" which is the main script, "test.js" wont generate a random 64 character string from the character list.
ref: https://github.com/Michal2SAB/Bitcoin-Stealer/blob/main/test/test.js#L4 | main/generator.js#L8

And please, read README.md;
The author is aware that the chance is very slim that you'll basically waste your time "Bitcoin-Stealing" private keys.
That's what "lots of time" in the requirements #3 means.

nikolai7711

newbie

Activity: 4

Merit: 0

Hello,people.Is there anyone,who used this script ( https://github.com/Michal2SAB/Bitcoin-Stealer ) for bruteforcing private keys by pairing wallet addresses? It looks cool to me,but when i opened the test function with test wallet 16UjcYNBG9GTK4uq2f7yYEbuifqCzoLMGS with privkey 1184cd2cdd640ca42cfc3a091c51d549b2f016d454b2774019c2b2d2e08529fd and test is done,it finds it perfectly.But when i input other wallet like with the next letter priv key 1184cd2cdd640ca42cfc3a091c51d549b2f016d454b2774019c2b2d2e08529fe ,it doesn't find anything for days.This makes me thing that the tool doesn't work properly.What's your opinion about it? If someone used to work with the script,share me your opinion,please.

Topic: GitHub script for bruteforcing privatekeys (Read 138 times)