Is LiquidLauncher_0.6.1_x64-setup.exe safe?
Unsigned installer shows sandbox process-injection and LSASS access despite zero engine detections.
No antivirus engine flagged the file, yet sandbox evidence shows process injection and LSASS access. Similar imphash samples were previously rated suspicious or malicious. The combination of unsigned status and offensive MITRE techniques keeps the file in mixed-signals territory.
ae4098ab203530e035…35f402a1aff34aRecommended 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.
No antivirus engine flagged the file, yet sandbox evidence shows process injection and LSASS access. Similar imphash samples were previously rated suspicious or malicious. The combination of unsigned status and offensive MITRE techniques keeps the file in mixed-signals territory.
Zero detections across 75 engines rules out a clear malicious consensus, but the sandbox recorded T1055 process injection, T1134 token manipulation, and T1485 data destruction. The file is unsigned and its imphash matches four prior samples that received suspicious or malicious verdicts. Prevalence is common_new, indicating the installer is circulating, yet the lack of a trusted publisher and the presence of LSASS-targeted activity prevent a clean classification.
What We Detected
75 engines returned zero malicious or suspicious flags. The executable is unsigned and carries an NSIS-style installer footprint. Sandbox execution recorded process injection (T1055), token manipulation (T1134), and data-destruction attempts (T1485), plus direct LSASS memory access.
Threat Behavior
Offensive MITRE techniques observed in a single sandbox run suggest the installer may drop or execute additional payloads capable of credential access. No dropped child files were flagged malicious, and no external C2 domains were contacted during the observed execution window.
What To Do Now
Do not run the installer on production systems. Keep Windows Defender and other endpoint protection enabled. If the software is required, execute it only in an isolated virtual machine and monitor for unexpected child processes or registry changes.
Where this verdict could be wrong1 caveat
- communityComments[0] reports only a single low-confidence YARA rule (SUSP_XORed_PE_ImportNames) with 1/72 AV ratio.
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_new prevalence with hundreds of submitters
- No malicious dropped children
- Unsigned PE installer
- Sandbox observed LSASS access
- MITRE T1055, T1134, T1485 triggered
- Imphash previously linked to suspicious samples
Treat the file as untrusted; run only in an isolated environment if testing is necessary and keep all security software active.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 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
- 23MITRE ATT&CK techniques
- 11spawned processes
- 0network contacts
- 23filesystem & 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: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
LiquidLauncher_0.6.1_x64-setup.exe
ae4098ab203530e0351dc2ad75260a81858a8f1925bd1dce3335f402a1aff34a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\LiquidLauncher_0.6.1_x64-setup.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
nseD6B9.tmp
C:\Users\<USER>\AppData\Local\Temp\nseD6B9.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\System.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\<USER>\AppData\Local\Temp\nseD6B9.tmp
- C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\nsis_tauri_utils.dll
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\<USER>\AppData\Local\Temp\nsxF0E9.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsnF197.tmp
- C:\Users\user\AppData\Local\Temp\nsbDA4D.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.
- 7215aff36096fb0b63b8…4dd343Never scannednever seen before
- 9bc38434f5050ce7b94a…076c19Never scannednever seen before
- b1350f487692057c8ffd…551fc0Never scannednever seen before
- 9baee42d66f715bba878…b40256Never scannednever seen before
- e1901fb976b7001d34b2…464faaNever scannednever seen before
- 8b4c47c4cf5e76ec57dd…90d37cNever scannednever seen before
- 6722abb3265dc6b8cf32…564fecNever scannednever seen before
- 5ba143b5db4a87d32d6e…ad4709Never scannednever seen before
- a25831eb8fc38382376e…c563c2Never scannednever seen before
- 310a0cefe33ee3c6d11e…771de1Never 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.
- 2rule hits recorded
- 0 / 75engines flagged
- 484sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 535 times from 484 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: LiquidLauncher_0.6.1_x64-setup.exe — ae4098ab203530e0351dc2ad75260a81858a8f1925bd1dce3335f402a1aff34a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\LiquidLauncher_0.6.1_x64-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nseD6B9.tmp — C:\Users\<USER>\AppData\Local\Temp\nseD6B9.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\System.dll
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.exe
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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- LiquidLauncher_0.6.1_x64-setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 7.4 MB
- Last analyzed
- Sep 7, 2026, 1:34 AM UTC
ae4098ab203530e0351dc2ad75260a81858a8f1925bd1dce3335f402a1aff34aSafety & 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 LiquidLauncher_0.6.1_x64-setup.exe safe, or is it malware?
What is LiquidLauncher_0.6.1_x64-setup.exe?
How many antivirus engines detected LiquidLauncher_0.6.1_x64-setup.exe?
What should I do if I already installed LiquidLauncher_0.6.1_x64-setup.exe?
How do I remove LiquidLauncher_0.6.1_x64-setup.exe?
What is the SHA-256 hash of LiquidLauncher_0.6.1_x64-setup.exe?
How up to date is this analysis of LiquidLauncher_0.6.1_x64-setup.exe?
Community
Member reviews and reports for this exact file hash.