Is BlueStacksInstaller.exe safe?
Unsigned installer with process-injection signals, four YARA hits, and three prior malicious imphash matches.
One low-trust engine flagged the file; no tier-1 detections. Runtime shows process injection and direct-IP traffic, four community YARA rules matched, and three similar imphash samples were previously malicious. Sandbox and child-file checks returned clean.
288401d581882eda9c…e598ed0fac3dedRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy 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.
One low-trust engine flagged the file; no tier-1 detections. Runtime shows process injection and direct-IP traffic, four community YARA rules matched, and three similar imphash samples were previously malicious. Sandbox and child-file checks returned clean.
The single low-trust detection and lack of tier-1 consensus normally suggest a false positive, yet the unsigned status, three offensive MITRE techniques, and four YARA rules create conflicting signals. Similar imphash files have been tied to msilzilla and malwarex families in prior verdicts. No sandbox verdict or malicious child was observed, and host-reputation data is unavailable. The combination of static and behavioural red flags outweighs the lone low-trust flag, placing the sample in mixed-signals territory.
What We Detected
76 engines scanned the file; only APEX (low-trust) returned a malicious label. The executable is unsigned and carries an installer filename hint. Four YARA rules from YARAify matched, including generic .NET and imphash patterns. Sandbox execution recorded three offensive MITRE techniques (T1055 process injection, T1134 token manipulation, T1562.001 impair defences) plus direct-IP connections to 12 addresses.
Threat Behavior
Process-injection activity and direct-IP traffic are consistent with both legitimate installers and commodity malware loaders. No malicious child files were dropped and the sandbox did not issue a malicious verdict. Three prior samples sharing the same imphash were classified malicious with families msilzilla and malwarex.
What To Do Now
Do not run the file on production systems. If installation is required, execute it in an isolated virtual machine and monitor for unexpected outbound connections or new processes. Keep endpoint protection enabled.
Where this verdict could be wrong2 caveats
- engines.tier1Malicious=0 and onlyLowTrustFlagging=true — single low-trust detection often false positive.
- hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false — no sandbox or child confirmation of malice.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 engine detections
- Sandbox returned no malicious verdict
- No malicious dropped children
- Unsigned executable
- Process-injection techniques observed
- Four community YARA rules matched
- Three prior malicious imphash matches
Treat as suspicious; run only in an isolated environment and monitor network activity until a definitive verdict is available.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial15 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete6 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
- 17MITRE ATT&CK techniques
- 13spawned processes
- 15network contacts
- 28filesystem & 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: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
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.
Moderate concern: Decoded or unpacked concealed content while running.
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
BlueStacksInstaller.exe
288401d581882eda9cb5ad8ff7b234bf6c5bd0699071d9ff7be598ed0fac3ded
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\BlueStacksInstaller.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
dw20.exe -x -s 872
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
86dc1580-d045-441a-a15d-991c5fc810dd
C:\ProgramData\Microsoft\Windows\WER\Temp\86dc1580-d045-441a-a15d-991c5fc810dd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
192.168.0.61
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.216.147.61
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.
- 192.168.0.61
- 23.216.147.61
- 23.96.180.189
- 23.196.145.221
- 23.41.4.206
- 184.27.218.92
- 23.216.147.74
- 192.168.0.26
- 20.99.133.109
- 23.55.140.42
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\86dc1580-d045-441a-a15d-991c5fc810dd
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\0b6ebcee-9bd2-4800-b81c-6ef492991026
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF39.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0D0.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF39.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0D0.tmp.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D54.tmp
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\a9488661-c8dd-4a59-8318-9062d6e20a6b
- 0x0
- Global\冰̕
- \Sessions\1\BaseNamedObjects\Global\AmiProviderMutex_InventoryApplicationFile
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 8fe786eb2aa1bbbecb15…6452daNever scannednever seen before
- a72418ccf6ef44f4f4d5…d01934Never 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.
- 6rule hits recorded
- 1 / 76engines flagged
- 22sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
5 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 76 antivirus engines flagged the file, including APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 4 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: BlueStacksInstaller.exe — 288401d581882eda9cb5ad8ff7b234bf6c5bd0699071d9ff7be598ed0fac3ded
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\BlueStacksInstaller.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — dw20.exe -x -s 872
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 86dc1580-d045-441a-a15d-991c5fc810dd — C:\ProgramData\Microsoft\Windows\WER\Temp\86dc1580-d045-441a-a15d-991c5fc810dd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 192.168.0.61 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.216.147.61 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
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.
- NETexecutableMicrosoft
- pe_imphash
- Skystars_Malware_Imphash
- Sus_CMD_Powershell_Usage
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.
Evidence"C:\Users\<USER>\Desktop\BlueStacksInstaller.exe"The 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.
Evidence23.216.147.61 · 23.96.180.189 · 23.196.145.221
1 of 76 engines flagged this file
View all 76 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- BlueStacksInstaller.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 183.5 KB
- Last analyzed
- Aug 14, 2026, 10:29 AM UTC
288401d581882eda9cb5ad8ff7b234bf6c5bd0699071d9ff7be598ed0fac3dedSafety & 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 run 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. Get a fresh copy 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 BlueStacksInstaller.exe safe, or is it malware?
What is BlueStacksInstaller.exe?
How many antivirus engines detected BlueStacksInstaller.exe?
I already downloaded and ran BlueStacksInstaller.exe — what should I do?
How do I remove BlueStacksInstaller.exe?
What is the SHA-256 hash of BlueStacksInstaller.exe?
How up to date is this analysis of BlueStacksInstaller.exe?
Community
Member reviews and reports for this exact file hash.