README.md

gbombd

ZIP 💣 httpd. Sends a ZIP bomb if it recognizes the client as a bot or a scanner. You're going to find User Agents inside the code so you can add more to those. It simply creates a big file with repetitive data (in this case zeros), so the compresion is more effective but when the client decompresses the gzip'ed data it will consume all his CPU rendering it useless.

Got the idea from here.

Compile

Build it using the Go complier (you don't need to go get anything):

$ go build -v -o gbombd gbombd.go

Using this thing

$ ./gbombd -help
Usage of ./gbombd:
  -filename string
    	Filename to create and use (default "bomb.gz")
  -port int
    	HTTPd port to use (default 80)
  -preserve
    	Preserve the bomb file for future use
  -size int
    	Size of file to create (default 10240)
  -verbose
    	Be verbose

By default it will open port 80 and you will need more privileges for that. The default file size is 10G and name bomb.gz. The file will be removed once the application exits but you can avoid that by using the -preserve switch.

$ ./gbombd -verbose -size 1024 -port 81 -preserve
[+] Creating file: bomb.gz. Wait...
[+] Done!
[+] Serving data on port 81/TCP
[+] Serving 1042079 bytes gzipped to [::1]:34062 (UA:"curl")
[i] Catched signal: interrupt. Exiting...
[+] Removing bomb file: bomb.gz

Tests

1. curl: Never stops loading content and CPU usage goes up.
2. Nikto: ignores the data.
3. sqlmap: same as curl.
4. thc-hydra: same as sqlmap but CPU usage is low.

Why? Go is fun and annoying some people is even funnier.