Is MOD_MENU.exe safe?
First-seen 14 MB EXE signed by unknown 'Setup Wizard' with two tier-1 detections and prior RAT-like filetype matches.
Two tier-1 engines flag the file as packed or trojan while 71 others remain silent. The signer has no history, the file is brand new, and similar filetype samples were previously rated suspicious or malicious.
0e5de4421ffe81dbb4…559f7bbd204689Recommended 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.
Two tier-1 engines flag the file as packed or trojan while 71 others remain silent. The signer has no history, the file is brand new, and similar filetype samples were previously rated suspicious or malicious.
The combination of tier-1 detections, unknown signer, and rare_new prevalence creates mixed signals that prevent a clean verdict. Similar filetype matches to known RAT families add weight toward caution. No sandbox data or contacted-host reputation is available to confirm or refute malicious behaviour.
What We Detected
4 of 75 engines flagged the sample. ESET-NOD32 and Microsoft each contributed a tier-1 detection naming VMProtect packing or Wacatac trojan. The remaining 67 engines returned undetected.
Threat Behavior
No sandbox execution data is present. The file shows high entropy sections but is not marked likely packed. No dropped children or contacted hosts were recorded.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and submit the sample to a sandbox service for runtime observation before any further assessment.
Where this verdict could be wrong1 caveat
- engines.tier1FamilyConsensus.strong=false (only 1 tier-1 engine on vmprotect)
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 triggered heuristics
- no sandbox malicious verdict available
- no dropped malicious children
- rare_new prevalence
- unknown signer with no history
- two tier-1 malicious detections
- similar filetype matches previously rated suspicious or malicious
Treat the file as untrusted pending sandbox analysis; do not run it on production systems.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 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
- 4 / 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
4 of 75 antivirus engines flagged the file, including Bkav and Elastic.
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
Category: generic-trojan
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.
4 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. 4 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- MOD_MENU.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: Setup Wizard
- Size
- 13.9 MB
- Last analyzed
- Aug 16, 2026, 10:05 AM UTC
0e5de4421ffe81dbb4d2ce91e7667b1e27695c5ea676a59e5d559f7bbd204689Safety & 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 MOD_MENU.exe safe, or is it malware?
What is MOD_MENU.exe?
How many antivirus engines detected MOD_MENU.exe?
I already downloaded and ran MOD_MENU.exe — what should I do?
How do I remove MOD_MENU.exe?
What kind of malware is MOD_MENU.exe?
Is MOD_MENU.exe digitally signed?
What is the SHA-256 hash of MOD_MENU.exe?
How up to date is this analysis of MOD_MENU.exe?
Community
Member reviews and reports for this exact file hash.