Is Cartoon M.U.G.E.N.exe safe?
Generic detections, unsigned UPX-style packing, and direct-IP activity warrant caution, although tier-1 engines and the completed sandbox provide no malware confirmation.
Eight of 76 engines flagged this executable, but none of the 17 tier-1 engines did, and no named malware family emerged. Its unsigned, packed structure and two direct-IP contacts justify caution because those addresses were not reputation-checked, though the sandbox found no offensive behavior, malicious verdict, persistence, or dropped payload.
0ecd998611d15f50eb…1a35abf504fa04Recommended 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 76 engines flagged this executable, but none of the 17 tier-1 engines did, and no named malware family emerged. Its unsigned, packed structure and two direct-IP contacts justify caution because those addresses were not reputation-checked, though the sandbox found no offensive behavior, malicious verdict, persistence, or dropped payload.
The detection pattern is mixed: 8 of 76 engines raised generic alerts, but the two stronger detections were tier-2 and all 17 tier-1 engines remained silent. Static inspection shows an unsigned executable with UPX-style sections and a high-entropy code section, which can conceal code but is also common in older compressed software. One sandbox run observed connections to two IP addresses, yet produced no malicious sandbox verdict, offensive-only techniques, persistence, or dropped payload. No complete reputation result is available for those IP addresses because the contacted-host cross-check was not saved. The file has existed since 2012, and neither MalwareBazaar nor YARAify supplied independent corroboration, leaving meaningful concerns without enough evidence for a confirmed malware finding.
What We Detected
Eight of 76 antivirus engines flagged the executable. Six were low-trust detections and two came from tier-2 engines, DeepInstinct and SentinelOne; all used generic or machine-learning labels rather than identifying a consistent malware family. All 17 tier-1 engines reported the sample undetected.
Threat Behavior
Static analysis found UPX-style sections, high-entropy code, and an unsigned executable, which can indicate concealed code but may also reflect ordinary compression. One completed sandbox run observed contacts to 20.99.133.109 and 192.229.211.108. It did not produce a malicious sandbox verdict, offensive-only techniques, persistence indicators, or dropped files. No complete host-reputation check is available for the observed IP addresses, so their risk remains unresolved.
What To Do Now
Do not run the file on a production or personal system unless its source and expected hash can be independently verified. Keep endpoint protection enabled, and if testing is necessary, use an isolated disposable environment with network monitoring.
Where this verdict could be wrong4 caveats
- All 17 tier-1 engines, including Avast, BitDefender, ESET-NOD32, Fortinet, and Ikarus, reported the sample undetected.
- The completed sandbox produced no malicious verdict, no persistence indicators, and no dropped-file hashes.
- externalIntel.malwareBazaar.hit=false and externalIntel.yaraify.ruleCount=0 provide no independent malware-family corroboration, although absence of hits does not prove benignity.
- The file was first submitted in 2012 and has 16 unique sources, reducing concern that it is a newly introduced sample.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- engines.tier1Malicious=0 across 17 tier-1 engines.
- behaviour.hasMaliciousSandboxVerdict=false.
- behaviour.offensiveCount=0 and no persistence indicators were recorded.
- externalIntel.malwareBazaar.hit=false and externalIntel.yaraify.ruleCount=0.
- The sample dates to 2012 and prevalence.uniqueSources=16.
- 8/76 engines produced malicious detections.
- The executable is unsigned.
- peAnalysis.highEntropyCode=true and peAnalysis.likelyPacked=true.
- The sandbox contacted 20.99.133.109 and 192.229.211.108 directly.
- contactedHosts=null leaves the observed IP addresses without a completed reputation assessment.
- MalwareTips.Synth.DropperNetworkProfile fired, although its supporting evidence is not independently conclusive.
Avoid executing it until the original distributor and hash are verified. Keep security protection enabled and quarantine or test only in an isolated disposable environment.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete8 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 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
- 5MITRE ATT&CK techniques
- 2spawned processes
- 2network contacts
- 7filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Note: Collects details about your system.
Note: Connected to 2 servers during sandbox analysis.
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
Cartoon M.U.G.E.N.exe
0ecd998611d15f50ebd188f1fcda8d8919b76bd9c6aab5dea61a35abf504fa04
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\0ecd998611d15f50ebd188f1fcda8d8919b76bd9c6aab5dea61a35abf504fa04.exe
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\wuapihost.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.133.109
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
192.229.211.108
Contact observed during runtime.
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.
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
- 192.229.211.108
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7CD.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF898.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF8C8.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER39B8.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.
- 3rule hits recorded
- 8 / 76engines flagged
- 16sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
8 of 76 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 18 times from 16 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Cartoon M.U.G.E.N.exe — 0ecd998611d15f50ebd188f1fcda8d8919b76bd9c6aab5dea61a35abf504fa04
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\0ecd998611d15f50ebd188f1fcda8d8919b76bd9c6aab5dea61a35abf504fa04.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\wuapihost.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 20.99.133.109 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 192.229.211.108 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved 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.
PE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencehigh-entropy code sectionThe 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 · 192.229.211.108Unsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidence20.99.133.109
8 of 76 engines flagged this file
View all 76 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Cartoon M.U.G.E.N.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 294.0 KB
- Last analyzed
- Sep 22, 2026, 11:33 AM UTC
0ecd998611d15f50ebd188f1fcda8d8919b76bd9c6aab5dea61a35abf504fa04Safety & 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 Cartoon M.U.G.E.N.exe safe, or is it malware?
What is Cartoon M.U.G.E.N.exe?
How many antivirus engines detected Cartoon M.U.G.E.N.exe?
What should I do if I already ran Cartoon M.U.G.E.N.exe?
How do I remove Cartoon M.U.G.E.N.exe?
What is the SHA-256 hash of Cartoon M.U.G.E.N.exe?
How up to date is this analysis of Cartoon M.U.G.E.N.exe?
Community
Member reviews and reports for this exact file hash.