File scan report
Verdict Suspicious
Is Moon Watch. zip safe? Treat it as suspicious.
14 of the 65 antivirus engines that checked it flagged the archive, six of them major.
Why Suspicious? 14 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as suspicious; block or sandbox until contacted-host reputation and further file it created analysis are available.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open or extract it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already opened or extracted it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (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
14 of 65 flagged
- Flagged 14
- No detection 51
- No result 10
- Code signing Not applicable
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The combination of major detections, offensive MITRE techniques, and direct-IP contacts outweighs the lack of a strong family consensus and the absence of malicious files it created. Because the file was first seen on Aug 24, 2026 and has no prior history, the evidence is mixed rather than decisive. The missing contacted-hosts reputation check further limits certainty.
What We Detected
Archive contains PE, ELF and Mach-O binaries. Six tier-7 engines (Avast, AVG, Avira, F-Secure, Kaspersky, Sophos, TrendMicro) reported malicious or unwanted program labels; one engine named a WinDivert-related family. Sandbox execution recorded rundll32 loading several .NET DLLs and seven direct-IP connections.
Threat Behavior
Observed MITRE techniques include process injection (T1055), service creation (T1543.002) and defense-evasion (T1562.001). No persistence registry keys or program markers were created. Ten files it created remain unclassified.
What To Do Now
Do not execute the archive. Keep security software enabled. If the file is required, submit it to a controlled analysis environment and monitor for control-server traffic to the observed IPs.
Where this verdict could be wrong2 caveats
- engines.tier1FamilyConsensus.strong=false (only 1 engine on malwarex family)
- No dropped file is known to be malicious and 10/10 children unknown
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No malicious files it created
- No strong major family consensus
- No external-intel hits
- Six major antivirus engines flagged the sample
- Direct-IP traffic to seven addresses
- Rare and file
6 sources checked · 5 complete · 1 partial. 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- 15sandbox rule tags
- 15spawned processes
- 7network contacts
- 15filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Checked whether it was running on a test computer.
Moderate concern: Hid files or windows on the test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Talked to servers over the internet during 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 code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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.
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 7: FileSeen in the test run
MoonWatch.zip
f1106c03fb393ad4fe62227639934d4994dde2d194c58847bd98d571e2f2b14a
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
rundll32.exe
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\MoonWatch 1.1.1/ComposableAsync.Core.dll",#1
Test run - Evidence 3 of 7: ProcessSeen in the test run
rundll32.exe
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\MoonWatch 1.1.1/DotNetBungieAPI.dll",#1
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
unarchiver.log
C:\Users\user\AppData\Local\Temp\unarchiver.log
Test run - Evidence 5 of 7: Written fileSeen in the test run
z04c35i0.pk4
C:\Users\user\AppData\Local\Temp\z04c35i0.pk4
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
23.11.32.159
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
184.28.164.23
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 15 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
14 of the 65 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 14
- Avast (major engine)Win32:MalwareX-gen [Misc]
- AVG (major engine)Win32:MalwareX-gen [Misc]
- Avira (major engine)TR/W32.Agent
- F-Secure (major engine)Trojan.TR/W32.Agent
- Kaspersky (major engine)not-a-virus:HEUR:RiskTool.Multi.WinDivert.gen
- Sophos (major engine)Generic Reputation PUA (PUA)
- TrellixENS (major engine)Artemis!3E8C97589DB7
- TrendMicro (major engine)Trojan.Win32.WINDIVERT.USBLHK26
File fingerprint
- Last analyzed
- Aug 25, 2026, 6:43 AM UTC
- SHA-256
f1106c03fb393ad4fe62227639934d4994dde2d194c58847bd98d571e2f2b14a- SHA-1
dcb0783f4b906a1d14e85c184a3141743cb79962- MD5
77ea8b3f792344d5ca273f9521ef2eca
About this file
MoonWatch.zip is a ZIP file of 28.0 MB.
- Type and size
- ZIP · 28.0 MB
- Signer
- Not applicable
- First seen
- Aug 24, 2026On VirusTotal.
- Submitted by
- 2 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is MoonWatch.zip safe, or is it malware?
What is MoonWatch.zip?
How many antivirus engines detected MoonWatch.zip?
I already downloaded and opened or extracted MoonWatch.zip — what should I do?
What is the SHA-256 hash of MoonWatch.zip?
How up to date is this analysis of MoonWatch.zip?
Community
Member reviews and reports for this exact file hash.