File scan report
Verdict Safe
Is Liquid
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
Includes 23 mapped techniques, every process, file, registry and network entry and 7 dropped files.
Show the technical evidenceChapter 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.
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 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.