Does this checker detect every ZIP bomb?
No. It checks directory structures and known budget violations. Extreme compression ratios, excessive entry counts or ambiguous headers produce warnings or processing blocks. Nested archives are not recursively cleared.
How to use the check
- Choose the ZIP without extracting it first.
- Review paths, technical details and inspection coverage. Detailed path and name findings cover the first 300 entries; the tree preview shows at most 500.
- If selective export is offered, read its omissions and manifest. Structural errors or encryption block that export.
Exact limits
At most 1,000 entries, 25 MiB per entry, 32 MiB declared total output and compression ratio 100. ZIP64 and ambiguous legacy filename encodings are unsupported. Selective ZIP export contains a documented selection with a manifest; retained files can still be harmful.
Reproducible synthetic example
invoice.pdf.exe contains only harmless text in this example. Its name still triggers zip.active and name.extensions. ZIP inspection does not execute the file or analyze its contents as a program.
The findings come from an actual local scan of this test file. Download it and choose it in the scanner. No real personal data or malware.
Download test file: paths-demo.zipExample inspection coverage: partial.
Interpret the result
Risk and inspection coverage are separate statements. complete means analyzed within the defined inspection scope. Green does not establish the absence of malware. partial, unavailable or failed mean inspection is limited, unsupported or unsuccessful.
- Check a ZIP before extracting: paths, extensions and ZIP bombs
- Inspection method and next steps
- More guides
Responsible operator: Tom Silas Helmke, operator of ScanBeforeOpen. Content revised: .