Is Owlin.exe safe?
11 tier-1 engines flag this unsigned 33-day-old EXE with process-injection and data-destruction techniques.
46 of 75 engines detect the file, including 11 tier-1 engines converging on the MalwareX family. Sandbox evidence shows process injection, defense evasion, and data-archiving activity. The file is unsigned and has no prior clean history.
0306f4ee5039bddae6…ae6d62712dcbaeRecommended 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.
46 of 75 engines detect the file, including 11 tier-1 engines converging on the MalwareX family. Sandbox evidence shows process injection, defense evasion, and data-archiving activity. The file is unsigned and has no prior clean history.
The engine consensus is decisive: 11 tier-1 detections and a named family outweigh the absence of external-intel hits. Offensive MITRE techniques observed in the single sandbox run reinforce the malicious classification. Lack of code signing removes any benign-publisher benefit. Medium prevalence and 33-day age indicate the sample is established enough for broad detection yet not commodity software. Incomplete host-reputation data is neutral and does not offset the other signals.
What We Detected
11 of 17 tier-1 engines and 46 engines overall flag Owlin.exe as malicious, converging on the MalwareX / SelfDel family. The file is a 11.5 MB unsigned 64-bit PE first seen 33 days ago.
Threat Behavior
Sandbox execution recorded MITRE techniques T1055 (process injection), T1485 (data destruction), T1560 (data archiving), and T1562.001 (defense evasion). Two direct IP addresses were contacted; host reputation was not cross-checked. Ten dropped children were inspected and none flagged malicious.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and submit the sample to your security vendor for additional correlation. If the file appeared unsolicited, treat the host as potentially compromised and investigate for persistence or lateral movement.
Where this verdict could be wrong2 caveats
- droppedChildren.hasMaliciousChild=false and 10 children inspected with no malicious verdicts
- externalIntel.yaraify.ruleCount=0 and no CIRCL/MalwareBazaar hits
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 malicious dropped children
- No external YARA or CIRCL hits
- 11 tier-1 malicious detections
- Unsigned executable
- Process-injection and defense-evasion techniques observed
- Direct-IP network traffic without domain resolution
Block the hash, remove the file, and scan the system for additional threats; maintain all security software in an active state.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete46 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 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
- 9spawned processes
- 2network contacts
- 35filesystem & 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: Used an input-capture technique that can record credentials or keystrokes.
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.
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
Owlin.exe
0306f4ee5039bddae624578c917ab44123365a64edbf760177ae6d62712dcbae
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Owlin.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=Owlin.exe --webview-exe-version=1.1.2 --user-data-dir="C:\Users\<USER>\AppData\Local\Owlin\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --edge-webview-custom-scheme --autoplay-policy=no-user-gesture-required --disable-features=msWebOOUI,msPdfOOUI,msSmartScreenProtection --enable-features=MojoIpcz --lang=en-US --accept-lang=en-US --mojo-named-platform-channel-pipe=3256.2880.13890287505067871829
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
throttle_store.dat
C:\Users\<USER>\AppData\Local\Owlin\EBWebView\Crashpad\throttle_store.dat
04Isolated runtime analysis - Written fileObserved
settings.dat
C:\Users\<USER>\AppData\Local\Owlin\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\Local\Owlin\EBWebView\Crashpad\throttle_store.dat
- C:\Users\<USER>\AppData\Local\Owlin\EBWebView\Crashpad\settings.dat
- C:\Users\<USER>\AppData\Local\Owlin\EBWebView\BrowserMetrics\BrowserMetrics-6A6EA88C-DD4.pma
- C:\Users\<USER>\AppData\Local\Owlin\EBWebView\lockfile
- C:\Users\<USER>\AppData\Local\Owlin\EBWebView\Variations
- C:\Users\<USER>\AppData\Local\Owlin\EBWebView\BrowserMetrics-spare.pma
- C:\Users\<USER>\AppData\Local\Owlin\EBWebView\337e571d-7750-450d-8b79-b9479fc6faba.tmp
- C:\Users\<USER>\AppData\Local\Owlin\EBWebView\Default\Code Cache\js\index-dir\the-real-index
- C:\Users\<USER>\AppData\Local\Owlin\EBWebView\Default\Code Cache\js\index-dir\temp-index
- C:\Users\<USER>\AppData\Local\Owlin\EBWebView\Default\Code Cache\wasm\index-dir\temp-index
- Owlin-sim
- Local\ChromeProcessSingletonStartup!
- __OMADM_NAMED_MUTEX__
- \Sessions\1\BaseNamedObjects\Owlin-sim
- \Sessions\1\BaseNamedObjects\DBWinMutex
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
- 7ce77f9623ae60788def…eebca3Never scannednever seen before
- d2d255c3dffe7619b8ca…65af1aNever scannednever seen before
- a0c9abae18599f0a65fc…e38e87Never scannednever seen before
- 5dfc321417fc31359f23…4a2026Never scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never scannednever seen before
- 75338d75c7ffe60a0894…bfc914Never scannednever seen before
- 4f53cda18c2baa0c0354…02b945Never scannednever seen before
- deba77bc71479c2e98a7…e1c573Never scannednever seen before
- 0628922305d2478ba75a…e28107Never 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.
- 2rule hits recorded
- 46 / 75engines flagged
- 62sources 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
46 of 75 antivirus engines flagged the file, including AhnLab-V3 and Alibaba.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 80 times from 62 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Owlin.exe — 0306f4ee5039bddae624578c917ab44123365a64edbf760177ae6d62712dcbae
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Owlin.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=Owlin.exe --webview-exe-version=1.1.2 --user-data-dir="C:\Users\<USER>\AppData\Local\Owlin\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --edge-webview-custom-scheme --autoplay-policy=no-user-gesture-required --disable-features=msWebOOUI,msPdfOOUI,msSmartScreenProtection --enable-features=MojoIpcz --lang=en-US --accept-lang=en-US --mojo-named-platform-channel-pipe=3256.2880.13890287505067871829
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: throttle_store.dat — C:\Users\<USER>\AppData\Local\Owlin\EBWebView\Crashpad\throttle_store.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: settings.dat — C:\Users\<USER>\AppData\Local\Owlin\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
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 LocalService -s W32TimeThe 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
46 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
- Owlin.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 11.0 MB
- Last analyzed
- Sep 3, 2026, 11:05 AM UTC
0306f4ee5039bddae624578c917ab44123365a64edbf760177ae6d62712dcbaeSafety & 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
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- 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 Owlin.exe a virus?
What is Owlin.exe?
How many antivirus engines detected Owlin.exe?
What should I do if I already ran Owlin.exe?
How do I remove Owlin.exe?
What kind of malware is Owlin.exe?
What is the SHA-256 hash of Owlin.exe?
How up to date is this analysis of Owlin.exe?
Community
Member reviews and reports for this exact file hash.