Is Mod_Menu_v2.7.zip safe?
The archive drew three antivirus detections and showed LSASS-targeting activity plus defense impairment, but lacks strong family consensus or corroborating threat-intelligence matches.
Three of 75 engines flagged this archive, including one tier-1 detector, while sandbox evidence indicates LSASS targeting and defense impairment. Those behaviors warrant caution despite broad engine silence, no malicious sandbox verdict, and no corroborating external-intelligence hits.
0d6c9de0135c5fe5d5…7af80377fce2c0Recommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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.
Three of 75 engines flagged this archive, including one tier-1 detector, while sandbox evidence indicates LSASS targeting and defense impairment. Those behaviors warrant caution despite broad engine silence, no malicious sandbox verdict, and no corroborating external-intelligence hits.
The archive was detected by 3 of 75 engines, with TrendMicro-HouseCall providing the sole tier-1 finding and no strong family consensus. Runtime observation recorded offensive techniques T1485 and T1562.001, and a heuristic specifically associated process activity with LSASS, which can indicate credential-access behavior. However, the completed sandbox did not issue a malicious verdict, and no persistence or network contacts were recorded during that run. Ten dropped children were inspected without a malicious result, but every child remained unclassified, so this is not strong reassurance. The file is also broadly submitted and more than a year old, yet no curated threat-intelligence source corroborated a known family. Together, these are materially concerning but mixed signals rather than conclusive family identification.
What We Detected
Three of 75 antivirus engines flagged the ZIP archive. TrendMicro-HouseCall labeled it Trojan.Win64.Gen.TL0101F726YW, SentinelOne reported a suspicious archive, and Bkav supplied a generic malware label. Only one tier-1 engine supported the named label, so there is no strong independent family consensus.
Threat Behavior
One completed sandbox run recorded T1485 and T1562.001, including behavior associated with data destruction and impairing defenses. The MalwareTips.Synth.CredentialDumper heuristic also linked observed process activity to lsass.exe, a sensitive Windows credential process. The sandbox did not issue a malicious verdict, record persistence, or observe network contacts; because contactedHosts is unavailable, no complete host-reputation result exists. All ten dropped children remain unclassified despite no child being explicitly identified as malicious.
What To Do Now
Do not run the executable from this archive on a production or personal system. Keep endpoint protection enabled, quarantine the archive, and obtain the mod only from a verified official source; if it was already executed, run a full security scan and review credential exposure.
Where this verdict could be wrong4 caveats
- Only 3/75 engines detected the archive, and 16/17 reporting tier-1 engines did not flag it.
- behaviour.hasMaliciousSandboxVerdict=false, although the LSASS-related observation remains concerning.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false; absence of hits may reflect coverage limitations.
- droppedChildren.hasMaliciousChild=false, but all 10 inspected children have unknown verdicts.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 3 of 75 engines flagged the archive.
- The tier-1 family consensus is not strong and has only one agreeing engine.
- The completed sandbox did not issue a malicious verdict.
- No persistence indicators or network contacts were recorded during the sandbox run.
- No CIRCL, MalwareBazaar, or YARAify match was returned.
- TrendMicro-HouseCall produced a tier-1 generic Trojan detection.
- Sandbox evidence associated activity with lsass.exe.
- Offensive technique T1562.001 indicates possible defense impairment.
- Offensive technique T1485 indicates possible data-destruction behavior.
- The archive contains a portable executable with debugging-environment detection and long-sleep tags.
- All 10 dropped children remain unclassified.
Quarantine the archive and avoid executing its contents unless the publisher and download channel can be independently verified. Keep security protection enabled and perform a full scan if it has already run.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 10MITRE ATT&CK techniques
- 15spawned processes
- 0network contacts
- 35filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
Mod_Menu_v2.7.zip
0d6c9de0135c5fe5d569bb5a3ad1d0c1b5cac52d23d3a4a52b7af80377fce2c0
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\Mod Menu v2.7.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
VCRUNTIME140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI64922\VCRUNTIME140.dll
04Isolated runtime analysis - Written fileObserved
VCRUNTIME140_1.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI64922\VCRUNTIME140_1.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\VCRUNTIME140_1.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\_asyncio.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\_cffi_backend.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\base_library.zip
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\clr_loader\ffi\dlls\amd64\ClrLoader.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\clr_loader\ffi\dlls\amd64
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\clr_loader\ffi\dlls\x86\ClrLoader.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI64922\clr_loader\ffi\dlls\x86
- \BaseNamedObjects\Local\SM0:4984:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:4984:120:WilError_03
- \BaseNamedObjects\Local\ZonesCacheCounterMutex
- \BaseNamedObjects\Local\ZonesLockedCacheCounterMutex
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 965f199679afa9b31d53…f12771Never scannednever seen before
- 6a99bc0128e0c7d6cbbf…cbc6c8Never scannednever seen before
- 3b75c4cf714e7e8092f4…32000eNever scannednever seen before
- 1430e4a2ed19eda84066…9ecbfeNever scannednever seen before
- eff52743773eb550fcc6…7b280aNever scannednever seen before
- ccfffddcd3defb8d8990…5f27d7Never scannednever seen before
- 08050f94efe7bdd9d7cb…29a5dbNever scannednever seen before
- ceebae7b8927a3227e53…2f1508Never scannednever seen before
- 37fedcffbf73c4eb9f05…d28e0bNever scannednever seen before
- 18c35ba9b4c29652269f…dbfbc9Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 3 / 75engines flagged
- 1,611sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
3 of 75 antivirus engines flagged the file, including Bkav and SentinelOne.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 1,611 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 1,783 times from 1,611 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Mod_Menu_v2.7.zip — 0d6c9de0135c5fe5d569bb5a3ad1d0c1b5cac52d23d3a4a52b7af80377fce2c0
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\Mod Menu v2.7.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: VCRUNTIME140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI64922\VCRUNTIME140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: VCRUNTIME140_1.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI64922\VCRUNTIME140_1.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
3 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Mod_Menu_v2.7.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 11.3 MB
- Last analyzed
- Sep 18, 2026, 10:40 PM UTC
0d6c9de0135c5fe5d569bb5a3ad1d0c1b5cac52d23d3a4a52b7af80377fce2c0Safety & 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 open or extract 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 archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- 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_v2.7.zip safe, or is it malware?
What is Mod_Menu_v2.7.zip?
How many antivirus engines detected Mod_Menu_v2.7.zip?
I already downloaded and opened or extracted Mod_Menu_v2.7.zip — what should I do?
How do I remove Mod_Menu_v2.7.zip?
What kind of malware is Mod_Menu_v2.7.zip?
What is the SHA-256 hash of Mod_Menu_v2.7.zip?
How up to date is this analysis of Mod_Menu_v2.7.zip?
Community
Member reviews and reports for this exact file hash.