Is Eon_Launcher_1.3.5_x64_en-US.msi safe?
Unsigned MSI installer shows sandbox evidence of LSASS access and process injection techniques.
One tier-2 engine flagged the file while 15 tier-1 engines remained silent. Sandbox logs indicate LSASS access and process injection, yet no tier-1 family consensus or malicious child files were found.
9374f8a09d208c5bc3…7eecf9edffe5a1Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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.
One tier-2 engine flagged the file while 15 tier-1 engines remained silent. Sandbox logs indicate LSASS access and process injection, yet no tier-1 family consensus or malicious child files were found.
The single Google tier-2 detection carries limited weight against 74 other engines that did not flag the sample. However, the sandbox recorded LSASS memory access and MITRE techniques T1055, T1485, T1548, and T1562.001, which are rarely seen in legitimate installers. The file is unsigned and lacks any trusted-publisher history, increasing risk. Prevalence is medium and the file is 88 days old, so it is not brand-new. Conflicting community annotations—one calling it Wannacry, another calling it clean—leave the evidence balanced between suspicious and unknown.
What We Detected
One tier-2 engine (Google) returned a generic malicious label; 15 tier-1 engines reported clean. The MSI is unsigned. Sandbox execution logged LSASS access and process-injection activity mapped to MITRE T1055, T1485, T1548, and T1562.001.
Threat Behavior
Offensive techniques observed include credential-store access and defense-evasion patterns. No malicious dropped children or sandbox verdicts were recorded. Contacted-host reputation data is unavailable.
What To Do Now
Do not run the installer on production systems. Keep endpoint protection enabled. If the file is required, execute it only in an isolated virtual machine and monitor for unexpected outbound traffic or new processes.
Where this verdict could be wrong1 caveat
- communityComments[1] explicitly labels the file 'Clean' with score 19/100
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 tier-1 engines reported clean
- Medium prevalence across 2135 submitters
- No malicious dropped children
- Unsigned Windows Installer
- Sandbox observed LSASS access
- MITRE techniques T1055, T1485, T1548, T1562.001
- Single tier-2 detection
Treat the installer as untrusted; run only in a controlled environment or obtain a signed copy from the official publisher.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was 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
- 10MITRE ATT&CK techniques
- 12spawned processes
- 1network contacts
- 33filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used removable-media replication behaviour that can spread files between devices.
High concern: Attempted to impair or bypass security controls.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Note: Connected to 1 server 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
Eon_Launcher_1.3.5_x64_en-US.msi
9374f8a09d208c5bc30d27c20a5e9fa8a153eb083435e274427eecf9edffe5a1
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\Eon_Launcher_1.3.5_x64_en-US.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ngen.log
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
04Isolated runtime analysis - Written fileObserved
~DFDD7749C15394E1E7.TMP
C:\Windows\Temp\~DFDD7749C15394E1E7.TMP
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
- C:\Windows\Temp\~DFDD7749C15394E1E7.TMP
- C:\Windows\Temp\~DFECAEE95A49EBA675.TMP
- C:\Windows\Temp\~DFC9B4EB6D7D7A75C0.TMP
- C:\Windows\Temp\~DF6A5EBF711605BE21.TMP
- C:\Config.Msi\CMP272A.tmp
- C:\Config.Msi
- C:\Windows\Installer\10c42.msi
- C:\Config.Msi\CMP4C08.tmp
- C:\Config.Msi\10c41.rbs
- Global\_MSIExecute
- Local\SessionImmersiveColorMutex
- \BaseNamedObjects\Local\SM0:4128:304:WilStaging_02
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- ef1bc2b30b593a92a5fb…5fc15bNever scannednever seen before
- 7f263feb65374bea0384…1b62c9Never scannednever seen before
- 6f92b5593e21c6e88219…b6c66fNever scannednever seen before
- f239463682f4b112d390…d9a0aeNever scannednever seen before
- 45e739c2072760cec26f…1c4728Never scannednever seen before
- 079ff7043b71597c3795…58dc10Never scannednever seen before
- 6712bce08e855c2e1ace…82992bNever scannednever seen before
- 6754c43b709b9a1d3a4a…fed9bcNever scannednever seen before
- f7bc5c3178fe67502b87…beba58Never scannednever seen before
- 6087dbd8c5b04707b89c…2a1cecNever 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.
- 3rule hits recorded
- 1 / 75engines flagged
- 2,135sources 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
1 of 75 antivirus engines flagged the file, including Google.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 2,679 times from 2,135 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Eon_Launcher_1.3.5_x64_en-US.msi — 9374f8a09d208c5bc30d27c20a5e9fa8a153eb083435e274427eecf9edffe5a1
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\Eon_Launcher_1.3.5_x64_en-US.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ngen.log — C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ~DFDD7749C15394E1E7.TMP — C:\Windows\Temp\~DFDD7749C15394E1E7.TMP
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — 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.
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.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.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.
Evidence162.159.36.2
1 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Eon_Launcher_1.3.5_x64_en-US.msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 56.0 MB
- Last analyzed
- Aug 9, 2026, 11:31 PM UTC
9374f8a09d208c5bc30d27c20a5e9fa8a153eb083435e274427eecf9edffe5a1Safety & 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 install 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. Download a fresh installer 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 Eon_Launcher_1.3.5_x64_en-US.msi safe, or is it malware?
What is Eon_Launcher_1.3.5_x64_en-US.msi?
How many antivirus engines detected Eon_Launcher_1.3.5_x64_en-US.msi?
What should I do if I already installed Eon_Launcher_1.3.5_x64_en-US.msi?
How do I remove Eon_Launcher_1.3.5_x64_en-US.msi?
What is the SHA-256 hash of Eon_Launcher_1.3.5_x64_en-US.msi?
How up to date is this analysis of Eon_Launcher_1.3.5_x64_en-US.msi?
Community
Member reviews and reports for this exact file hash.