Is MPQEditor safe?
Microsoft and Fortinet flag this rare, unsigned executable, but conflicting generic labels and a non-malicious sandbox run leave the threat identity unresolved.
Four of 75 engines flagged the executable, including Microsoft and Fortinet, but they did not agree on a malware family. Its unsigned, newly observed status raises risk, while one sandbox run found no offensive-only behavior or malicious runtime verdict; avoid running it unless its source and hash can be independently verified.
7909f3e8b16eb136cc…12af5eb5c26522Recommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened 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.
Four of 75 engines flagged the executable, including Microsoft and Fortinet, but they did not agree on a malware family. Its unsigned, newly observed status raises risk, while one sandbox run found no offensive-only behavior or malicious runtime verdict; avoid running it unless its source and hash can be independently verified.
Four of 75 engines detected the sample, with Microsoft and Fortinet providing two independent high-trust warnings. Their Wacatac and Kryptik labels differ, and no strong family consensus or external research match identifies a specific threat. The executable is unsigned and has appeared through only one source during its first four observed days, which limits benign reputation. One completed sandbox run recorded only broadly common techniques and no malicious verdict or dropped hashes. A complete contacted-host reputation result is unavailable, so network reputation cannot strengthen either side of the assessment.
What We Detected
Four of 75 antivirus engines flagged the executable. Microsoft reported Trojan:Win32/Wacatac.B!ml and Fortinet reported W32/Kryptik.CCB!tr, providing two high-trust warnings, while CrowdStrike and TrellixENS added generic detections. Because these labels do not converge on one family, the evidence supports caution without a reliable family attribution.
Threat Behavior
One completed sandbox run recorded T1027, T1027.002, T1071, and T1082, all categorized here as benign-common or ambient techniques rather than offensive-only behavior. It produced no malicious sandbox verdict, persistence indicators, written files, or dropped hashes. No complete contacted-host reputation result is available, although the recorded run listed no contacted domains, IPs, or URLs.
What To Do Now
Do not launch the file on a production system until its origin and SHA-256 hash are confirmed through the software publisher or another trusted distribution channel. Keep endpoint protection enabled, and quarantine or remove the file if its source cannot be authenticated.
Where this verdict could be wrong4 caveats
- 15 of 17 reporting tier-1 engines did not flag the sample, and engines.tier1FamilyConsensus.strong=false.
- The completed sandbox recorded no offensive-only techniques and issued no malicious sandbox verdict.
- YARAify returned 0 rules, MalwareBazaar had no hit, and the PE showed likelyPacked=false; these absences reduce corroboration but do not prove benignity.
- contactedHosts=null, so no complete host-reputation cross-check is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 15 of 17 reporting tier-1 engines did not flag the sample
- No strong tier-1 family consensus
- One sandbox produced no malicious verdict or offensive-only techniques
- No YARAify, MalwareBazaar, or CIRCL hit
- PE analysis found no likely packing or high-entropy code
- Two independent tier-1 detections from Microsoft and Fortinet
- Unsigned Win32 executable
- Only one source and one submission during four observed days
- Generic trojan-style labels from four engines
- No established signer or similar-file history
Avoid executing the file until its source and SHA-256 are verified through a trusted publisher channel. Keep endpoint protection enabled and quarantine it if authenticity cannot be established.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 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
CompleteRule evaluation completed with no recorded matches.
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
- 1spawned processes
- 0network contacts
- 1filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
MPQEditor
7909f3e8b16eb136cc4ecd9e4ac3a51669d0f329068e028cde12af5eb5c26522
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis
2 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.
- Local\SessionImmersiveColorMutex
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 4 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 of 75 antivirus engines flagged the file, including CrowdStrike and Fortinet.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: MPQEditor — 7909f3e8b16eb136cc4ecd9e4ac3a51669d0f329068e028cde12af5eb5c26522
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
4 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
Barely seen in the wild and first surfaced recently. 4 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- MPQEditor
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 1.8 MB
- Last analyzed
- Sep 15, 2026, 4:02 AM UTC
7909f3e8b16eb136cc4ecd9e4ac3a51669d0f329068e028cde12af5eb5c26522Safety & 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 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 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 MPQEditor safe, or is it malware?
What is MPQEditor?
How many antivirus engines detected MPQEditor?
What should I do if I already opened MPQEditor?
How do I remove MPQEditor?
What kind of malware is MPQEditor?
What is the SHA-256 hash of MPQEditor?
How up to date is this analysis of MPQEditor?
Community
Member reviews and reports for this exact file hash.