Our call: Is mkxp-z.exe safe?Safe
- 0 of 75 antivirus engines flagged the file.Observed · Antivirus analysis
- The hash has a long, established submission history across 918 sources.Derived · Submission history
- 1 high-confidence signature or behavior rule matched this file.Derived · Signature and behavior rules
1b9921a4fef0ee9128…836ca07d7aRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial14 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.
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
mkxp-z.exe
1b9921a4fef0ee9128555dae521bda0e2a32d19152022f27aba69f836ca07d7a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\Game.exe
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\1b9921a4fef0ee9128555dae521bda0e2a32d19152022f27aba69f836ca07d7a.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Logs
C:\ProgramData\Microsoft\Windows Security Health\Logs
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
192.168.0.15
Contact observed during runtime.
05Isolated runtime analysis - Contacted hostObserved
23.46.228.41
Contact observed during runtime.
06Isolated runtime analysis - +1 more recorded observation in Analyst mode
6 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
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 918 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: mkxp-z.exe — 1b9921a4fef0ee9128555dae521bda0e2a32d19152022f27aba69f836ca07d7a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\Game.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\1b9921a4fef0ee9128555dae521bda0e2a32d19152022f27aba69f836ca07d7a.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Logs — C:\ProgramData\Microsoft\Windows Security Health\Logs
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 192.168.0.15 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.46.228.41 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Behavior
Plain-English impact first, then the observed runtime evidence.
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.
- 192.168.0.15
- 23.46.228.41
- 23.196.145.221
- 20.99.133.109
- 20.69.140.28
- a83f:8110:0:0:1400:1400:2800:3800
- 192.168.0.10
- 23.55.140.42
- 192.168.0.36
- 151.101.22.172
- C:\ProgramData\Microsoft\Windows Security Health\Logs
- \BaseNamedObjects\Local\SM0:7052:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:7052:120:WilError_03
- \BaseNamedObjects\Local\ZonesCacheCounterMutex
- \BaseNamedObjects\Local\ZonesLockedCacheCounterMutex
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.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
Evidence%SAMPLEPATH%\Game.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.
Evidence23.46.228.41 · 23.196.145.221 · 20.99.133.109
0 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
- mkxp-z.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 17.7 MB
- Last analyzed
- Jun 11, 2026, 9:54 AM UTC
1b9921a4fef0ee9128555dae521bda0e2a32d19152022f27aba69f836ca07d7aSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
Run it only when it came from the developer's official site or another source you independently trust.
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
Keep your antivirus and Windows updates switched on so you stay protected.