I use Zip Bombs to Protect my Server

The article writer kind of complains that they're having to serve a 10MB file, which is the result of the gzip compression. If that's a problem, they could switch to bzip2. It's available pretty much everywhere that gzip is available and it packs the 10GB down to 7506 bytes.
That's not a typo. bzip2 is way better with highly redundant data.
- I believe he's returning a gzip HTTP response stream, not just a file payload that the requester then downloads and decompresses.
  Bzip isn't used in HTTP compression.
  
  Brotli is an option, and it's comparable to Bzip. Brotli works in most browsers, so hopefully these bots would support it.
  I just tested it, and a 10G file full of zeroes is only 8.3K compressed. That's pretty good, though a little bigger than BZip.
  
  For scrapers that not just implementing HTTP, but are trying to extract zip files, you can possibly drive them insane with zip quines: https://github.com/ruvmello/zip-quine-generator or otherwise compressed files that contain themselves at some level of nesting, possibly with other data so that they recursively expand to an unbounded ("infinite") size.
- Brotli gets it to 8.3K, and is supported in most browsers, so there's a chance scrapers also support it.
  
  Gzip encoding has been part of the HTTP protocol for a long time and every server-side HTTP library out there supports it, and phishing/scrapper bots will be done with server-side libraries, not using browser engines.
  Further, judging by the guy's example in his article he's not using gzip with maximum compression when generating the zip bomb files: he needs to add -9 to the gzip command line to get the best compression (but it will be slower). (I tested this and it made no difference at all).
- TIL why I'm gonna start learning more about bzip2. Thanks!
- zstd is a significantly better option than anything else available unless you need something specific for a specific reason: https://github.com/facebook/zstd?tab=readme-ov-file#benchmarks
  LZ4 is likely better than zstd, but it doesn't have wide usability yet.
  
  You might be thinking of lzip rather than lz4. Both compress, but the former is meant for high compression whereas the latter is meant for speed. Neither are particularly good at dealing with highly redundant data though, if my testing is anything to go by.
  Either way, none of those are installed as standard in my distro. xz (which is lzma based) is installed as standard but, like lzip, is slow, and zstd is still pretty new to some distros, so the recipient could conceivably not have that installed either.
  bzip2 is ancient and almost always available at this point, which is why I figured it would be the best option to stand in for gzip.
  As it turns out, the question was one of data streams not files, and as at least one other person pointed out, brotli is often available for streams where bzip2 isn't. That's also not installed by default as a command line tool, but it may well be that the recipient, while attempting to emulate a browser, might have actually installed it.

When I was serving high volume sites (that were targeted by scrapers) I had a collection of files in CDN that contained nothing but the word "no" over and over. Scrapers who barely hit our detection thresholds saw all their requests go to the 50M version. Super aggressive scrapers got the 10G version. And the scripts that just wouldn't stop got the 50G version.
It didn't move the needle on budget, but hopefully it cost them.
- How do you tell scrapers from regular traffic?
  
  Most often because they don't download any of the css of external js files from the pages they scrape. But there are a lot of other patterns you can detect once you have their traffic logs loaded in a time series database. I used an ELK stack back in the day.

Sadly about the only thing that reliably helps against malicious crawlers is Anubis
https://anubis.techaro.lol/
- That URL is telling me "Invalid response". Am I a bot?
  
  I’m sorry you had to find out this way.
  
  Now you know why your mom spent so much time with the Amiga
  
  https://anubis.techaro.lol/docs/user/known-broken-extensions
  If you have JShelter installed, it breaks the proof of work from anubis
  
  Probably.
  
  You're using a VPN, right?
- Neat
- I don't really like this approach, not just because I was flagged as a bot, but because I don't really like captchas. I swear I'm not a bot guys!
  
  That’s the reason I say ‚sadly‘. It’s definitely not good. But since everything else fails, this is what currently remains.

Before I tell you how to create a zip bomb, I do have to warn you that you can potentially crash and destroy your own device.
LOL. Destroy your device, kill the cat, what else?
- destroy your device by... having to reboot it. the horror! The pain! The financial loss of downtime!
- It'll email your grandmother all if your porn!
  
  Ah yes, the infamous "stinky cheese" email virus. Who knew zip bombs could be so destructive. It erased all of the easter eggs off of my DVDs.
  
  Haven’t thought about that Weird Al song in a while
  
  The horrors of having your TV record Gigli!
  
  outstanding reference

And if you want some customisation, e.g. some repeating string over and over, you can use something like this:

yes "b0M" | tr -d '\n' | head -c 10G | gzip -c > 10GB.gz
yes repeats the given string (followed by a line feed) indefinitely - originally meant to type "yes" + ENTER into prompts. tr then removes the line breaks again and head makes sure to only take 10GB and not have it run indefinitely.
If you want to be really fancy, you can even add some HTML header and footer to some files like header and footer and then run it like this:

yes "b0M" | tr -d '\n' | head -c 10G | cat header - footer | gzip -c > 10GB.gz

I've been thinking about making an nginx plugin that randomizes words on a page to poison AI scrapers.
- There are "AI mazes" that do that.
  I remember reading and article about this but haven't found it yet
  
  The one below, named Anubis, is the one I heard about. Come back to the thread and check the link.
- https://zadzmo.org/code/nepenthes/
  
  That is a very interesting git repo. Is this just a web view into the actual git folder?
- If you have the time, I think it's a great idea.

I'd be amazed if this works, since these sorts of tricks have been around since dinosaurs ruled the Earth, and most bots will use pretty modern zip libraries which will just return "nope" or throw an exception, which will be treated exactly the same way any corrupt file is - for example a site saying it's serving a zip file but the contents are a generic 404 html file, which is not uncommon.
Also, be careful because you could destroy your own device? What the hell? No. Unless you're using dd backwards and as root, you can't do anything bad, and even then it's the drive contents you overwrite, not the device you "destroy".
- On the other hand, there are lots of bots scraping Wikipedia even though it's easy to download the entire website as a single archive.
  So they're not really that smart....
- Yeah, this article came across as if written by a complete beginner. They mention having their WordPress hacked, but failed to admit it was because they didn't upgrade the install.

Anyone who writes a spider that's going to inspect all the content out there is already going to have to have dealt with this, along with about a bazillion other kinds of oddball or bad data.
- Competent ones, yes. Most developers aren't competent, scraper writers even less so.
  
  That's true. Scrapping is a gold mine for the people that don't know. I worked for a place which crawls the internet and beyond (fetches some internal dumps we pay for). There is no chance a zip bomb would crash the workers as there are strict timeouts and smell tests (even if a does it will crash an ECS task at worst and we will be alerted to fix that within a short time). We were as honest as it gets though, following GDPR, honoring the robots file, no spiders or scanners allowed, only home page to extract some insights.
  I am aware of some big name EU non-software companies very interested in keeping an eye on some key things that are only possible with scraping.
- That's the usual case with arms races: Unless you are yourself a major power, odds are you'll never be able to fully stand up to one (at least not on your own, but let's not stretch the metaphor too far). Often, the best you can do is to deterr other, minor powers and hope major ones never have a serious intent to bring you down.
  In this specific case, the number of potential minor "attackers" and the hurdle for "attack" mKe it attractive to try to overwhelm the amateurs at least. You'll never get the pros, you just hope they don't bother you too much.
- If you have billions of targets to scan, there's generally no need to handle each and every edge case. Just ignoring what you can't understand easily and jumping on to the next target is an absolutely viable strategy. You will never be able to process everything anyway.
  Of course, it changes a bit if some of these targets actually make your bot crash. If it happens to often, you will want to harden your bot against it. Then again, if it just happens every now and then, it's still much easier to just restart and continue with the next target.

First off, be very careful with bs=1G as it may overload the RAM. You will want to set count accordingly
- Yup, use something sensible like 10M or so.
  
  I would normally go much lower,
  bs=4K count=262144 which creates 1G with 4K block size

Probably only works for dumb bots and I'm guessing the big ones are resilient to this sort of thing.
Judging from recent stories the big threat is bots scraping for AIs and I wonder if there is a way to poison content so any AI ingesting it becomes dumber. e.g. text which is nonsensical or filled with counter information, trap phrases that reveal any AIs that ingested it, garbage pictures that purport to show something they don't etc.
- https://arstechnica.com/tech-policy/2025/01/ai-haters-build-tarpits-to-trap-and-trick-ai-scrapers-that-ignore-robots-txt/
- When it comes to attacks on the Internet, doing simple things to get rid of the stupid bots means kicking 90% of attacks out. No, it won't work against a determined foe, but it does something useful.
  Same goes for setting SSH to a random port. Logs are so much cleaner after doing that.
  
  Setting a random SSH port and limiting it to 3/min saw failed login attempts fall by 99% and jailed IPs fall to 0.
- There have been some attempts in that regard, I don’t remember the names of the projects, but there were one or two that’d basically generate a crapton of nonsense to do just that. No idea how well that works.
  
  https://blog.cloudflare.com/declaring-your-aindependence-block-ai-bots-scrapers-and-crawlers-with-a-single-click/
  https://xeiaso.net/blog/2025/anubis/
  https://github.com/jrwren/nepenthes
- I don't know as to poisoning AI, but one thing that I used to do was to redirect any suspicious bots or ones that were hitting their server too much to a simple html page with no JS or CSS or forward links. Then they used to go away.
- https://zadzmo.org/code/nepenthes/

This reminds me of shitty FTP sites with ratios when I was on dial-up. I used to push them files full of null characters with filenames that looked like actual content. The modem would compress the upload as it transmitted it which allowed me to upload the junk files at several times the rate of a normal file.
- that is pretty darn clever
  I use a torrent client that will lie on the upload (x10 or x11, or a myriad of other options) so as to satisfy the upload ratio requirement of many members only torrent communities

Funny part is many of us crusty old sysadmins were using derivatives of this decades ago to test RAID-5/6 sequencial reads and write speeds.

At least in germany having one of these on your system is illegal
- Out of curiosity, what is illegal about it, exactly?
  
  I mean i am not a lawyer.
  In germany we have § 303 b StGB. In short it says if you hinder someone elses dataprocessing through physical means or malicous data you can go to jail for up to 3 years . If it is a major process for someone you can get up to 5 and in major cases up to 10 years.
  So if you have a zipbomb on your system and a crawler reads and unpacks it you did two crimes. 1. You hindered that crawlers dataprocessing 2. Some isp nodes look into it and can crash too. If the isp is pissed of enough you can go to jail for 5 years. This applies even if you didnt crash them due to them having protection against it, because trying it is also against the law.
  Having a zipbomb is part of a gray area. Because trying to disrupt dataprocessing is illegal, having a zipbomb can be considered trying, however i am not aware of any judgement in this regard
  Edit: btw if you password protect your zipbomb, everything is fine
- Maybe bots shouldn't be trying to install malicious code? Sucks to suck.
  
  Still illegal. Not immoral, but a lot of our laws aren't built on morality.
- Illegal to publically serve or distribute.

Have you ever heard of sparse files, and how Linux and Windows deal with zips of it? You'll love this.

let me try..

Looks fine to me. Only 1 CPU core I think was 100%.

    
10+0 records in
10+0 records out
10737418240 bytes (11 GB, 10 GiB) copied, 28,0695 s, 383 MB/s

ow.. now the idea is to unzip it right?

nice idea:

    
if (ipIsBlackListed() || isMalicious()) {
    header("Content-Encoding: deflate, gzip");
    header("Content-Length: "+ filesize(ZIP_BOMB_FILE_10G)); // 10 MB
    readfile(ZIP_BOMB_FILE_10G);
    exit;
}

Interesting. I wonder how long it takes until most bots adapt to this type of "reverse DoS".
- Then we'll just be more clever as well. It's an arms race after all.

I want to know he they built that visualization

How I read that code:
"If the dev folder's bullshit is equal to 1 gram..."

❤️

This is why I use things like Docusaurus to generate static sites. Vulnerability injections are pretty hard when there's no code to inject into.

macOS compresses its memory. Does this mean we'll see bots running on macOS now?
- Linux and Windows compress it too, for 10 years or more. And that's not how you avoid zip bombs, just limit how much you uncompress and abort if it's over that limit.
  
  I was going to say the same thing.
- Is it immune to zip bombs?
  
  All I know is it compresses memory. The mechanism mentioned here for ZIP bombs to crash bots is to fill up memory fast with repeating zeroes.
- No, but that's an interesting question. Ultimately it probably comes down to hardware specs. Or depending on the particular bot and it's env the spec of the container it's running in
  Even with macos's style of compressing inactive memory pages you'll still have a hard cap that can be reached with the same technique (just with a larger uncompressed file)
  
  How long would it take to be considered an inactive memory page? Does OOM conditions immediately trigger compression, or would the process die first?