Is zstream-app.exe safe?
A completed sandbox flagged harmful execution involving process injection, LSASS targeting, destructive-impact capability, and defense impairment, reinforced by seven antivirus detections.
One completed sandbox produced a malware finding and recorded offensive techniques including process injection, impact activity, and security-control impairment. Seven of 75 engines detected the unsigned executable, including Microsoft, although the lack of tier-1 family consensus prevents reliable attribution to a specific malware family.
c71092e7a1b417e888…8f80a5d9faa349Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran 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.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
One completed sandbox produced a malware finding and recorded offensive techniques including process injection, impact activity, and security-control impairment. Seven of 75 engines detected the unsigned executable, including Microsoft, although the lack of tier-1 family consensus prevents reliable attribution to a specific malware family.
Runtime evidence is the strongest concern: one completed sandbox produced a malware finding and mapped execution to T1055, T1485, and T1562.001. A separate saved heuristic reports activity targeting LSASS, which is strongly associated with credential-access attempts and is not expected from an ordinary streaming application. Seven of 75 engines detected the executable, including Microsoft's Wacatac machine-learning label, but most tier-1 products remained silent and no family achieved consensus. The executable is unsigned, so there is no authenticated publisher history to counterbalance these findings. Its direct no complete contacted-host reputation result was available or hostile because contactedHosts is null and no complete reputation check was saved.
What We Detected
Seven of 75 antivirus engines flagged the executable. Microsoft reported Trojan:Win32/Wacatac.B!ml, while CrowdStrike, Skyhigh, TrellixENS, and others used generic or machine-learning labels. The labels do not establish a reliable named family, but they reinforce the runtime findings.
Threat Behavior
One completed sandbox produced a malware finding. Recorded offensive techniques include T1055 process injection, T1485 data destruction, and T1562.001 impairment of defenses. Saved evidence also indicates targeting of LSASS, a sensitive Windows credential process. The sample contacted 150.171.27.11 directly, but no complete host-reputation result is available, so that connection cannot be independently characterized.
What To Do Now
Do not run the file on a production system. If it already executed, isolate the device, keep endpoint protection enabled, perform a full scan, review credentials used on the system, and investigate signs of process injection or credential access.
Where this verdict could be wrong5 caveats
- Only 1/17 tier-1 engines detected the file, while Avast, BitDefender, ESET-NOD32, Fortinet, and other tier-1 engines did not.
- engines.tier1FamilyConsensus.family=null, and the seven labels are generic or machine-learning detections rather than a consistent named family.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false; these absences may reflect coverage gaps.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false, providing no static packing indicator.
- droppedChildren.hasMaliciousChild=false, although all 10 child verdicts remain unknown.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 16/17 tier-1 engines did not detect the sample
- engines.tier1FamilyConsensus.strong=false
- droppedChildren.hasMaliciousChild=false
- externalIntel.yaraify.ruleCount=0
- peAnalysis.likelyPacked=false
- behaviour.hasMaliciousSandboxVerdict=true
- T1055 process-injection activity
- LSASS-targeting activity reported by MalwareTips.Synth.CredentialDumper
- T1562.001 security-control impairment
- T1485 destructive-impact technique
- 7/75 antivirus detections, including Microsoft
Quarantine the file and avoid execution. If it has run, isolate the endpoint, keep all protection enabled, scan fully, and investigate LSASS access, injected processes, and possible credential exposure.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete7 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 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
- 18MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 36filesystem & 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: 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.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
zstream-app.exe
c71092e7a1b417e888776818b7b61d0502ae5cdf41873525538f80a5d9faa349
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\zstream-app.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files (x86)\Microsoft\EdgeWebView\Application\122.0.2365.92\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=zstream-app.exe --webview-exe-version=1.0.0 --user-data-dir="C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --disable-features=msSmartScreenProtection --enable-features=MojoIpcz --mojo-named-platform-channel-pipe=5804.2216.17987549767321032353
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
throttle_store.dat
C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Crashpad\throttle_store.dat
04Isolated runtime analysis - Written fileObserved
settings.dat
C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Crashpad\settings.dat
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
150.171.27.11
Contact observed during runtime.
06Isolated runtime analysis
6 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; 1 returned "malicious".
Adversary techniques mapped to the MITRE ATT&CK framework.
- 150.171.27.11
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeUpdate\ClientState\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}\dr
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeWebView\StabilityMetrics\user_experience_metrics.stability.exited_cleanly
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\ClientStateMedium\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}\usagestats
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeWebView\PreferenceMACs\Default\media.cdm.origin_data
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeWebView\PreferenceMACs\Default\media.storage_id_salt
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeWebView\PreferenceMACs\Default\edge.services.account_id
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Crashpad\throttle_store.dat
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Crashpad\settings.dat
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\BrowserMetrics\BrowserMetrics-6AB1CD91-1544.pma
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\lockfile
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Variations
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\BrowserMetrics-spare.pma
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\fd31b218-66cd-42c3-9f5a-35672f51fc9c.tmp
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Default\Code Cache\js\index-dir\the-real-index
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Default\Sync Data\LevelDB\000001.dbtmp
- C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Default\Site Characteristics Database\000001.dbtmp
- Local\ChromeProcessSingletonStartup!
- __OMADM_NAMED_MUTEX__
- Global\OneSettingQueryMutex+compat+encapsulation
- \Sessions\1\BaseNamedObjects\DBWinMutex
- \Sessions\1\BaseNamedObjects\Local\ChromeProcessSingletonStartup!
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fbcfe23a2ecb82b7100c…dc0f2dNever scannednever seen before
- a0c9abae18599f0a65fc…e38e87Never scannednever seen before
- b1e963d702392fb72247…c0cdecNever scannednever seen before
- 5dfc321417fc31359f23…4a2026Never scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never scannednever seen before
- 4f53cda18c2baa0c0354…02b945Never scannednever seen before
- deba77bc71479c2e98a7…e1c573Never scannednever seen before
- 0628922305d2478ba75a…e28107Never scannednever seen before
- 79b107307408e5ad9a14…25b3b1Never scannednever seen before
- 8f7df796a704e2ed968d…939398Never 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.
- 3rule hits recorded
- 7 / 75engines flagged
- 57sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 isolated runtime environment classified the observed behavior as malicious.
Verdict inputView chapterProvenanceObservedSourceIsolated runtime analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
7 of 75 antivirus engines flagged the file, including Bkav and CrowdStrike.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: zstream-app.exe — c71092e7a1b417e888776818b7b61d0502ae5cdf41873525538f80a5d9faa349
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\zstream-app.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files (x86)\Microsoft\EdgeWebView\Application\122.0.2365.92\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=zstream-app.exe --webview-exe-version=1.0.0 --user-data-dir="C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --disable-features=msSmartScreenProtection --enable-features=MojoIpcz --mojo-named-platform-channel-pipe=5804.2216.17987549767321032353
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: throttle_store.dat — C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Crashpad\throttle_store.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: settings.dat — C:\Users\<USER>\AppData\Roaming\zstream-app.exe\EBWebView\Crashpad\settings.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 150.171.27.11 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
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\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.27.11
7 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- zstream-app.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 24.0 MB
- Last analyzed
- Sep 30, 2026, 8:19 AM UTC
c71092e7a1b417e888776818b7b61d0502ae5cdf41873525538f80a5d9faa349Safety & 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 run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran 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
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy 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 zstream-app.exe malware?
What is zstream-app.exe?
How many antivirus engines detected zstream-app.exe?
I already downloaded and ran zstream-app.exe — what should I do?
How do I remove zstream-app.exe?
What kind of malware is zstream-app.exe?
What is the SHA-256 hash of zstream-app.exe?
How up to date is this analysis of zstream-app.exe?
Community
Member reviews and reports for this exact file hash.