File scan report
Verdict Safe
Is AOW4.
74 of the 69 antivirus engines that checked it report clean on an unsigned 64-bit executable with minimal sandbox activity.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 69 flagged
- Flagged 0
- No detection 69
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
1 point against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Zero malicious detections across 74 engines, including 17 major clean reports. The file is unsigned and contacted one external IP, but no sandbox verdict or offensive techniques were observed.
Medium prevalence with only two submissions is consistent with a low-profile but non-malicious utility. No RAG matches or external-intel hits add further weight to a clean assessment.
What We Detected
74 antivirus engines scanned the 59 MB 64-bit executable; none returned a malicious or suspicious result. 17 major antivirus engines explicitly classified it as clean. The file is unsigned and contains no packers or high-entropy code sections.
Threat Behavior
One sandbox execution recorded a single outbound connection to IP 162.159.36.2 with no domain name. No offensive MITRE techniques, dropped files, persistence mechanisms, or malicious programs it started were observed. The rule-based rule that fired notes that direct-IP traffic can occur in legitimate installers.
What To Do Now
Keep security software enabled. If the file’s origin is untrusted, run it in a controlled environment or request the publisher to provide a signed build. No further remediation is indicated by current evidence.
- Zero detections across 74 engines
- No offensive MITRE techniques or malicious sandbox verdict
- File is unsigned
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- 1sandbox rule tag
- 1spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
Includes 1 mapped technique and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
None of the 69 antivirus engines that checked it flag it; no publisher signature.
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.
File fingerprint
- Last analyzed
- Sep 7, 2026, 10:46 AM UTC
- SHA-256
3fae6e662397683633f5795acfeb5e68a470c66df4b79fdac943ee0c98d77d4e- SHA-1
42367bbd71e7d4b77a71197698915cd69439668a- MD5
4a51d4cc5a63388cf78b69dc9e02dbad
About this file
AOW4.exe is a Win32 EXE file of 59.1 MB.
- Type and size
- Win32 EXE · 59.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 7, 2026On VirusTotal.
- Submitted by
- 2 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 6.21 of 8
First scanned
Includes every engine result (74), PE section entropy and packers 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 AOW4.exe safe?
What is AOW4.exe?
How many antivirus engines detected AOW4.exe?
What is the SHA-256 hash of AOW4.exe?
Is it safe to run AOW4.exe?
How up to date is this analysis of AOW4.exe?
Community
Member reviews and reports for this exact file hash.