File scan report
Verdict Safe
Is Liquid Launcher_ 0. 6. 1_ x64- setup. exe safe? Yes, no threats found.
Unsigned but widely distributed NSIS-based LiquidLauncher installer that none of the 70 antivirus engines that checked it flagged, with sandbox activity matching an ordinary…
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
This installer looks like the genuine LiquidLauncher setup; download it only from the project's official release page and keep your security software enabled.
Good practice2 tips
We found nothing harmful in this file.
Install it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
1 point against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 70 antivirus engines that checked it flagged this LiquidLauncher setup file, and it has been submitted by nearly 500 distinct sources. In the sandbox it behaved like a normal installer, placing the launcher, an uninstaller and a Start Menu shortcut in the user profile.
No engine, including 17 major antivirus engines that returned a result, detected anything in this file. It has spread to 484 distinct submitters within about two months, typical of a popular open-source launcher release. The sandbox recorded no high-risk techniques and no named injection target; the injection mapping that appeared is one seen on many clean installers. Files written match a Tauri application packaged with the NSIS installer. The lack of a digital signature removes a publisher anchor but is common for open-source tools.
What We Detected
None of the 70 antivirus engines that checked it flagged this installer. It is unsigned, has no packer indicators, and its high overall entropy comes from the compressed installer overlay rather than packed code. A community note mentioned a generic third-party rule for XOR-encoded strings, which names no malware family.
Threat Behavior
In the sandbox runs the installer extracted standard NSIS helper libraries to the temp folder, then installed the launcher program, an uninstaller and a Start Menu shortcut under the user's local application data. No high-risk techniques, injection targets or persistence changes were recorded, and no network contacts by the sample were observed.
What To Do Now
The file appears to be a legitimate application installer. Obtain it from the project's official release channel and keep your antivirus enabled as usual.
Where this verdict could be wrong2 caveats
- The installer is unsigned, so there is no verified publisher identity behind it.
- A community note reported a generic suspicious-XOR pattern rule match from a third-party scanner, though it names no malware family and no engine currently flags the file.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 70 antivirus engines that checked it flagged the file.
- Submitted by 484 distinct sources, indicating broad legitimate distribution.
- Sandbox activity matched a standard application install with no high-risk techniques.
- No packer or obfuscation indicators in the executable code.
- The installer carries no digital signature, so the publisher cannot be verified from the file itself.
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 23sandbox rule tags
- 2spawned processes
- 0network contacts
- 23filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
23MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1010
- T1012
- T1027· Obfuscated code
- T1033· Reads user info
- T1055· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1112
- T1115
- T1125
- T1129· Loads modules
- T1134
- T1222
- T1485
- T1497· Sandbox evasion
- T1497.001· Sandbox evasion
- T1518· Checks your AV
- T1529
- T1547.009· Auto-start
- T1574· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
LiquidLauncher_0.6.1_x64-setup.exe"C:\Users\<USER>\Desktop\LiquidLauncher_0.6.1_x64-setup.exe"LiquidLauncher_0.6.1_x64-setup.exe"C:\Users\user\Desktop\LiquidLauncher_0.6.1_x64-setup.exe"
Files
21Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\nseD6B9.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\System.dll - Written
C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\modern-wizard.bmp - Written
C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\nsDialogs.dll - Written
C:\Users\<USER>\AppData\Local\Temp\nskD6DA.tmp\nsis_tauri_utils.dll - Written
C:\Users\<USER>\AppData\Local\LiquidLauncher\liquidlauncher.exe
Show all 21 entries for files
- Written
C:\Users\<USER>\AppData\Local\LiquidLauncher\uninstall.exe - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\LiquidLauncher.lnk - Written
C:\Users\<USER>\AppData\Local\Temp\nsxF138.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\nsnF197.tmp\System.dll - Written
C:\Users\<USER>\AppData\Local\Temp\nsnF197.tmp\modern-wizard.bmp - Written
C:\Users\<USER>\AppData\Local\Temp\nsnF197.tmp\nsDialogs.dll - Written
C:\Users\user\AppData\Local\Microsoft\Windows\Caches - Written
C:\Users\user\AppData\Local\Temp - Written
C:\Users\user\AppData\Local\Temp\ - Deleted
C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin - Deleted
C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update - Deleted
C:\Users\<USER>\AppData\Local\Temp\nsxF0E9.tmp - Deleted
C:\Users\<USER>\AppData\Local\Temp\nsnF197.tmp - Deleted
C:\Users\user\AppData\Local\Temp\nsbDA4D.tmp - Deleted
C:\Users\user\AppData\Local\Temp\nsrC193.tmp
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
cversions.3.mGlobal\OneSettingQueryMutex+compat+encapsulation
Sandbox background — not the file
9The analysis machine's own processes and connections, recorded in every run.
- VM process
Explorer.EXEC:\Windows\Explorer.EXE - VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
lsass.exeC:\Windows\system32\lsass.exe
Show all 9 entries for sandbox background — not the file
- VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p
Files this sample writes at runtime
This file drops 7 children at runtime. None are currently flagged malicious in our cache. 7 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 7215aff36096fb0b63b8…4dd343Not checkedno saved verdict
- 9bc38434f5050ce7b94a…076c19Not checkedno saved verdict
- e1901fb976b7001d34b2…464faaNot checkedno saved verdict
- 6722abb3265dc6b8cf32…564fecNot checkedno saved verdict
- 5ba143b5db4a87d32d6e…ad4709Not checkedno saved verdict
- a25831eb8fc38382376e…c563c2Not checkedno saved verdict
- 310a0cefe33ee3c6d11e…771de1Not checkedno saved verdict
Chapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 7, 2026, 1:34 AM UTC
- SHA-256
ae4098ab203530e0351dc2ad75260a81858a8f1925bd1dce3335f402a1aff34a- SHA-1
80f266fb6eed6ba472eae4cb68f1ba73a52c4106- MD5
7bbf2c744814a8884973d8573b60567d
About this file
LiquidLauncher_0.6.1_x64-setup.exe is a Win32 EXE file of 7.8 MB.
- Type and size
- Win32 EXE · 7.8 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 22, 2026On VirusTotal.
- Submitted by
- 484 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Antivirus consensus
0 of 70 engines flagged this file
5 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines0flagged
- Tier-236 engines0flagged
- Low-trust17 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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 uploaded, but first seen within the last six months. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is LiquidLauncher_0.6.1_x64-setup.exe safe?
What is LiquidLauncher_0.6.1_x64-setup.exe?
How many antivirus engines detected LiquidLauncher_0.6.1_x64-setup.exe?
What is the SHA-256 hash of LiquidLauncher_0.6.1_x64-setup.exe?
Is it safe to install 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.