File scan report
Verdict Malicious
Is Owlin. exe safe? No, we rate this exact file malicious.
46 of the 71 antivirus engines that checked it detect the file, including 11 major antivirus engines converging on the MalwareX family.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already ran it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't run it
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
46 of 71 flagged
- Flagged 46
- No detection 25
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
3 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The file is unsigned and has no prior clean history.
The engine consensus is decisive: 11 major 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 major antivirus 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 on Aug 1, 2026.
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 files it created were inspected and none flagged malicious.
What To Do Now
Do not execute the file. Keep security software 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
- No dropped file is known to be malicious and 10 children inspected with no malicious verdicts
- No community YARA rule matched 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 files it created
- No external YARA or CIRCL hits
- 11 malicious detections from major antivirus engines
- Unsigned executable
- Direct-IP network traffic without domain resolution
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 19sandbox rule tags
- 7spawned processes
- 1network contact
- 35filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, 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.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 6: FileSeen in the test run
Owlin.exe
0306f4ee5039bddae624578c917ab44123365a64edbf760177ae6d62712dcbae
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 6: ProcessSeen in the test run
Owlin.exe
"C:\Users\<USER>\Desktop\Owlin.exe"
Test run - Evidence 3 of 6: ProcessSeen in the test run
msedgewebview2.exe
"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
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 6: Written fileSeen in the test run
throttle_store.dat
C:\Users\<USER>\AppData\Local\Owlin\EBWebView\Crashpad\throttle_store.dat
Test run - Evidence 5 of 6: Written fileSeen in the test run
settings.dat
C:\Users\<USER>\AppData\Local\Owlin\EBWebView\Crashpad\settings.dat
Test run - +1 more recorded observation
- 1
Network
Hosts contacted
- Evidence 6 of 6: Contacted hostSeen in the test run
150.171.27.11
Contacted during the test run.
Test run
6 facts from the test run. See the full activity list.
Includes 19 mapped techniques, every process, file, registry and network entry and 6 dropped files.
Show the technical evidenceChapter 04
Technical details
46 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 46
- Avast (major engine)Win64:MalwareX-gen [Cryp]
- AVG (major engine)Win64:MalwareX-gen [Cryp]
- Avira (major engine)TR/W64.MalwareX
- BitDefender (major engine)Trojan.Generic.40357592
- Emsisoft (major engine)Trojan.Generic.40357592 (B)
- ESET-NOD32 (major engine)Generik.CCPTPE trojan
- F-Secure (major engine)Trojan.TR/W64.MalwareX
- Fortinet (major engine)W64/Kryptik_AGen.API!tr
File fingerprint
- Last analyzed
- Sep 3, 2026, 11:05 AM UTC
- SHA-256
0306f4ee5039bddae624578c917ab44123365a64edbf760177ae6d62712dcbae- SHA-1
dfb82a5ce91d3813e5fc27ff728b761158f1b355- MD5
66fabb9ee913950bdde2452eb55a2719
About this file
Owlin.exe is a Win32 EXE file of 11.6 MB.
- Type and size
- Win32 EXE · 11.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 1, 2026On VirusTotal.
- Submitted by
- 62 distinct sources
- Packer
- None detected
- Entropy
- 7.32 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
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.