Analysis of tap0901.sys: clean verdict, risk score 11/100. 0 YARA matches. SHA256 89c5ca1440df1864. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver tap0901.sys and assigned a verdict of Clean with a composite risk score of 11/100, indicating no notable risk signals (0-29 band).
| Verdict | Clean (11/100) |
| YARA matches | 0 |
| File size | 27136 bytes |
| Analyzed | 2026-03-22 |
| SHA256 | 89c5ca1440df186497ce158eb71c0c6bf570a75b6bc1880eac7c87a0250201c0 |
| SHA1 | daebe266073616e5fc931c319470fcf42a06867a |
| MD5 | d765f43cbea72d14c04af3d2b9c8e54b |
Version resource data embedded in the tap0901.sys PE header, as extracted by the analysis engine.
| File description | TAP-Windows Virtual Network Driver (NDIS 6.0) |
|---|---|
| Product | TAP-Windows Virtual Network Driver (NDIS 6.0) |
| Company | The OpenVPN Project |
| Original filename | tap0901.sys |
| Internal name | tap0901.sys |
| File version | 9.21.2 9/21 built by: WinDDK |
| Copyright | OpenVPN Technologies, Inc. |
Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.
| Component | Sub-score |
|---|---|
| Multi-engine consensus | 0 / 100 |
| YARA signature matches | 0 / 100 |
| Dangerous kernel imports | 30 / 100 |
| IOCTL dispatch surface | 24 / 100 |
| Known-vulnerable corpus | 0 / 100 |
| Code-signing state | 50 / 100 |
| Packing and entropy | 0 / 100 |
| Dynamic behaviour | 0 / 100 |
| CVE cross-reference | 0 / 100 |
Kernel-mode APIs resolved from the Import Address Table of tap0901.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmMapLockedPagesSpecifyCache | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| KeBugCheckEx | medium | Moderate risk - system modification capability |
| IofCompleteRequest | low | Standard kernel API - generally benign |
Control codes reachable through the driver dispatch routine. Codes tied to published exploit code are flagged, since they are the primary Bring Your Own Vulnerable Driver (BYOVD) entry points.
| Code | Severity | Transfer | Description |
|---|---|---|---|
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x008024A4 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2345 |
| 0x00802484 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2337 |
| 0x00226F15 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #3013 |
| 0x0080007E | medium | METHOD_OUT_DIRECT | FILE_DEVICE_CUSTOM Function #31 |
| 0x00225416 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_UNKNOWN Function #1285 |
| 0x00220004 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #1 |
| 0x00340390 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #228 |
Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.
| Section | Virtual size | Raw size | Entropy | Flags |
|---|---|---|---|---|
| .text | 0x3A37 | 0x3C00 | 6.19 | CODE, EXEC, READ |
| .rdata | 0x073C | 0x0800 | 3.84 | IDATA, READ |
| .data | 0x0608 | 0x0200 | 1.51 | IDATA, READ, WRITE |
| .pdata | 0x0270 | 0x0400 | 2.77 | IDATA, READ |
| PAGE | 0x0C36 | 0x0E00 | 5.73 | CODE, EXEC, READ |
| INIT | 0x0800 | 0x0800 | 5.54 | CODE, EXEC, READ, WRITE, DISCARD |
| .rsrc | 0x03F0 | 0x0400 | 3.39 | IDATA, READ, DISCARD |
| .reloc | 0x0060 | 0x0200 | 0.35 | IDATA, READ, DISCARD |
| Control Flow Guard | Not enabled |
|---|---|
| ASLR | Not enabled |
| DEP | Not enabled |
| Integrity check | Not enforced |
| Mitigation score | 0 / 100 |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1003.001 | OS Credential Dumping: LSASS Memory | Credential Access |
| T1055.012 | Process Hollowing | Defense Evasion |
| T1068 | Exploitation for Privilege Escalation | Privilege Escalation |
| T1543.003 | Windows Service | Persistence |
| T1553.006 | Code Signing Policy Modification | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
Engine angr, status no_findings, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 0.
Based on DriverShield static and dynamic analysis, tap0901.sys is assessed as clean, with no notable risk signals. Its composite risk score is 11/100 (verdict: clean). Always validate findings independently before acting.
tap0901.sys has a DriverShield composite risk score of 11/100, placing it in the clean verdict band. SHA256: 89c5ca1440df186497ce158eb71c0c6bf570a75b6bc1880eac7c87a0250201c0.
tap0901.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators.
Related: What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas