I've done this without compression but just sending infinite data. On some days I've sent a TB to a single IP address... Might be an idea to combine this. I'd assume the resulting gzip file here contains a repeating pattern that you can generate on the fly?
How to defend your website with ZIP bombs (2017)
11–20 of 79 posts
Re: How to defend your website with ZIP bombs (2017)
#12Is it legal to purposefully distribute a malicious payload as a booby trap?
digital castle doctrine or whatever.
Re: How to defend your website with ZIP bombs (2017)
#13Re: How to defend your website with ZIP bombs (2017)
#14Is it legal to purposefully distribute a malicious payload as a booby trap?
Edit: spelling. I’m old school and used to typing on my computer. It’s getting repaired and all I’ve got is my phone. /rant
Re: How to defend your website with ZIP bombs (2017)
#15If I recall correctly, HTTP clients do not need to care about Content-Encoding at all and can choose to just not do anything with your ZIP bomb. To really hit them, you will want to do this at the Transfer-Encoding level.
Re: How to defend your website with ZIP bombs (2017)
#16The title says that you can "defend" your webpage, but it is not clear how it "defends" against anything. The only thing you possibly achieve is that every now and then, someone with an automated scanner (which may be an attacker, or may be a security researcher or service) will see his tool crash or consume large amounts of resources.
You're spending time trying to annoy attackers that you should probably just ignore. If you really worry that someone running some automated scanner against your webpage causes you any harm, you probably should spend your time with something different than building zip bombs, and instead fix the security problems you have.
Re: How to defend your website with ZIP bombs (2017)
#17Re: How to defend your website with ZIP bombs (2017)
#18Is it legal to purposefully distribute a malicious payload as a booby trap?
Re: How to defend your website with ZIP bombs (2017)
#19In essence a hacker would have to pay before attempting to hack the ssh endpoint. Of course the admin would have to pay too but the money would end up on his/her wallet.
Quite ingenious if you ask me.
Re: How to defend your website with ZIP bombs (2017)
#20People have been coming up with ideas like that regularly. I'm not a fan. The title says that you can "defend" your webpage, but it is not clear how it "defends" against anything. The only thing you possibly achieve is that every now and then, someone with an automated scanner (which may be an attacker, or may be a security researcher or service) will see his tool crash or consume large amounts of resources. You're s…