Is Mod Menu v2.7.exe safe?
Unsigned executable with LSASS access, direct-IP C2, and mixed AV detections.
Eight of 75 engines flag the file; one tier-1 labels it Trojan.Win64.Gen.TL0101F726YW. Sandbox shows LSASS credential-dumping behaviour and direct-IP traffic to two external hosts. The file remains unsigned and carries community tags linking it to multiple malware families.
ecd96bcd37799b50fc…00bd159c67df5aRecommended 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.
Eight of 75 engines flag the file; one tier-1 labels it Trojan.Win64.Gen.TL0101F726YW. Sandbox shows LSASS credential-dumping behaviour and direct-IP traffic to two external hosts. The file remains unsigned and carries community tags linking it to multiple malware families.
The single tier-1 detection and two offensive MITRE techniques outweigh the lack of strong family consensus. Unsigned status and LSASS access are strong risk indicators for a purported game mod. Direct-IP contact without domains adds suspicion, though the absence of a completed host-reputation check prevents a definitive malicious call. The file's age and moderate prevalence keep it out of the malicious band but still warrant caution.
What We Detected
8 of 75 engines report malicious, including TrendMicro-HouseCall (tier-1) naming Trojan.Win64.Gen.TL0101F726YW. Sandbox execution revealed LSASS memory access and two direct-IP connections (20.99.133.109, 23.55.140.42). The binary is unsigned and contains PyInstaller artifacts.
Threat Behavior
Offensive MITRE techniques T1485 (data encrypted for impact) and T1562.001 (impair defenses) were observed. Community annotations link the sample to Black Basta, Cobalt Strike, and multiple stealers. No dropped children were flagged malicious.
What To Do Now
Do not execute the file. Keep endpoint protection enabled. If the file was downloaded from an untrusted source, delete it and scan the system with current signatures.
Where this verdict could be wrong1 caveat
- prevalence.classification=common_old with 902 submitters — file has been circulating for 378 days without tier-1 consensus.
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 tier-1 family consensus
- Common-old prevalence (902 submitters)
- Unsigned executable
- LSASS credential access observed
- Direct-IP external connections
- Community tags reference known malware families
Treat as untrusted; avoid execution and delete the sample.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete8 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules 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
- 18MITRE ATT&CK techniques
- 15spawned processes
- 3network contacts
- 40filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
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: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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.exe
ecd96bcd37799b50fccecd126b92decff7eaf7b0bfc688700900bd159c67df5a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\chrome_Unpacker_BeginUnzipping3144_690324175\qualification_app.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
VCRUNTIME140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI39282\VCRUNTIME140.dll
04Isolated runtime analysis - Written fileObserved
VCRUNTIME140_1.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI39282\VCRUNTIME140_1.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.133.109
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.55.140.42
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 20.99.133.109
- 23.55.140.42
- 192.168.0.2
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\VCRUNTIME140_1.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\_asyncio.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\_cffi_backend.cp313-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\base_library.zip
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\clr_loader\ffi\dlls\amd64\ClrLoader.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\clr_loader\ffi\dlls\amd64
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\clr_loader\ffi\dlls\x86\ClrLoader.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI39282\clr_loader\ffi\dlls\x86
- Local\WERReportingForProcess3988
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\4e3836cd-d599-461b-836c-070bf1478c19
- Global\OneSettingQueryMutex+compat+encapsulation
- __OMADM_NAMED_MUTEX__
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
- decc3b8aad960b8e1c23…613de6Never 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
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 8 / 75engines flagged
- 902sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
8 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 902 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 948 times from 902 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Mod Menu v2.7.exe — ecd96bcd37799b50fccecd126b92decff7eaf7b0bfc688700900bd159c67df5a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\chrome_Unpacker_BeginUnzipping3144_690324175\qualification_app.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: VCRUNTIME140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI39282\VCRUNTIME140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: VCRUNTIME140_1.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI39282\VCRUNTIME140_1.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 20.99.133.109 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.55.140.42 — Contact observed during runtime.
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.
Sandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence20.99.133.109 · 23.55.140.42
8 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
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.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 11.6 MB
- Last analyzed
- Aug 15, 2026, 11:14 AM UTC
ecd96bcd37799b50fccecd126b92decff7eaf7b0bfc688700900bd159c67df5aSafety & 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 v2.7.exe safe, or is it malware?
What is Mod Menu v2.7.exe?
How many antivirus engines detected Mod Menu v2.7.exe?
What should I do if I already ran Mod Menu v2.7.exe?
How do I remove Mod Menu v2.7.exe?
What kind of malware is Mod Menu v2.7.exe?
What is the SHA-256 hash of Mod Menu v2.7.exe?
How up to date is this analysis of Mod Menu v2.7.exe?
Community
Member reviews and reports for this exact file hash.