Is LiquidLauncher_0.5.0_x64_en-US.msi safe?
Malicious file assessment
6 high-confidence signature or behavior rules matched this file.
ac86ca5150d64af0b5…3c019e920733c1Recommended next actions
Before installing
Do not install it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already installed it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 4 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete8 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
- 13MITRE ATT&CK techniques
- 14spawned processes
- 4network contacts
- 38filesystem & 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: Used removable-media replication behaviour that can spread files between devices.
High concern: Created or modified a system service, which can keep code running.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Communicates over the network in a non-standard way.
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.
Threat context
How info-stealers work
An info-stealer runs quietly in the background and copies your private data — saved passwords, browser cookies, autofill details, and crypto wallets — then sends it to criminals. You usually won't notice anything is wrong.
Bottom line:Stolen logins are used to break into your accounts or sold in bulk on criminal markets.
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.5.0_x64_en-US.msi
ac86ca5150d64af0b55e22f65adac3cfd13aac88868085fcea3c019e920733c1
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\installer.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ngen.log
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
04Isolated runtime analysis - Written fileObserved
~DFB2F0C3C9E7239F29.TMP
C:\Windows\Temp\~DFB2F0C3C9E7239F29.TMP
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
150.171.22.17
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
93.186.135.80
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.22.17
- 93.186.135.80
- http://cacerts.digicert.com/DigiCertGlobalRootG2.crt
- http://msedge.f.tlu.dl.delivery.mp.microsoft.com/filestreamingservice/files/0c4084f3-1bed-4246-b8ed-206ccbe60e3c?P1=1754072141&P2=404&P3=2&P4=YWHjm+6z7MOPIf597feSbOWCurKGWP+6G49g1m6lr14e2C3l9ofyr2ijjOBmKm0wt3dn2HQDKYk2JYN23ofq2w==
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
- C:\Windows\Temp\~DFB2F0C3C9E7239F29.TMP
- C:\Windows\Temp\~DF2FC5AD4ACEC0370D.TMP
- C:\Windows\Temp\~DF9EFF7642AABBB1BD.TMP
- C:\Windows\Temp\~DF1648FCF70DA30D77.TMP
- C:\Config.Msi\CMPEA31.tmp
- C:\Config.Msi
- C:\Windows\Installer\e467.msi
- C:\Config.Msi\CMPEE96.tmp
- C:\Config.Msi\e466.rbs
- Global\_MSIExecute
- Local\MSCTF.Asm.MutexDefault1
- \Sessions\1\BaseNamedObjects\Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:1616:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:1616:120:WilError_03
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- c5ae2be40fc540c96371…141ec5Never scannednever seen before
- 9c595a347c0157e31ac9…d325d1Never scannednever seen before
- 2026f1aa8b8edbeca986…5f2f59Never scannednever seen before
- a428891ad555debdf739…95249aNever scannednever seen before
- c3daa73d6bca245f683d…ec90b6Never scannednever seen before
- 10d3274b67d28275461e…9c3e2eNever scannednever seen before
- 3ea9329a7824a9f979a4…503841Never scannednever seen before
- 71354da209a1fad06a3f…a45a48Never scannednever seen before
- ee562340edef4b0bda92…193fafNever scannednever seen before
- 9bd19eb5493a6268b1bc…db7652Never 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.
- 8rule hits recorded
- 0 / 74engines flagged
- 3,676sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 3,676 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: LiquidLauncher_0.5.0_x64_en-US.msi — ac86ca5150d64af0b55e22f65adac3cfd13aac88868085fcea3c019e920733c1
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\installer.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ngen.log — C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ~DFB2F0C3C9E7239F29.TMP — C:\Windows\Temp\~DFB2F0C3C9E7239F29.TMP
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 150.171.22.17 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 93.186.135.80 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: infostealer
One or more independent reference databases matched 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.
- DebuggerCheck__API
- NET
- Sus_Obf_Enc_Spoof_Hide_PE
- upxHook
- maldoc_find_kernel32_base_method_1
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox 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.
Evidence150.171.22.17 · 93.186.135.80
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
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
- LiquidLauncher_0.5.0_x64_en-US.msi
- Format
- Windows Installer
- Code signing
- No verified publisher
- Size
- 9.2 MB
- Last analyzed
- Jul 3, 2026, 3:26 PM UTC
ac86ca5150d64af0b55e22f65adac3cfd13aac88868085fcea3c019e920733c1Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't install this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already installed it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- Recovery step 04
Download a fresh installer from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is LiquidLauncher_0.5.0_x64_en-US.msi malware?
What is LiquidLauncher_0.5.0_x64_en-US.msi?
How many antivirus engines detected LiquidLauncher_0.5.0_x64_en-US.msi?
I already downloaded and installed LiquidLauncher_0.5.0_x64_en-US.msi — what should I do?
How do I remove LiquidLauncher_0.5.0_x64_en-US.msi?
What kind of malware is LiquidLauncher_0.5.0_x64_en-US.msi?
What is the SHA-256 hash of LiquidLauncher_0.5.0_x64_en-US.msi?
How up to date is this analysis of LiquidLauncher_0.5.0_x64_en-US.msi?
Community
Member reviews and reports for this exact file hash.