A Better Zip Bomb

The tiny ‘trap’ file stirring revenge fantasies and IT panic

TLDR: A researcher unveiled a tiny zip file that explodes into huge data on unzip—turning megabytes into terabytes. Commenters split between pranky revenge jokes, fears of web-delivered “bombs,” and whether tools like Debian’s unzip can detect and block them, debating how ready defenses are for this old-but-updated trick.

A researcher just showed off a “better zip bomb,” a teeny zip file that blows up into a ridiculous amount of data the moment you unzip it—no tricks inside tricks required. Think 10 megabytes inflating to 281 terabytes in one go. Because it uses plain zip tech that most apps understand, the community reaction swung from awe to panic. One commenter relived a layoff and joked they’d have loved to email this to their condescending ex-boss. Others worried about the internet angle: could a website send a compressed response that detonates right in your browser?

Security-minded folks pushed back with reality checks. Veterans asked, “How do you even spot one?” and Linux users chimed in that Debian’s unzip actually screams “invalid zip… possible bomb” and bails out—right after dumping a random 21MB file named “0,” which became an instant meme. Meanwhile, the “this is old” crowd noted the write-up dates to 2019, only for defenders to clap back: it’s been updated through 2023 and tangled with the new .zip web addresses, like 42.zip.

So the vibe? Half prankster, half alarm bell. People fantasize about petty revenge, tinkerers dream up protocol-level bombs, and pragmatists argue tools can and should say “nope.”

Key Points

  • The article outlines a non-recursive zip bomb that expands fully after a single decompression by overlapping files within a ZIP.
  • Using DEFLATE, the technique achieves quadratic growth in output size and compression ratios over 28 million (10 MB → ~281 TB).
  • Zip64 enables even larger expansions (~4.5 PB) but reduces compatibility with some ZIP parsers.
  • Comparisons show the method’s non-recursive expansion greatly exceeds classic examples like 42.zip and ZIP quines.
  • The author documents the 2023 appearance of the 42.zip domain under the .zip TLD and differences among 42.zip versions based on size and timestamps.

Hottest takes

“If only I knew about this then...” — kleiba
“Can we have a zip bomb... with a compressed http response” — cuechan
“How does one detect a zip bomb?” — 542458
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.