Is PokemonInfiniteFusion-Launcher_1.1.exe safe?
Only 3 of 74 engines flagged this unsigned launcher, but direct-IP traffic and one XWorm label warrant caution pending source verification.
The evidence is mixed: 3 of 74 engines detected the file, while all 17 tier-1 engines remained silent and no family consensus formed. Because the unsigned launcher contacted two IP addresses whose reputations were not checked and exposed T1486 during one sandbox run, avoid running it unless its source and hash can be independently verified.
2f0c5e02bb7ab740ab…c4badefe610998Recommended 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.
The evidence is mixed: 3 of 74 engines detected the file, while all 17 tier-1 engines remained silent and no family consensus formed. Because the unsigned launcher contacted two IP addresses whose reputations were not checked and exposed T1486 during one sandbox run, avoid running it unless its source and hash can be independently verified.
Three of 74 engines flagged the executable, but none of the 17 tier-1 engines did so. Zillya named XWorm, while the other two detections were generic, leaving the claimed family uncorroborated. One sandbox run observed T1486 and direct connections to two IP addresses, but it produced no malicious sandbox verdict or persistence indicators. The file is unsigned and has no established publisher history, reducing confidence in its origin. Ten extracted children were inspected without a malicious finding, although their individual verdicts remain unknown. Taken together, these are unresolved mixed signals rather than convincing proof of XWorm infection or a strong false-positive pattern.
What We Detected
Three of 74 antivirus engines flagged the executable. Zillya identified it as Backdoor.XWorm.Win32.3294, while APEX and Bkav returned generic malware labels; none of the 17 tier-1 engines detected it, and no tier-1 family consensus exists. The executable is unsigned and has no established signer history.
Threat Behavior
One completed sandbox run recorded T1486 and connections to 104.21.1.82 and 199.232.196.193. No malicious sandbox verdict, persistence indicators, or malicious dropped children were recorded. A complete host-reputation result is unavailable because the contacted-host cross-check was not saved, so the two no complete contacted-host reputation result was available or confirmed command-and-control.
What To Do Now
Do not launch the file until its SHA-256 hash and download source are confirmed through the project's official release channel. Keep endpoint protection enabled; if the source cannot be authenticated, remove the file or test it only in an isolated environment.
Where this verdict could be wrong4 caveats
- All 17 tier-1 engines were silent, substantially weakening the isolated XWorm label from Zillya.
- behaviour.hasMaliciousSandboxVerdict=false, and no persistence indicators or malicious dropped children were identified.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false, though absence of hits does not prove benignity.
- The two observed IP addresses were not reputation-checked because contactedHosts=null.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 3/74 engines detected the sample
- tier1Malicious=0 and all 17 tier-1 engines reported it clean
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false across 10 inspected children
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false
- Unsigned Win32 executable with no established publisher history
- Zillya detected Backdoor.XWorm.Win32.3294
- Sandbox observed MITRE technique T1486
- Direct connections to 104.21.1.82 and 199.232.196.193
- No complete reputation result for the contacted IP addresses
Verify SHA-256 2f0c5e02bb7ab740abb390206884f1b990ca42157aa8366dbfc4badefe610998 against the project's official release channel before use. Keep endpoint protection enabled and discard the file if its origin cannot be confirmed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
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
- 13MITRE ATT&CK techniques
- 2spawned processes
- 2network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
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.
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
PokemonInfiniteFusion-Launcher_1.1.exe
2f0c5e02bb7ab740abb390206884f1b990ca42157aa8366dbfc4badefe610998
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\PokemonInfiniteFusion-Launcher_1.1.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\PokemonInfiniteFusion-Launcher_1.1.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_avif.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI31122\PIL\_avif.cp312-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imaging.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI31122\PIL\_imaging.cp312-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.21.1.82
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
199.232.196.193
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 104.21.1.82
- 199.232.196.193
- C:\Users\<USER>\AppData\Local\Temp\_MEI31122\PIL\_avif.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI31122\PIL\_imaging.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI31122\PIL\_imagingcms.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI31122\PIL\_imagingmath.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI31122\PIL\_imagingtk.cp312-win_amd64.pyd
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 6af926fd1a58f3912b6f…7d4f71Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never scannednever seen before
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
- 3 / 74engines flagged
- 366sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
3 of 74 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 447 times from 366 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: PokemonInfiniteFusion-Launcher_1.1.exe — 2f0c5e02bb7ab740abb390206884f1b990ca42157aa8366dbfc4badefe610998
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\PokemonInfiniteFusion-Launcher_1.1.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\PokemonInfiniteFusion-Launcher_1.1.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: _avif.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI31122\PIL\_avif.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _imaging.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI31122\PIL\_imaging.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 104.21.1.82 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 199.232.196.193 — Contact observed during runtime.
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.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The 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.
Evidence104.21.1.82 · 199.232.196.193
3 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
- PokemonInfiniteFusion-Launcher_1.1.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 32.6 MB
- Last analyzed
- Sep 21, 2026, 11:08 AM UTC
2f0c5e02bb7ab740abb390206884f1b990ca42157aa8366dbfc4badefe610998Safety & 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 PokemonInfiniteFusion-Launcher_1.1.exe safe, or is it malware?
What is PokemonInfiniteFusion-Launcher_1.1.exe?
How many antivirus engines detected PokemonInfiniteFusion-Launcher_1.1.exe?
I already downloaded and ran PokemonInfiniteFusion-Launcher_1.1.exe — what should I do?
How do I remove PokemonInfiniteFusion-Launcher_1.1.exe?
What kind of malware is PokemonInfiniteFusion-Launcher_1.1.exe?
What is the SHA-256 hash of PokemonInfiniteFusion-Launcher_1.1.exe?
How up to date is this analysis of PokemonInfiniteFusion-Launcher_1.1.exe?
Community
Member reviews and reports for this exact file hash.