Is PrismLauncher-Cracked-main.zip safe?
Zero detections across 75 engines, one clean sandbox run, medium prevalence, research-tool filename pattern.
No engine flagged the ZIP; sandbox showed no malicious verdict. Two direct-IP contacts exist but host reputation was not cross-checked. Filename matches research-tool patterns and prevalence is medium.
ec053f88d338794634…1391ba15343c38Recommended next actions
Before opening or extracting
Open or extract it only when its sender or download source has been independently verified.
If you already opened or extracted 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.
No engine flagged the ZIP; sandbox showed no malicious verdict. Two direct-IP contacts exist but host reputation was not cross-checked. Filename matches research-tool patterns and prevalence is medium.
All 75 reporting engines returned clean. Sandbox executed the archive without malicious verdict and dropped ten children, none malicious. The two contacted IPs lack host-reputation coverage, so their status is unknown. Filename heuristics label it a research tool and prevalence is medium, consistent with a cracked or modified launcher archive rather than widespread malware.
What We Detected
75 engines scanned the 5.2 MB ZIP; none returned malicious or suspicious labels. Sandbox analysis observed two direct-IP connections and typical unarchiver activity, but no malicious verdict or dropped malicious children.
Threat Behavior
Observed MITRE techniques are limited to process-name manipulation and debug-environment detection—common in modified game launchers. No persistence, C2 domains, or registry changes were recorded.
What To Do Now
Keep antivirus enabled. If you obtained the file from an unofficial source, consider the official Prism Launcher repository instead. The incomplete host-reputation check on the two IPs is the only remaining uncertainty.
Where this verdict could be wrong1 caveat
- contactedHosts=null — host-reputation cross-check incomplete; cannot confirm whether the two contacted IPs (150.171.110.195, 150.171.73.13) are known-malicious.
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 malicious
- sandbox verdict clean
- medium prevalence over 42 days
- no malicious dropped children
- contactedHosts cross-check incomplete
- filename contains 'Cracked'
File can be treated as safe for research or testing purposes; continue using endpoint protection and prefer official distribution channels.
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
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 8MITRE ATT&CK techniques
- 15spawned processes
- 2network contacts
- 15filesystem & 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-Cracked-main.zip
ec053f88d33879463494f5bcb76a712e5f0ac3b4f728be65871391ba15343c38
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" "C:\Users\<USER>\AppData\Local\Temp\PrismLauncher-Cracked-main/launcher/resources/documents/credits.html"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 2620 -s 2300
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
0160ca4f-9f43-4c46-91cd-1145766b90ad
C:\ProgramData\Microsoft\Windows\WER\Temp\0160ca4f-9f43-4c46-91cd-1145766b90ad
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
150.171.110.195
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
150.171.73.13
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 and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 150.171.110.195
- 150.171.73.13
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\0160ca4f-9f43-4c46-91cd-1145766b90ad
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\5ea8f4ff-bbda-48ec-b590-e69ab1b81b61
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 1d30e46f2b89d7bf02cb…8740b1Never scannednever seen before
- 1b7c5631d6085ef6ae0c…8ea7e7Never scannednever seen before
- af852b1924254464919c…b8baa2Never scannednever seen before
- e1e00d3bdf1572906698…59e127Never scannednever seen before
- 1693c68f8c990c93a0b1…4e26f8Never scannednever seen before
- c0eeddf121b5315caa3c…487d63Never scannednever seen before
- 1d51124ec82b5fad8b03…f6be0fNever scannednever seen before
- f20fe79754d94f6159ca…d52e2aNever scannednever seen before
- 8bb50c46cb5aba113ea7…67d401Never scannednever seen before
- d1e7d1385577be4b7a71…0707bdNever 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.
- 1rule hit recorded
- 0 / 75engines flagged
- 130sources 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 hash has been submitted 145 times from 130 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: PrismLauncher-Cracked-main.zip — ec053f88d33879463494f5bcb76a712e5f0ac3b4f728be65871391ba15343c38
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" "C:\Users\<USER>\AppData\Local\Temp\PrismLauncher-Cracked-main/launcher/resources/documents/credits.html"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\WerFault.exe -u -p 2620 -s 2300
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 0160ca4f-9f43-4c46-91cd-1145766b90ad — C:\ProgramData\Microsoft\Windows\WER\Temp\0160ca4f-9f43-4c46-91cd-1145766b90ad
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 150.171.110.195 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 150.171.73.13 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The 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.
Evidence150.171.110.195 · 150.171.73.13
0 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
- PrismLauncher-Cracked-main.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 5.0 MB
- Last analyzed
- Aug 29, 2026, 12:17 PM UTC
ec053f88d33879463494f5bcb76a712e5f0ac3b4f728be65871391ba15343c38Safety & 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
Open or extract it only when its sender or download source has been independently verified.
- 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-Cracked-main.zip safe?
What is PrismLauncher-Cracked-main.zip?
How many antivirus engines detected PrismLauncher-Cracked-main.zip?
What is the SHA-256 hash of PrismLauncher-Cracked-main.zip?
Is it safe to open or extract PrismLauncher-Cracked-main.zip?
How up to date is this analysis of PrismLauncher-Cracked-main.zip?
Community
Member reviews and reports for this exact file hash.