Is PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe safe?
Installer signed by Seth Flynn with zero engine detections and matching prior safe samples.
Zero of 75 engines flagged the file. The executable is signed by Seth Flynn with a clean prior sample and two additional imphash matches that also returned safe. Sandbox activity matches a standard NSIS installer workflow.
717eed9e82a89fe788…a878077e3488baRecommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
Zero of 75 engines flagged the file. The executable is signed by Seth Flynn with a clean prior sample and two additional imphash matches that also returned safe. Sandbox activity matches a standard NSIS installer workflow.
All 75 engines returned clean results, including 17 tier-1 engines. The signer has a 100 % safe rate on the single historical sample. Three similar-hash records also returned safe, two of them with matching signer. The sandbox observed typical installer behaviour (NSIS temp extraction, killing prior instances) and no malicious children or sandbox verdicts were produced.
What We Detected
75 antivirus engines scanned the 44 MB NSIS-based installer; none returned a malicious or suspicious result. The binary is Authenticode-signed by Seth Flynn and verified. Three prior samples sharing the same imphash were previously classified safe, two of them also signed by Seth Flynn.
Threat Behavior
One sandbox execution recorded typical installer actions: extraction of NSIS plug-ins, writing PrismLauncher binaries to %LocalAppData%\Programs\PrismLauncher, and terminating any running prismlauncher.exe. Three MITRE mappings (T1055, T1134, T1485) were triggered, but the observed activity aligns with legitimate self-extraction and upgrade handling rather than malicious process injection or credential dumping. One direct-IP connection to 162.159.36.2 occurred; host reputation data is unavailable.
What To Do Now
The file can be executed if obtained from the official Prism Launcher project site. Keep Windows Defender and other endpoint protection enabled; no disabling of security software is required or recommended.
Where this verdict could be wrong2 caveats
- contactedHosts=null — host reputation cross-check incomplete; cannot confirm whether 162.159.36.2 is clean.
- triggeredHeuristics show T1055/T1134/T1485 mappings, but sandbox evidence is consistent with NSIS installer self-extraction and process termination of prior PrismLauncher instances.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines flagged malicious
- verified signature by Seth Flynn
- three prior safe imphash matches
- medium prevalence, 47 submitters
Proceed with installation from the trusted source; retain endpoint protection.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 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
- 22MITRE ATT&CK techniques
- 13spawned processes
- 1network contacts
- 28filesystem & mutex artifacts
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
PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe
717eed9e82a89fe788d1ec099325b75a8719b6948657f9fe50a878077e3488ba
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\PrismLauncher-Windows-MinGW-w64-Setup-11.0.3 _1_.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
TaskKill /IM prismlauncher.exe /F
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
modern-wizard.bmp
C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\modern-wizard.bmp
04Isolated runtime analysis - Written fileObserved
nsDialogs.dll
C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\nsDialogs.dll
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:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\nsExec.dll
- C:\Users\<USER>\AppData\Local\Programs\PrismLauncher\prismlauncher.exe
- C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\nsExec.dll
- C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 52c6a712d5c25529a383…8642d8Never scannednever seen before
- 169bbc68fa4d8d731313…63a340Never scannednever seen before
- 2fe0859fd222e06a7b57…f2e043Never scannednever seen before
- dcd8309a904c9d61ad66…3dc7a8Never scannednever seen before
- 2cd3a2d4053954db1196…843c77Never scannednever seen before
- 2bde8c82d0cd5f7a5cbf…bdb54eNever scannednever seen before
- ae65f36c53888fb18898…01d225Never scannednever seen before
- f73934fb5ac16aaaec1d…ff074dNever scannednever seen before
- 8c9359edeb22bfaa8d36…b3d1b7Never scannednever seen before
- da272ca1ccd2ada75a49…71f8e6Never 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
- 0 / 75engines flagged
- 47sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The file has a valid code signature from Seth Flynn.
ProvenanceObservedSourceCode-signing metadataObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe — 717eed9e82a89fe788d1ec099325b75a8719b6948657f9fe50a878077e3488ba
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\PrismLauncher-Windows-MinGW-w64-Setup-11.0.3 _1_.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — TaskKill /IM prismlauncher.exe /F
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: modern-wizard.bmp — C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\modern-wizard.bmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: nsDialogs.dll — C:\Users\<USER>\AppData\Local\Temp\nstD36E.tmp\nsDialogs.dll
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\Explorer.EXESandbox 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 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Seth Flynn
- Size
- 42.7 MB
- Last analyzed
- Aug 10, 2026, 5:40 AM UTC
717eed9e82a89fe788d1ec099325b75a8719b6948657f9fe50a878077e3488baSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Install it only when it came from the developer's official site or an official app store.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe safe?
What is PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe?
How many antivirus engines detected PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe?
Is PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe digitally signed?
What is the SHA-256 hash of PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe?
Is it safe to install PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe?
How up to date is this analysis of PrismLauncher-Windows-MinGW-w64-Setup-11.0.3.exe?
Community
Member reviews and reports for this exact file hash.