Is not_malware.exe safe?
Single tier-1 detection on a brand-new unsigned executable with no further corroboration.
One high-trust engine flagged the file as Trojan:Win32/Wacatac.B!ml while 68 others returned clean. The sample is unsigned, appeared today, and has no sandbox or external-intel results.
108ef649b237d592d9…24574c9786a5a5Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
One high-trust engine flagged the file as Trojan:Win32/Wacatac.B!ml while 68 others returned clean. The sample is unsigned, appeared today, and has no sandbox or external-intel results.
A lone tier-1 detection without family consensus is insufficient for a malicious verdict, yet the complete absence of signing, zero prior history, and rarity keep the file out of the safe category. Similar-hash matches are weak because they involve signed installers. No runtime or external-intel data exists to resolve the ambiguity.
What We Detected
Microsoft flagged the sample as Trojan:Win32/Wacatac.B!ml; 68 of 75 engines returned clean. The file is a 150 kB unsigned 64-bit PE submitted for the first time today.
Threat Behavior
No sandbox execution data, no contacted hosts, and no external-intel hits are available. The single detection remains uncorroborated.
What To Do Now
Do not run the file. Keep endpoint protection enabled and wait for additional engine coverage or sandbox results before trusting it.
- 68/75 engines clean
- no sandbox malicious verdict
- unsigned executable
- rare_new prevalence
- single tier-1 detection
Treat the file as untrusted until further engine or sandbox evidence appears.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 1 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 75 antivirus engines flagged the file, including Microsoft.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
1 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 1 antivirus detection make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- not_malware.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 147.3 KB
- Last analyzed
- Sep 5, 2026, 4:27 PM UTC
108ef649b237d592d960d2a8009c37792c73f09dbaccd3d91b24574c9786a5a5Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is not_malware.exe safe, or is it malware?
What is not_malware.exe?
How many antivirus engines detected not_malware.exe?
What should I do if I already ran not_malware.exe?
How do I remove not_malware.exe?
What is the SHA-256 hash of not_malware.exe?
How up to date is this analysis of not_malware.exe?
Community
Member reviews and reports for this exact file hash.