Our call: Is CNModFixerV2.1.exe safe?Suspicious
Unsigned executable with one tier-1 and three low-trust detections but clean sandbox run.
- 4 of 74 antivirus engines flagged the file, including APEX and Bkav.Observed · Antivirus analysis
- The hash has been submitted 5 times from 5 sources.Derived · Saved report facts
f1ebe19df912bfd507…4a48677e17Recommended 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.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
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.
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
CNModFixerV2.1.exe
f1ebe19df912bfd5077f9ebd44342da4a410aa16f3029906845d374a48677e17
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\CNModFixerV2.1.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
CNModFixerV2.1.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\_MEI36202\VCRUNTIME140.dll
04Isolated runtime analysis - Written fileObserved
_bz2.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI36202\_bz2.pyd
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.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 of 74 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 5 times from 5 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: CNModFixerV2.1.exe — f1ebe19df912bfd5077f9ebd44342da4a410aa16f3029906845d374a48677e17
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\CNModFixerV2.1.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — CNModFixerV2.1.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: VCRUNTIME140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI36202\VCRUNTIME140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _bz2.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI36202\_bz2.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at
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.
Four of 74 engines flagged the file, including Microsoft as Trojan:Win32/Wacatac.B!ml. No sandbox malice, no dropped malicious children, and no external-intel hits were observed.
The file is a three-day-old unsigned 64-bit PE. One tier-1 engine and three lower-tier engines raised alerts, yet the sandbox produced only ambient behaviour and no malicious verdict. No dropped children were malicious and external intelligence sources returned no hits. Medium prevalence and lack of similar-hash history leave the sample in mixed-signal territory.
What We Detected
Four engines out of 74 reported the sample malicious: Microsoft (tier-1) labelled it Trojan:Win32/Wacatac.B!ml; CrowdStrike (tier-2) assigned win/malicious_confidence_60%; two low-trust engines added generic detections. No tier-1 family consensus exists.
Threat Behavior
The single sandbox execution wrote temporary Python runtime files, created several standard mutexes, and performed typical system-information queries. No C2 traffic, persistence mechanisms, or offensive MITRE techniques were recorded.
What To Do Now
Do not run the file on production systems. Re-scan after additional vendor coverage appears and consider obtaining a signed build from the original author if this is intended legitimate software.
Where this verdict could be wrong3 caveats
- Single tier-1 detection (Microsoft) could be a heuristic false positive; 15 other tier-1 engines reported clean.
- Sandbox produced no malicious verdict and no C2 or persistence indicators.
- Unsigned status is expected for many small modding utilities but still removes a strong trust signal.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- sandbox returned no malicious verdict
- no malicious dropped children
- no external intelligence hits
- unsigned executable
- single tier-1 malicious detection
- recent first-seen (3 days)
Treat as untrusted; keep antivirus enabled and await further vendor analysis before execution.
Behavior
Plain-English impact first, then the observed runtime evidence.
What this file does
Observed actions and their security significance
High concern: Manipulated how the operating system loads code, which can redirect execution.
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.
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\_MEI36202\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI36202\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI36202\_decimal.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI36202\_hashlib.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI36202\_lzma.pyd
- \BaseNamedObjects\Local\SM0:7012:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:7012:120:WilError_03
- \BaseNamedObjects\Local\ZonesCacheCounterMutex
- \BaseNamedObjects\Local\ZonesLockedCacheCounterMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 5c07572df2913618cfb8…b35dadNever scannednever seen before
- 055544d562ca50d49443…809d25Never scannednever seen before
- 456adaf7d2116f3e9410…80e71fNever scannednever seen before
- 1985000499475faf541b…c18862Never scannednever seen before
- 7c31b21496d4783456d9…561438Never scannednever seen before
- d28c3dd1c22bfb8a6e8a…589d11Never scannednever seen before
- b43119bdfc7c562bf07c…4ed2daNever scannednever seen before
- b17a87979862d19241ed…311001Never scannednever seen before
- 8010d006df2d62839c93…5e56ecNever scannednever seen before
- 1a513c0601c5b628018c…a27756Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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.
4 of 74 engines flagged this file
View all 74 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- CNModFixerV2.1.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 9.3 MB
- Last analyzed
- Jul 28, 2026, 11:26 PM UTC
f1ebe19df912bfd5077f9ebd44342da4a410aa16f3029906845d374a48677e17Safety & 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.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an unexpected attachment or a random download link is a red flag.
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.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.