Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't use this script #7

Open
Eik0 opened this issue Jun 27, 2020 · 2 comments
Open

Don't use this script #7

Eik0 opened this issue Jun 27, 2020 · 2 comments

Comments

@Eik0
Copy link

Eik0 commented Jun 27, 2020

It's absolute crap. It won't do anything and you will get caught. More info here

@HLoTW
Copy link
Owner

HLoTW commented Jun 27, 2020

I didn’t see anything about the script on that site.. but I appreciate your confrontation.. this code it is shit @Eik0 but it does do something rather than nothing.. this tool is for public use what do you expect it to be over powering? If you guessed that you are wrong.. it was used on sites during a protest on Minneapolis more than one machine had this installed.. have you done any analysis yourself about the script?

@Eik0
Copy link
Author

Eik0 commented Jun 28, 2020

While I think it's a good idea in theory, you're actually putting people at risk. It certainly works on large networks, but it's pretty useless and dangerous on personal computers.
You can find details on the link I posted, under "Analysis of OP-Minneapolis DDoS tool", then the pdf file.
It's a very detailed analysis of your code but to summarize:
• your scrap function is done without proxy, so the website is getting tons of requests from the attacker ip
• you're taking public proxy lists, so there is potential for X-Forwarded-For IP address
• you're running the attack on a single thread which is.. very inneficient (max 50mbps according to the paper)
• please don't put all your user agents at the beginning of the same file, and do proper naming of your variables T_T

But once again I get the "public" thing and I like this kind of initiative, but please before releasing and claiming it's safe, think about all the potential flaws

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants