File scan report

Verdict Suspicious

Analyzed , 2 months ago

Is MoonWatch.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.

Don't open or extract it until you know where it came from

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

  1. Don't open or extract it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. 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

  1. 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.

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
FileMoonWatch.zip28.0 MBSHA-256 f1106c03fb39…f2b14a
  • Code signing Not applicable
  • Test run Completed
  • First seen 2mo ago
14 of the 65 antivirus engines that checked it flag it, including Kaspersky and Avast.

Chapter 02

Why we think so

3 points against it and 3 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

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.

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.

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.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      MoonWatch.zip

      f1106c03fb393ad4fe62227639934d4994dde2d194c58847bd98d571e2f2b14a

      Uploaded file
  2. Processes

    What ran

    2
    1. 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
    2. 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
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      unarchiver.log

      C:\Users\user\AppData\Local\Temp\unarchiver.log

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      z04c35i0.pk4

      C:\Users\user\AppData\Local\Temp\z04c35i0.pk4

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      23.11.32.159

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      184.28.164.23

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 14 of 65 engines flagged it · 10 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial7 hosts contacted in the test run had no completed reputation check Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

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
6 more in the full engine list

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

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is MoonWatch.zip safe, or is it malware?
MoonWatch.zip is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 14 of the 65 antivirus engines that checked it flag it. Don't open or extract it unless you're sure where it came from. If you need what's inside, download it again from the original website.
What is MoonWatch.zip?
MoonWatch.zip is a ZIP archive, about 28.0 MB. VirusTotal first saw it on Aug 24, 2026.
How many antivirus engines detected MoonWatch.zip?
14 of the 65 antivirus engines that checked it flag MoonWatch.zip, including Kaspersky and Avast. We weigh which engines flagged it and what else the scan found, not just the count.
I already downloaded and opened or extracted MoonWatch.zip — what should I do?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of MoonWatch.zip?
The SHA-256 fingerprint of MoonWatch.zip is f1106c03fb393ad4fe62227639934d4994dde2d194c58847bd98d571e2f2b14a, and its MD5 is 77ea8b3f792344d5ca273f9521ef2eca. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of MoonWatch.zip?
This report reflects the scan on Aug 25, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Recent reports on other files with the same rating.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.