Is PrismLauncher-Windows-MinGW-arm64-Setup-11.0.3.exe safe?
Zero-engine detections, verified signature, and matching prior safe samples outweigh the sandbox heuristics.
The file shows no malicious detections across 75 engines and carries a verified signature from a previously clean signer. Similar-hash history also returned safe verdicts. Sandbox heuristics flagged process activity, but no sandbox verdict or dropped malicious children were observed.
4568411fc86d3dae9f…0c30f50d5d1668Recommended 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.
The file shows no malicious detections across 75 engines and carries a verified signature from a previously clean signer. Similar-hash history also returned safe verdicts. Sandbox heuristics flagged process activity, but no sandbox verdict or dropped malicious children were observed.
All 75 reporting engines returned clean results, including 17 tier-1 engines. The installer is signed by Seth Flynn with a 100 % safe history on the single prior sample. Two similar-hash matches also returned safe verdicts, one sharing the same signer. While the sandbox recorded MITRE techniques T1055, T1134 and T1485 plus two high/medium heuristics, the sandbox itself produced no malicious verdict and no malicious children were dropped. The contacted-host reputation check is incomplete, but the absence of detections and the signing evidence dominate.
What We Detected
75 engines scanned the 42 MB installer; none flagged it malicious or suspicious. The binary is signed by Seth Flynn (verified) and the signer’s first recorded sample was clean. Two prior files sharing the same imphash were previously classified safe, one matching the signer exactly.
Threat Behavior
One sandbox recorded typical installer actions plus three MITRE techniques (T1055, T1134, T1485) and triggered two heuristics related to process injection and LSASS access. No sandbox verdict was malicious, no malicious children were dropped, and no external-intel sources returned hits.
What To Do Now
The file can be executed with standard precautions. Keep endpoint protection enabled; the current evidence supports treating it as benign installer software.
Where this verdict could be wrong2 caveats
- behaviour.offensiveTechniques include T1055 (Process Injection) and T1134 (Access Token Manipulation) plus triggeredHeuristics 'MalwareTips.Synth.ProcessInjection' (high) and 'MalwareTips.Synth.CredentialDumper' (medium) — sandbox context is installer activity but still a counter-signal.
- contactedHosts=null — reputation cross-check for contactedIps=['162.159.36.2'] is missing, so network behaviour cannot be fully cleared.
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 with clean history
- Two prior safe verdicts on matching imphash/signer
- No malicious dropped children
- Sandbox heuristics flagged process-injection and credential-dumper patterns
- Contacted-host reputation check incomplete for IP 162.159.36.2
Run the installer with existing protections enabled; current evidence indicates the file is clean.
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
- 12spawned processes
- 1network contacts
- 26filesystem & 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-arm64-Setup-11.0.3.exe
4568411fc86d3dae9fd2cc82c2b1a04b5f27794e02218b7bc20c30f50d5d1668
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\PrismLauncher-Windows-MinGW-arm64-Setup-11.0.3.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\nsvCD72.tmp\modern-wizard.bmp
04Isolated runtime analysis - Written fileObserved
nsDialogs.dll
C:\Users\<USER>\AppData\Local\Temp\nsvCD72.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\nsvCD72.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsvCD72.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nsvCD72.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsvCD72.tmp\nsExec.dll
- C:\Users\<USER>\AppData\Local\Programs\PrismLauncher\prismlauncher.exe
- C:\Users\<USER>\AppData\Local\Temp\nsvCD72.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsvCD72.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nsvCD72.tmp\nsExec.dll
- C:\Users\<USER>\AppData\Local\Temp\nsvCD72.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsvCD72.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.
- cbf7c88bc91e761ccf37…2ec944Never scannednever seen before
- 85ce3082c5e4028fbe33…72ecc7Never scannednever seen before
- 9e415a7c724208e59d8a…577dd6Never scannednever seen before
- 8562a06f979005bbef8e…076ce0Never scannednever seen before
- d099cb74119b45398405…aa8d26Never scannednever seen before
- 0bf69bffb5050eeb655d…9cb15aNever scannednever seen before
- e908d6915ca53555a59d…ec804aNever scannednever seen before
- 99e7a64ab617727abc0c…84afd4Never scannednever seen before
- 8657ecc68e448540c42d…f6accaNever scannednever seen before
- a54aceae9144dad7e2af…64ab75Never 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
- 12sources 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-arm64-Setup-11.0.3.exe — 4568411fc86d3dae9fd2cc82c2b1a04b5f27794e02218b7bc20c30f50d5d1668
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\PrismLauncher-Windows-MinGW-arm64-Setup-11.0.3.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\nsvCD72.tmp\modern-wizard.bmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: nsDialogs.dll — C:\Users\<USER>\AppData\Local\Temp\nsvCD72.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-arm64-Setup-11.0.3.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Seth Flynn
- Size
- 40.8 MB
- Last analyzed
- Aug 10, 2026, 5:40 AM UTC
4568411fc86d3dae9fd2cc82c2b1a04b5f27794e02218b7bc20c30f50d5d1668Safety & 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-arm64-Setup-11.0.3.exe safe?
What is PrismLauncher-Windows-MinGW-arm64-Setup-11.0.3.exe?
How many antivirus engines detected PrismLauncher-Windows-MinGW-arm64-Setup-11.0.3.exe?
Is PrismLauncher-Windows-MinGW-arm64-Setup-11.0.3.exe digitally signed?
What is the SHA-256 hash of PrismLauncher-Windows-MinGW-arm64-Setup-11.0.3.exe?
Is it safe to install PrismLauncher-Windows-MinGW-arm64-Setup-11.0.3.exe?
How up to date is this analysis of PrismLauncher-Windows-MinGW-arm64-Setup-11.0.3.exe?
Community
Member reviews and reports for this exact file hash.