File scan report
Verdict Malicious
Is 42. zip safe? No, we rate this exact file malicious.
Classic 42.zip zip-bomb archive flagged by three major antivirus engines and researcher-curated CIRCL entry.
Strong evidence · Two or more major antivirus engines agree.
Treat the file as malicious and avoid extraction; delete it unless it is intentionally retained for isolated, controlled testing.
What to do now3 steps
This ZIP archive is harmful. Don't open or extract it, and delete it.
If you haven't opened or extracted it
Don't open or extract this archive. Delete the archive and any files you extracted from it, then empty the Recycle Bin or Trash.
If you already opened or extracted it
If you already extracted it, delete the extracted files too and run a full antivirus scan.
If a page it opened asked for a password or card details and you entered them, change that password and call your bank.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
6 of 33 flagged
- Flagged 6
- No detection 27
- No result 42
- Code signing Not applicable
- Test run Completed
- First seen 14y ago
Chapter 02
Why we think so
2 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Three major antivirus engines label the file as a zip bomb, and external intelligence confirms it matches the well-known 42.zip sample. Sandbox analysis did not produce a malicious verdict, but the file's age, prevalence, and consistent naming across sources support the malicious classification.
The file is a 42 KB ZIP archive first submitted in 2012 and widely recognized as the classic 42.zip zip bomb. Three less reliable engines (Fortinet, GData, Symantec) explicitly flag it with zip-bomb or arch-bomb labels, and the CIRCL database links the hash to a known zip-bomb collection. While the single sandbox run returned no malicious verdict and contacted-host reputation data is unavailable, the combination of major detections, researcher-curated intelligence, and long-term prevalence outweighs the dissenting signals.
What We Detected
Three less reliable engines (Fortinet, GData, Symantec) and three additional engines flag the archive as a zip bomb or arch bomb. External intelligence from CIRCL confirms the hash matches the well-known 42.zip sample stored in a zip-bomb repository.
Threat Behavior
Zip bombs are crafted archives that expand to enormous sizes when decompressed, potentially exhausting disk space or memory. The file triggered one offensive MITRE technique (T1543.002) in sandbox analysis, but the sandbox itself did not classify the sample as malicious. No malicious files it created were dropped.
What To Do Now
Do not attempt to extract or open the archive. Keep security software enabled and delete the file if it is not required for controlled testing.
Where this verdict could be wrong2 caveats
- No sandbox returned a malicious verdict and no dropped file is known to be malicious — sandbox did not classify the sample as malicious.
- No contacted-host reputation result was saved — host-reputation cross-check was not completed, so no complete malicious-host result is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Sandbox returned no malicious verdict
- No malicious files it created detected
- Three major antivirus engines flag the file as a zip bomb
- CIRCL database links the hash to a known zip-bomb collection
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 4sandbox rule tags
- 4spawned processes
- 0network contacts
- 18filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
42.zip
bbd05de19aa2af1455c0494639215898a15286d9b05073b6c4817fe24b2c36fa
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
WINWORD.EXE
"C:\Program Files (x86)\Microsoft Office\Office16\WINWORD.EXE" "C:\Users\<USER>\Desktop\moving_structure.doc" /q
Test run - Evidence 3 of 5: ProcessSeen in the test run
cmd.exe
C:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -jar "C:\Users\user\Desktop\download.jar""
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
{56EC85A0-CC4B-48DC-ADB0-ED344B1829BE} - OProcSessId.dat
C:\Users\<USER>\AppData\Local\Temp\{56EC85A0-CC4B-48DC-ADB0-ED344B1829BE} - OProcSessId.dat
Test run - Evidence 5 of 5: Written fileSeen in the test run
Normal.dotm
C:\Users\<USER>\AppData\Roaming\Microsoft\Templates\Normal.dotm
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 4 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 04
Technical details
6 of the 33 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 6
- Fortinet (major engine)Riskware/zipbomb
- GData (major engine)Archive.Mail-Bomb.ZipBomb.I81YT0
- Symantec (major engine)Trojan.Archbomb
- huorongTrojan/ZipBomb
- KingsoftWin32.Troj.zipbomb.v
- McAfeeDPUP:Archive/zipbomb.NE
File fingerprint
- Last analyzed
- Aug 31, 2026, 3:35 AM UTC
- SHA-256
bbd05de19aa2af1455c0494639215898a15286d9b05073b6c4817fe24b2c36fa- SHA-1
6c42c62696616b72bbfc88a4be4ead57aa7bc503- MD5
1df9a18b18332f153918030b7b516615
About this file
42.zip is a ZIP file of 42.8 kB.
- Type and size
- ZIP · 42.8 kB
- Signer
- Not applicable
- First seen
- Feb 28, 2012On VirusTotal.
- Submitted by
- 3,470 distinct sources
First scanned
Includes every engine result (75) and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is 42.zip malware?
What is 42.zip?
How many antivirus engines detected 42.zip?
I already downloaded and opened or extracted 42.zip — what should I do?
How do I remove 42.zip?
What kind of malware is 42.zip?
What is the SHA-256 hash of 42.zip?
How up to date is this analysis of 42.zip?
Community
Member reviews and reports for this exact file hash.