Is CrystalLauncherInstaller.NX.exe safe?
Unsigned installer with zero engine detections, common prevalence, and no malicious children or host contacts.
All 75 engines are clean. The file is a widely submitted installer that writes a Java runtime and launcher files. Sandbox shows process activity but no malicious verdict or known-bad network destinations.
7b94de8df91be707e5…411ae73837c35dRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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.
All 75 engines are clean. The file is a widely submitted installer that writes a Java runtime and launcher files. Sandbox shows process activity but no malicious verdict or known-bad network destinations.
Zero detections across 75 engines, including 17 tier-1 engines, removes any malware-family signal. The file is unsigned, yet its 1605 submissions over 221 days and 1313 unique sources indicate commodity distribution rather than targeted malware. Dropped children and contacted hosts show no malicious indicators. While the imphash matches one prior hacktool sample, that file had 53 malicious detections; the current sample has none. The triggered heuristics reflect generic installer behaviour rather than confirmed malicious intent.
What We Detected
75 antivirus engines scanned the sample; none returned a malicious or suspicious result. The executable is unsigned and contains no code-signing certificate. Sandbox execution recorded four MITRE techniques labelled offensive (T1055, T1485, T1562.001, T1620) but produced no malicious sandbox verdict.
Threat Behavior
The installer drops a Java runtime and Crystal-Launcher files, creates desktop shortcuts, and contacts launcher.crystal-launcher.net over HTTPS. No dropped child file or contacted host appears in our malicious cache. The imphash matches prior samples, one of which was labelled Extreme Injector, but that sample triggered 53 engines while this one triggers zero.
What To Do Now
Keep Windows Defender and other endpoint protection enabled. If the software is obtained from the official Crystal Launcher site and matches expected behaviour, it can be used; otherwise treat any unexpected executable with caution.
Where this verdict could be wrong1 caveat
- similarHashes contains one malicious verdict (extremeinjector) on the same imphash, but that sample had 53/75 engines malicious while this file has zero detections.
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 detections across 75 engines
- Common-old prevalence with 1313 unique sources
- No malicious dropped children
- no complete contacted-host reputation result was available
- Unsigned executable
- Process-injection and LSASS-access techniques observed in sandbox
The sample shows no malicious indicators from engines or external intelligence; standard security software should remain active while using the installer.
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 of 5 contacted hosts were cross-checked; coverage is incomplete.
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
- 28MITRE ATT&CK techniques
- 12spawned processes
- 6network contacts
- 32filesystem & 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
CrystalLauncherInstaller.NX.exe
7b94de8df91be707e5f14d6f0348af435c4ad5ec3cf294e666411ae73837c35d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
launchlog.txt
C:\Users\<USER>\AppData\Local\CrystalLauncherInstallerNX\launchlog.txt
04Isolated runtime analysis - Written fileObserved
crystalRuntime
C:\Users\<USER>\AppData\Local\CrystalLauncherInstallerNX\crystalRuntime
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.21.77.167
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.216.81.253
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.
- 104.21.77.167
- 23.216.81.253
- 8.8.8.8
- 172.67.210.66
- https://launcher.crystal-launcher.net:443/bootstrapNX/static/runtimes.xml
- https://launcher.crystal-launcher.net/bootstrapNX/static/runtimes.xml
- C:\Users\<USER>\AppData\Local\CrystalLauncherInstallerNX\launchlog.txt
- C:\Users\<USER>\AppData\Local\CrystalLauncherInstallerNX\crystalRuntime
- C:\Users\<USER>\AppData\Local\CrystalLauncherInstallerNX\language.flag
- C:\Users\<USER>\AppData\Roaming\.crystalinst
- C:\Users\<USER>\AppData\Local\CrystalLauncherInstallerNX\crystalRuntimeBranch
- C:\Users\<USER>\AppData\Roaming\Crystal-Launcher\launcher.exe:Zone.Identifier
- C:\Users\<USER>\AppData\Roaming\Crystal-Launcher\runtime\64\jdk-17.0.1+12\release.tmp
- C:\Users\<USER>\AppData\Roaming\Crystal-Launcher\runtime\64\jdk-17.0.1+12\bin\api-ms-win-core-console-l1-1-0.dll.tmp
- C:\Users\<USER>\AppData\Roaming\Crystal-Launcher\runtime\64\jdk-17.0.1+12\bin\api-ms-win-core-console-l1-2-0.dll.tmp
- C:\Users\<USER>\AppData\Roaming\Crystal-Launcher\runtime\64\jdk-17.0.1+12\bin\api-ms-win-core-datetime-l1-1-0.dll.tmp
- cversions.3.m
- \Sessions\1\BaseNamedObjects\DBWinMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 3be05b3e69d1b36e3a1e…ada510Never scannednever seen before
- ac3706ebbb78cfba74e5…0aba8fNever scannednever seen before
- 2475272f129a0b36bd9b…61dce8Never scannednever seen before
- e9419f6d87e8205c8397…c42eb0Never scannednever seen before
- 41777e1e10bae7763ceb…ae8f77Never scannednever seen before
- ce7cee34364a43a7b0ec…5f04afNever scannednever seen before
- a865bfc17913dacddfae…50e960Never scannednever seen before
- 364c39cb89e2fcaa06aa…f9948aNever scannednever seen before
- dbd3a49d0d906b4ed921…17151cNever scannednever seen before
- 6c8437d9c7ed0ddda1e4…301c0cNever 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
- 1,313sources 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 a long, established submission history across 1,313 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: CrystalLauncherInstaller.NX.exe — 7b94de8df91be707e5f14d6f0348af435c4ad5ec3cf294e666411ae73837c35d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: launchlog.txt — C:\Users\<USER>\AppData\Local\CrystalLauncherInstallerNX\launchlog.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: crystalRuntime — C:\Users\<USER>\AppData\Local\CrystalLauncherInstallerNX\crystalRuntime
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.21.77.167 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.216.81.253 — 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.
Evidence104.21.77.167 · 23.216.81.253 · 172.67.210.66
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- CrystalLauncherInstaller.NX.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 1.5 MB
- Last analyzed
- Aug 22, 2026, 5:09 PM UTC
7b94de8df91be707e5f14d6f0348af435c4ad5ec3cf294e666411ae73837c35dSafety & 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
Run it only when it came from the developer's official site or another source you independently trust.
- 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 CrystalLauncherInstaller.NX.exe safe?
What is CrystalLauncherInstaller.NX.exe?
How many antivirus engines detected CrystalLauncherInstaller.NX.exe?
What is the SHA-256 hash of CrystalLauncherInstaller.NX.exe?
Is it safe to run CrystalLauncherInstaller.NX.exe?
How up to date is this analysis of CrystalLauncherInstaller.NX.exe?
Community
Member reviews and reports for this exact file hash.