Our call: Is Vynx Launcher_1.0.0_x64_en-US.msi safe?Suspicious
Unsigned MSI shows sandbox evidence of process injection and LSASS access yet zero engine detections.
- 1 high-confidence signature or behavior rule matched this file.Derived · Signature and behavior rules
- 0 of 74 antivirus engines flagged the file.Observed · Antivirus analysis
- The hash has been submitted 424 times from 362 sources.Derived · Saved report facts
2bb31f8d49a0002c64…9b8692df5aRecommended 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.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 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.
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
Vynx Launcher_1.0.0_x64_en-US.msi
2bb31f8d49a0002c64acd586b7c36726771f30f5d8cfe194fe469b9b8692df5a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\Vynx Launcher_1.0.0_x64_en-US _1_.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
~DFB2F0F3E9C73E9D02.TMP
C:\Windows\Temp\~DFB2F0F3E9C73E9D02.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.
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
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 424 times from 362 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Vynx Launcher_1.0.0_x64_en-US.msi — 2bb31f8d49a0002c64acd586b7c36726771f30f5d8cfe194fe469b9b8692df5a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\Vynx Launcher_1.0.0_x64_en-US _1_.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: ~DFB2F0F3E9C73E9D02.TMP — C:\Windows\Temp\~DFB2F0F3E9C73E9D02.TMP
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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 file triggered two high-severity behavioural heuristics (T1055, LSASS access) but no antivirus engine flagged it. Medium prevalence and lack of signing leave the intent ambiguous.
Zero detections across 74 engines rules out a known malware family, yet the sandbox recorded LSASS memory access and process-injection activity that legitimate installers rarely need. The package is unsigned and the contacted IP lacks reputation data, so the evidence is mixed. Medium prevalence suggests the file is not brand-new but does not prove legitimacy. Overall the behavioural red flags outweigh the clean engine results.
What We Detected
Zero of 74 engines returned a malicious verdict. Sandbox execution revealed two offensive MITRE techniques (T1055 Process Injection, T1548 Elevation Abuse) and direct access to lsass.exe. The MSI dropped ten child files, none of which have known malicious verdicts.
Threat Behavior
The observed LSASS access and process-injection calls are consistent with credential-dumping tooling, yet the same actions can appear in advanced installers that self-update or elevate privileges. No domains were contacted and the single IP (162.159.36.2) has no cached reputation.
What To Do Now
Run the installer only in a controlled test environment. Keep Windows Defender and other endpoint protection enabled. Monitor for unexpected child processes or LSASS access if execution is required.
Where this verdict could be wrong2 caveats
- Unsigned installer with process-injection and LSASS-access signals could indicate a legitimate but highly privileged launcher; absence of tier-1 detections and medium prevalence reduce confidence in malice.
- contactedHosts is null so no host-reputation cross-check is available; direct-IP contact to 162.159.36.2 remains unverified.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero engine detections (0/74)
- Medium prevalence across 362 sources
- No malicious dropped children
- No external-intel hits
- Unsigned Windows Installer
- Sandbox observed LSASS access
- Process-injection technique recorded
- Direct-IP contact without domain
Treat as potentially risky; do not execute on production systems until additional code-signing or vendor provenance is confirmed.
Behavior
Plain-English impact first, then the observed runtime evidence.
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.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Reads your Windows user-account details.
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.
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\~DFB2F0F3E9C73E9D02.TMP
- C:\Windows\Temp\~DF91D4B9290A6F8BF1.TMP
- C:\Windows\Temp\~DF3E5ED4F787A2457C.TMP
- C:\Windows\Temp\~DF93F1C866C0BD3EA2.TMP
- C:\Config.Msi\CMPD5BE.tmp
- C:\Config.Msi
- C:\Windows\Installer\d033.msi
- C:\Config.Msi\CMPD968.tmp
- C:\Config.Msi\d032.rbs
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:6952:304:WilStaging_02
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 8db46f504026cf0f4d9b…7fe760Never scannednever seen before
- 772a8128a739bea0685f…8bd21bNever scannednever seen before
- e51907d515322b93f393…fea97aNever scannednever seen before
- d7ba772feb82360ab8f5…b9a13dNever scannednever seen before
- 5480644c4c2b0e094e68…4f456fNever scannednever seen before
- 8a630e7472ed14694e53…699397Never scannednever seen before
- c73d479115406c2b245a…74463fNever scannednever seen before
- 21b4dd82eed80665fbeb…3f5dd1Never scannednever seen before
- 4dd819e83f881d290ad9…01bbdbNever scannednever seen before
- dab6dfd2d427a4e5b5cf…927f8dNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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
0 of 74 engines flagged this file
View all 74 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
- Vynx Launcher_1.0.0_x64_en-US.msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 7.4 MB
- Last analyzed
- Jul 27, 2026, 5:20 PM UTC
2bb31f8d49a0002c64acd586b7c36726771f30f5d8cfe194fe469b9b8692df5aSafety & 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.
Don't install it unless you're certain it came from a source you trust.
Check where you got it — an unexpected attachment or a random download link is a red flag.
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.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.