Is Epic.Switcher.v4.2.0.exe safe?
Unsigned 40-day-old executable triggers three sandbox heuristics yet only a single low-trust engine flags it.
One low-trust engine and three synthesis heuristics (process injection, LSASS access, direct-IP) raise concern, but tier-1 engines are silent and no malicious sandbox verdict or known-bad host contact is recorded.
993b01326f7644183e…58883a8ce34c44Recommended 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 and three synthesis heuristics (process injection, LSASS access, direct-IP) raise concern, but tier-1 engines are silent and no malicious sandbox verdict or known-bad host contact is recorded.
The file is unsigned and shows MITRE techniques that malware often uses, yet the single detection is low-trust and the sandbox did not return a malicious verdict. Contacted-host reputation data is missing, so the two direct-no complete contacted-host reputation result was available or malicious. Medium prevalence and lack of RAG history leave the sample in mixed-signal territory.
What We Detected
73 engines scanned the sample; only Trapmine (low_trust) returned a malicious label. No tier-1 engine flagged it. The binary is unsigned and 40 days old with medium prevalence.
Threat Behavior
Sandbox execution recorded T1055 process injection, T1485 data destruction, and T1562.001 defense-evasion techniques plus LSASS access and direct-IP traffic to 150.171.27.11 and 162.159.36.2. No malicious sandbox verdict or dropped malicious children were observed.
What To Do Now
Keep antivirus enabled. Do not run the file on production systems until additional reputation or sandbox evidence becomes available.
Where this verdict could be wrong1 caveat
- Sandbox observed LSASS access and direct-IP traffic, but no malicious sandbox verdict or known-bad host correlation exists.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero tier-1 detections
- No malicious sandbox verdict
- No dropped malicious children
- Unsigned executable
- Sandbox heuristics for process injection and LSASS access
- Direct-IP traffic without domain context
Treat as suspicious; do not execute until further reputation data or a clean multi-engine consensus appears.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 73 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were 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
- 19MITRE ATT&CK techniques
- 15spawned processes
- 2network 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.
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
Epic.Switcher.v4.2.0.exe
993b01326f7644183e634f3fa1d8680bb195f3950fb1fa47c758883a8ce34c44
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Epic.Switcher.v4.2.0.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=Epic.Switcher.v4.2.0.exe --webview-exe-version=1.0.0 --user-data-dir="C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --disable-features=msSmartScreenProtection --enable-features=MojoIpcz --mojo-named-platform-channel-pipe=2768.4684.6163132955901198753
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
throttle_store.dat
C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\Crashpad\throttle_store.dat
04Isolated runtime analysis - Written fileObserved
settings.dat
C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.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 - Contacted hostObserved
162.159.36.2
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.27.11
- 162.159.36.2
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\Crashpad\throttle_store.dat
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\Crashpad\settings.dat
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\BrowserMetrics\BrowserMetrics-6A408D48-DF8.pma
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\lockfile
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\Variations
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\BrowserMetrics-spare.pma
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\510d6db4-c5b8-44cf-a8ce-5d50eeb5e1cc.tmp
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\Default\Code Cache\js\index-dir\the-real-index
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\Default\Code Cache\wasm\index-dir\the-real-index
- C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\Default\Code Cache\wasm\index-dir\temp-index
- 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.
- fb05ecdbc3955508d377…b3b11eNever scannednever seen before
- fbcfe23a2ecb82b7100c…dc0f2dNever scannednever seen before
- 7ec2a2c762786f7dac6e…8b3fe9Never scannednever seen before
- b7108dc589bc1313330b…fa5399Never scannednever seen before
- 7d1e1f79ec51b8f39559…b0f5feNever scannednever seen before
- 8f1018d161f6241e703c…192c6eNever scannednever seen before
- a0c9abae18599f0a65fc…e38e87Never scannednever seen before
- b1e963d702392fb72247…c0cdecNever scannednever seen before
- 5dfc321417fc31359f23…4a2026Never scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never 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
- 1 / 73engines flagged
- 6sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 73 antivirus engines flagged the file, including Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 6 times from 6 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Epic.Switcher.v4.2.0.exe — 993b01326f7644183e634f3fa1d8680bb195f3950fb1fa47c758883a8ce34c44
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Epic.Switcher.v4.2.0.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=Epic.Switcher.v4.2.0.exe --webview-exe-version=1.0.0 --user-data-dir="C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --disable-features=msSmartScreenProtection --enable-features=MojoIpcz --mojo-named-platform-channel-pipe=2768.4684.6163132955901198753
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: throttle_store.dat — C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\Crashpad\throttle_store.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: settings.dat — C:\Users\<USER>\AppData\Roaming\Epic.Switcher.v4.2.0.exe\EBWebView\Crashpad\settings.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 150.171.27.11 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
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 · 162.159.36.2
1 of 73 engines flagged this file
View all 73 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
- Epic.Switcher.v4.2.0.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 11.7 MB
- Last analyzed
- Aug 7, 2026, 5:46 AM UTC
993b01326f7644183e634f3fa1d8680bb195f3950fb1fa47c758883a8ce34c44Safety & 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 Epic.Switcher.v4.2.0.exe safe, or is it malware?
What is Epic.Switcher.v4.2.0.exe?
How many antivirus engines detected Epic.Switcher.v4.2.0.exe?
I already downloaded and ran Epic.Switcher.v4.2.0.exe — what should I do?
How do I remove Epic.Switcher.v4.2.0.exe?
What is the SHA-256 hash of Epic.Switcher.v4.2.0.exe?
How up to date is this analysis of Epic.Switcher.v4.2.0.exe?
Community
Member reviews and reports for this exact file hash.