Is WebexApp.exe safe?
Unsigned executable with three tier-1 detections and sandbox evidence of process injection plus scheduled-task persistence.
10 of 75 engines flagged the file, including three tier-1 engines that label it Agentb or Wacatac. Sandbox logs show LSASS access, process injection, and creation of SYSTEM-level scheduled tasks, all within the first day of submission.
0a5a093e44201689a0…7314d07ca5cd7cRecommended 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.
10 of 75 engines flagged the file, including three tier-1 engines that label it Agentb or Wacatac. Sandbox logs show LSASS access, process injection, and creation of SYSTEM-level scheduled tasks, all within the first day of submission.
The combination of tier-1 malicious detections, unsigned status, and multiple offensive MITRE techniques observed in sandbox outweighs the absence of external-intel hits. The file is rare and brand-new, so no historical reputation mitigates the risk. Direct-IP contact and dropped child file add supporting context but are not decisive on their own.
What We Detected
Three tier-3 engines (Kaspersky, Microsoft, Sophos) and seven additional engines returned malicious verdicts. The sample is unsigned despite the WebexApp.exe filename. Sandbox execution recorded LSASS memory access, process injection (T1055), and creation of two SYSTEM-level scheduled tasks for persistence.
Threat Behavior
The binary wrote multiple files to system directories, created mutexes, and contacted the IP 179.61.227.148 directly. No legitimate Webex components or signing certificates were present.
What To Do Now
Quarantine or delete the file. Do not execute it. Keep Windows Defender and other endpoint protection enabled; the observed behaviour matches common credential-theft and persistence patterns.
- Unsigned executable
- Process injection observed
- LSASS access (credential dumping)
- SYSTEM-level scheduled-task persistence
- Rare and brand-new submission
Block and remove the file; monitor for any dropped children or scheduled tasks created under similar names.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete10 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
Complete4 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
- 27MITRE ATT&CK techniques
- 11spawned processes
- 1network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Created or modified a scheduled task, which can provide persistence.
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
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.
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
WebexApp.exe
0a5a093e44201689a0a84cef0f60c0ea71427b8b37b0581a3c7314d07ca5cd7c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\cisco.exe"
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
SnjUuLf.exe:WindowsUpdate
C:\Windows\System32\SnjUuLf.exe:WindowsUpdate
04Isolated runtime analysis - Written fileObserved
RuntimeBroker.exe
C:\Windows\RuntimeBroker.exe
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
179.61.227.148
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 and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 179.61.227.148
- C:\Windows\System32\SnjUuLf.exe:WindowsUpdate
- C:\Windows\RuntimeBroker.exe
- C:\ProgramData\OneDriveUpdate.exe
- C:\Users\<USER>\Desktop\cisco.exe
- C:\Windows\System32\Tasks\zgX3QAStY6wddwSJ8BU1_297
- C:\ProgramData\OneDriveUpdate.exe
- C:\Users\<USER>\Desktop\cisco.exe
- C:\Windows\Tasks\zgX3QAStY6wddwSJ8BU1_297.job
- C:\Windows\Tasks\jZ4vwIDd3R4jL56_934.job
- Global\SyncRootManager
- Local\SessionImmersiveColorMutex
- NbLXlYe3Bfyl
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 6c816769f4ece5160cad…a139dfNever 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.
- 4rule hits recorded
- 10 / 75engines flagged
- 1sources 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
10 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: WebexApp.exe — 0a5a093e44201689a0a84cef0f60c0ea71427b8b37b0581a3c7314d07ca5cd7c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\cisco.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: SnjUuLf.exe:WindowsUpdate — C:\Windows\System32\SnjUuLf.exe:WindowsUpdate
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: RuntimeBroker.exe — C:\Windows\RuntimeBroker.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 179.61.227.148 — 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.
Sample spawned schtasks / PowerShell scheduled-task cmdlets / sc create. Persistence mechanism.
Evidenceschtasks /create /tn "zgX3QAStY6wddwSJ8BU1_297" /tr "\"C:\Windows\RuntimeBroker.exe\"" /sc onlogon /rl highest /ru SYSTEM /fThe 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 LocalSystemNetworkRestricted -p -s WdiSystemHostSandbox 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.
Evidence179.61.227.148
10 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
Barely seen in the wild and first surfaced recently. 10 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- WebexApp.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 400.3 KB
- Last analyzed
- Aug 17, 2026, 12:33 AM UTC
0a5a093e44201689a0a84cef0f60c0ea71427b8b37b0581a3c7314d07ca5cd7cSafety & 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 WebexApp.exe malware?
What is WebexApp.exe?
How many antivirus engines detected WebexApp.exe?
I already downloaded and ran WebexApp.exe — what should I do?
How do I remove WebexApp.exe?
What kind of malware is WebexApp.exe?
What is the SHA-256 hash of WebexApp.exe?
How up to date is this analysis of WebexApp.exe?
Community
Member reviews and reports for this exact file hash.