Is PrismLauncher-Windows-MSVC-Setup-11.0.3.exe safe?
No antivirus engine detected malware, but one sandbox reported concerning injection and LSASS-related activity that warrants verifying the unsigned installer before running it.
All 74 antivirus engines were silent, including 17 tier-1 engines, and the two YARA matches identify the NSIS installer framework rather than malware. However, the unsigned executable produced a malicious sandbox result with process-injection and LSASS-related indicators, so it should only be used after its source and hash are independently verified.
3049faba7b69d515b2…22e9b3909dcaafRecommended 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.
All 74 antivirus engines were silent, including 17 tier-1 engines, and the two YARA matches identify the NSIS installer framework rather than malware. However, the unsigned executable produced a malicious sandbox result with process-injection and LSASS-related indicators, so it should only be used after its source and hash are independently verified.
Static scanning found no detection among 74 engines, including all 17 reporting tier-1 engines. The two community YARA rules merely recognize an NSIS installer and do not identify a threat family. Runtime evidence is less reassuring: one sandbox labeled the run malicious, with mappings to T1055, T1134, and T1485 and a separate LSASS-targeting heuristic, although another sandbox result was clean. The complete domain cross-check found no known malicious or suspicious contacted domain, and no inspected child was identified as malicious, but the child verdicts remain unresolved. Related PrismLauncher builds received prior safe decisions, yet those are imphash-only matches and cannot overcome the unsigned file's anomalous runtime evidence.
What We Detected
None of 74 antivirus engines flagged the installer, including 17 reporting tier-1 engines. Two YARA rules matched—Detect_NSIS_Nullsoft_Installer and NSIS—but both identify the common Nullsoft installer format rather than a malware family. The file is unsigned, so its publisher cannot be authenticated through a code-signing certificate.
Threat Behavior
One completed sandbox run produced conflicting results: one entry labeled the execution malicious while another labeled it clean. The saved evidence maps activity to process injection (T1055), token manipulation (T1134), and file or directory discovery/destruction behavior (T1485), while a heuristic also reports access involving LSASS. These observations are concerning, although installer and bundled Microsoft runtime activity may contribute to noisy behavioral classifications. All four contacted domains received complete reputation coverage with no known malicious or suspicious result, and none of ten inspected children was identified as malicious; however, those children remain unclassified.
What To Do Now
Obtain the installer only from PrismLauncher's official release channel and compare its SHA-256 value with an officially published checksum if available. If the source or checksum cannot be verified, quarantine the file and avoid running it; keep endpoint protection enabled.
Where this verdict could be wrong4 caveats
- signing.applicable=true but signing.signed=false, so the executable lacks publisher authentication.
- The MalwareTips.Synth.CredentialDumper heuristic reports LSASS-targeting activity, which is atypical for an ordinary launcher installer.
- The five safe similarHashes entries are imphash-only matches without signer co-matching, so a shared NSIS framework may explain the similarity.
- droppedChildren.inspected=10 found no malicious child, but all ten child verdicts are unknown rather than confirmed clean.
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/74 antivirus engines detected the sample
- All 17 reporting tier-1 engines were undetected
- YARA matches identify NSIS rather than a malware family
- Complete domain cross-check found no known malicious or suspicious domain
- No inspected dropped child was identified as malicious
- Unsigned Windows executable despite code signing being applicable
- behaviour.hasMaliciousSandboxVerdict=true
- Process-injection mapping T1055
- LSASS-targeting credential-dumper heuristic
- Ten dropped children remain unclassified
Verify SHA-256 3049faba7b69d515b2e036e9a8e28918d20e12f8d882f8e0d222e9b3909dcaaf against PrismLauncher's official release information before execution. If verification is unavailable, quarantine it and keep endpoint protection enabled.
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
Partial4 of 9 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete4 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
- 35MITRE ATT&CK techniques
- 14spawned processes
- 12network contacts
- 35filesystem & 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: Changed an auto-start location that can make code run after sign-in or restart.
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.
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
PrismLauncher-Windows-MSVC-Setup-11.0.3.exe
3049faba7b69d515b2e036e9a8e28918d20e12f8d882f8e0d222e9b3909dcaaf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\PrismLauncher-Windows-MSVC-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\nsnE04E.tmp\modern-wizard.bmp
04Isolated runtime analysis - Written fileObserved
nsDialogs.dll
C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\nsDialogs.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
aka.ms
Saved reputation verdict: safe.
06Contacted-host cross-check - Contacted hostObserved
i18n.prismlauncher.org
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; 1 returned "malicious".
Adversary techniques mapped to the MITRE ATT&CK framework.
- aka.ms
- i18n.prismlauncher.org
- yr.c.lencr.org
- yr2.c.lencr.org
- 23.222.198.10
- 185.199.110.153
- 23.49.5.233
- 104.18.20.213
- 184.31.114.8
- http://yr.c.lencr.org/
- http://yr2.c.lencr.org/73.crl
- https://i18n.prismlauncher.org/index_v2.json
- HKEY_CURRENT_USER\SOFTWARE\PrismLauncher\InstallDir
- HKEY_CURRENT_USER\Software\Classes\curseforge\shell\open\command\(Default)
- HKEY_CURRENT_USER\Software\Classes\prismlauncher\shell\open\command\(Default)
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PrismLauncher\DisplayName
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PrismLauncher\DisplayIcon
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\PrismLauncher\UninstallString
- C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\nsExec.dll
- C:\Users\<USER>\AppData\Local\Programs\PrismLauncher\prismlauncher.exe
- C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\NScurl.dll
- C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\nsExec.dll
- C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\System.dll
- cversions.3.m
- Local\SessionImmersiveColorMutex
- QtLockedFile mutex c:/users/bruno/appdata/local/temp/plda7e2591a4d7-lockfile
- Local\MSCTF.Asm.MutexDefault1
- DefaultTabtip-MainUI
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 946d0f28a1ae8bfeeb73…93eea1Never scannednever seen before
- 2ac8b7c19a5189662de3…39f9caNever scannednever seen before
- c9d4c5c5dbf8d9ef3264…9f18e5Never scannednever seen before
- 44c76290f7a2e45940e8…acbc8dNever scannednever seen before
- 27891eec899be859e3b4…c6e701Never scannednever seen before
- 4fb8262965662195bf51…f7515aNever scannednever seen before
- 5c13a65870d770d1642a…0c7009Never scannednever seen before
- 2cd3a2d4053954db1196…843c77Never scannednever seen before
- f13bae0ec08c91b4a315…4d6916Never scannednever seen before
- 503c433dcde2f3a9e7d3…044fdeNever 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.
- 4rule hits recorded
- 0 / 74engines flagged
- 2,316sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 isolated runtime environment classified the observed behavior as malicious.
Verdict inputView chapterProvenanceObservedSourceIsolated runtime analysisObserved at - 02
3 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: PrismLauncher-Windows-MSVC-Setup-11.0.3.exe — 3049faba7b69d515b2e036e9a8e28918d20e12f8d882f8e0d222e9b3909dcaaf
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\PrismLauncher-Windows-MSVC-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\nsnE04E.tmp\modern-wizard.bmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: nsDialogs.dll — C:\Users\<USER>\AppData\Local\Temp\nsnE04E.tmp\nsDialogs.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: aka.ms — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: i18n.prismlauncher.org — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
- Detect_NSIS_Nullsoft_Installer
- NSIS
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\DllHost.exe /Processid:{F32D97DF-E3E5-4CB9-9E3E-0EB5B4E49801}Sandbox 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.exe
0 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
- PrismLauncher-Windows-MSVC-Setup-11.0.3.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 22.7 MB
- Last analyzed
- Oct 7, 2026, 3:41 AM UTC
3049faba7b69d515b2e036e9a8e28918d20e12f8d882f8e0d222e9b3909dcaafSafety & 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 PrismLauncher-Windows-MSVC-Setup-11.0.3.exe safe, or is it malware?
What is PrismLauncher-Windows-MSVC-Setup-11.0.3.exe?
How many antivirus engines detected PrismLauncher-Windows-MSVC-Setup-11.0.3.exe?
What should I do if I already installed PrismLauncher-Windows-MSVC-Setup-11.0.3.exe?
How do I remove PrismLauncher-Windows-MSVC-Setup-11.0.3.exe?
What is the SHA-256 hash of PrismLauncher-Windows-MSVC-Setup-11.0.3.exe?
How up to date is this analysis of PrismLauncher-Windows-MSVC-Setup-11.0.3.exe?
Community
Member reviews and reports for this exact file hash.