Is mkxp-z.exe safe?
No antivirus engine detected malware, and extensive long-term prevalence plus an uneventful sandbox run outweigh the isolated process-injection technique mapping.
None of 75 antivirus engines flagged this executable, including all 17 tier-1 engines, despite years of broad circulation. One sandbox mapped activity to process injection, but produced no malicious verdict, dropped payload, persistence indicator, or independently corroborating detection.
5c75e92fcbb6ec50b9…7b8686b532bf04Recommended 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.
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.
None of 75 antivirus engines flagged this executable, including all 17 tier-1 engines, despite years of broad circulation. One sandbox mapped activity to process injection, but produced no malicious verdict, dropped payload, persistence indicator, or independently corroborating detection.
The strongest evidence is the complete absence of detections across 75 antivirus engines, with all 17 tier-1 engines silent. The file has circulated since 2023 across 2,965 sources and 4,575 submissions, making an undetected widespread threat less likely. A completed sandbox run mapped one action to T1055, but its verdict was non-malicious and there were no written files, dropped hashes, or persistence indicators. Both observed domains were covered by the host-reputation check and neither was listed as malicious or suspicious. The executable is unsigned and has a negative reputation score, but those weaker concerns do not outweigh the consistent independent evidence.
What We Detected
None of 75 antivirus engines reported a malicious or suspicious result. This includes 17 tier-1 engines such as Avast, BitDefender, ESET, Kaspersky, and Fortinet. The file has also been submitted 4,575 times by 2,965 distinct sources since August 2023, indicating broad and established circulation.
Threat Behavior
One completed sandbox run did not produce a malicious verdict. A heuristic mapped activity to MITRE T1055, a technique associated with process injection, but the mapping alone does not prove malicious intent or a specific injection method. No files were written, no child hashes were dropped, and no persistence indicators were recorded. The host-reputation check covered both observed domains, and neither was listed as malicious or suspicious.
What To Do Now
Obtain the executable from the project's official release channel and verify its SHA-256 hash when the publisher provides one. Because the file is unsigned, keep endpoint protection enabled and avoid copies obtained from untrusted mirrors.
Where this verdict could be wrong3 caveats
- The executable is unsigned: signing.signed=false and signing.signerStats.found=false, so publisher identity cannot be authenticated.
- MalwareTips.Synth.ProcessInjection fired at high severity for T1055; process injection can be used offensively even though this isolated mapping does not establish intent.
- file.reputation=-10 is negative, although it conflicts with 0/75 detections and substantial long-term prevalence.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines reported malicious or suspicious results.
- All 17 tier-1 engines reported no detection.
- 2,965 sources submitted the file 4,575 times since 2023.
- behaviour.hasMaliciousSandboxVerdict=false.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false.
- signing.signed=false; publisher identity is not authenticated.
- MalwareTips.Synth.ProcessInjection fired for MITRE T1055.
- file.reputation=-10.
Use only a copy obtained from the official project channel and verify its hash if possible. Keep endpoint protection enabled, especially because the executable lacks a verifiable signature.
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
Partial2 of 22 contacted hosts were cross-checked; coverage is incomplete.
YARA
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
- 4MITRE ATT&CK techniques
- 15spawned processes
- 22network contacts
- 15filesystem & mutex artifacts
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.
- www.microsoft.com
- res.public.onecdn.static.microsoft
- 20.99.133.109
- 192.229.211.108
- 20.99.184.37
- 192.168.0.1
- 192.168.0.35
- 23.216.81.152
- 104.71.214.69
- 20.99.186.246
- 23.59.198.43
- 20.99.185.48
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService123.0.6288.0\Start
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\GoogleUpdaterInternalService123.0.6288.0\ImagePath
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER338E.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3459.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3489.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3564.tmp.WERInternalMetadata.xml
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
- 0 / 75engines flagged
- 2,965sources in submission history
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 2,965 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 — 5c75e92fcbb6ec50b9f8fc61913d751a8945d6a1fc69c3017c7b8686b532bf04
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\mkxp-z.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\wuapihost.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 08
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
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.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence%SAMPLEPATH%\mkxp-z.exe
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
- 14.0 MB
- Last analyzed
- Oct 7, 2026, 3:44 PM UTC
5c75e92fcbb6ec50b9f8fc61913d751a8945d6a1fc69c3017c7b8686b532bf04Safety & 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.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is mkxp-z.exe safe?
What is mkxp-z.exe?
How many antivirus engines detected mkxp-z.exe?
What is the SHA-256 hash of mkxp-z.exe?
Is it safe to run mkxp-z.exe?
How up to date is this analysis of mkxp-z.exe?
Community
Member reviews and reports for this exact file hash.