Is weblauncher.exe safe?
No antivirus engine detected the executable, and its observed WebView-based execution produced no malicious sandbox verdict, persistence indicator, or corroborating threat-intelligence match.
All 74 antivirus engines avoided flagging this executable, including 17 tier-1 engines, and one completed sandbox run produced no malicious verdict. The unsigned status and a defense-impairment technique warrant ordinary caution, but neither is corroborated by malware-family detections, hostile infrastructure, persistence, packing, or external research rules.
5d756c3d6ef2776b57…08ca7c60e7d181Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
All 74 antivirus engines avoided flagging this executable, including 17 tier-1 engines, and one completed sandbox run produced no malicious verdict. The unsigned status and a defense-impairment technique warrant ordinary caution, but neither is corroborated by malware-family detections, hostile infrastructure, persistence, packing, or external research rules.
The strongest evidence is broad antivirus agreement: 0 of 74 engines reported a detection, including no alerts from 17 reporting tier-1 engines. One completed runtime analysis showed Microsoft Edge WebView activity and did not produce a malicious sandbox verdict or persistence indicators. The observed host-reputation check covered the sole distinct contacted IP and found no cached malicious or suspicious result. The executable is also unpacked, has circulated through 1,083 sources, and has no MalwareBazaar, YARAify, or CIRCL match. Its unsigned status, T1562.001 mapping, and unresolved dropped child prevent absolute assurance, but these isolated concerns lack independent corroboration.
What We Detected
None of the 74 antivirus engines flagged the executable, including all 17 reporting tier-1 engines. It has appeared through 1,083 sources across 1,217 submissions, is not packed, and produced no matching MalwareBazaar entry, YARAify rule, or CIRCL record.
Threat Behavior
One completed sandbox run primarily launched Microsoft Edge WebView and created related browser-profile and crash-reporting data. It recorded T1562.001, but produced no malicious sandbox verdict and found no persistence indicators. The reputation check covered the sole distinct contacted IP, 162.159.36.2, without a malicious or suspicious cache match. One dropped child was inspected without a malicious result, although its final status remains unresolved.
What To Do Now
Confirm that the file came from the expected developer or distribution channel because it is unsigned. Keep endpoint protection enabled and rescan if the executable changes, requests elevated privileges unexpectedly, or begins making unexplained network connections.
Where this verdict could be wrong4 caveats
- signing.signed=false, so the executable has no publisher identity or certificate history to establish provenance.
- behaviour.offensiveTechniques includes T1562.001, a defense-impairment technique, although the completed sandbox did not issue a malicious verdict.
- droppedChildren.rollup records one unknown child, so the dropped component was not affirmatively established as benign.
- One communityComments entry alleges several threat categories, but it has zero votes and conflicts with the engine, sandbox, packing, and persistence evidence.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/74 antivirus engines reported a detection.
- All 17 reporting tier-1 engines were undetected.
- One completed sandbox run produced no malicious verdict or persistence indicators.
- The sole distinct contacted IP had no malicious or suspicious cache match.
- No packing, MalwareBazaar hit, CIRCL hit, or YARAify rule was found.
- The executable is unsigned and has no verified publisher history.
- Runtime telemetry mapped activity to MITRE T1562.001.
- One dropped child remains without a definitive verdict.
- A zero-vote community annotation alleges malware behavior without corroborating engine or sandbox evidence.
Use the file only if its source and intended WebView-launcher function are expected, since no verified publisher is available. Keep security protection enabled and obtain a fresh scan if its behavior or hash changes.
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
Partial1 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
CompleteRule evaluation completed with no recorded matches.
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
- 7MITRE ATT&CK techniques
- 4spawned processes
- 2network contacts
- 17filesystem & mutex artifacts
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.
- 164.77.179.74.in-addr.arpa
- 162.159.36.2
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\WMI\AutoLogger\Circular Kernel Context Logger\Status
- HKEY_CURRENT_USER\Software\Microsoft\EdgeWebView\BLBeacon\state
- HKEY_CURRENT_USER\Software\Microsoft\EdgeWebView\ThirdParty\StatusCodes
- C:\Users\user\AppData\Local\com.casualdev.weblauncher
- C:\Users\user\AppData\Local\com.casualdev.weblauncher\EBWebView
- C:\Users\user\AppData\Local\com.casualdev.weblauncher\EBWebView\BrowserMetrics
- C:\Users\user\AppData\Local\com.casualdev.weblauncher\EBWebView\BrowserMetrics\BrowserMetrics-69DF4F66-7D8.pma
- C:\Users\user\AppData\Local\com.casualdev.weblauncher\EBWebView\Crashpad
- com.casualdev.weblauncher-sim
- \Sessions\1\BaseNamedObjects\com.casualdev.weblauncher-sim
- \Sessions\1\BaseNamedObjects\DBWinMutex
- \Sessions\1\BaseNamedObjects\Local\ChromeProcessSingletonStartup!
- \Sessions\1\BaseNamedObjects\__OMADM_NAMED_MUTEX__
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 41c91a9c93d76295746a…1cc304Never 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.
- 0rule hits recorded
- 0 / 74engines flagged
- 1,083sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1,217 times from 1,083 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: weblauncher.exe — 5d756c3d6ef2776b574a69c5096b065531be128b78f579017e08ca7c60e7d181
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\weblauncher.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\weblauncher.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: com.casualdev.weblauncher — C:\Users\user\AppData\Local\com.casualdev.weblauncher
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: EBWebView — C:\Users\user\AppData\Local\com.casualdev.weblauncher\EBWebView
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 164.77.179.74.in-addr.arpa — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 74 engines flagged this file
View all 74 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
- weblauncher.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 13.3 MB
- Last analyzed
- Sep 29, 2026, 11:05 AM UTC
5d756c3d6ef2776b574a69c5096b065531be128b78f579017e08ca7c60e7d181Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is weblauncher.exe safe?
What is weblauncher.exe?
How many antivirus engines detected weblauncher.exe?
What is the SHA-256 hash of weblauncher.exe?
Is it safe to run weblauncher.exe?
How up to date is this analysis of weblauncher.exe?
Community
Member reviews and reports for this exact file hash.