Analysis of _SYSDIR_drivers_kboot64_1_.sys: suspicious verdict, risk score 58/100. 3 YARA matches, 0/76 multi-engine detections. SHA256 b1f9f7759dc39f44. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver _SYSDIR_drivers_kboot64_1_.sys and assigned a verdict of Suspicious with a composite risk score of 58/100, indicating some risk signals warranting review (30-59 band).
| Verdict | Suspicious (58/100) |
| YARA matches | 3 |
| Multi-engine detections | 0 / 76 |
| File size | 191128 bytes |
| Code-signing signer | Microsoft Windows Hardware Compatibility Publisher |
| Analyzed | 2026-08-05 |
| SHA256 | b1f9f7759dc39f443002c04cba3e6296dc8ee5a9d4e0b8f684beb776ee0a4a92 |
| SHA1 | 163f5616d764ab44d28cf7f6e27e8a3af449eaeb |
| MD5 | 426f448d76cab0757bb15391147c8fc0 |
Version resource data embedded in the _SYSDIR_drivers_kboot64_1_.sys PE header, as extracted by the analysis engine.
| File version | 2024.7.15.20320 |
|---|
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 | 85 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 100 / 100 |
| Known-vulnerable corpus | 0 / 100 |
| Code-signing state | 80 / 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 _SYSDIR_drivers_kboot64_1_.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmMapIoSpace | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| ZwOpenProcess | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| MmGetSystemRoutineAddress | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| PsSetCreateProcessNotifyRoutine | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| PsLookupProcessByProcessId | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| ZwDeleteKey | medium | Moderate risk - system modification capability |
| MmUnmapIoSpace | medium | Moderate risk - system modification capability |
| ZwWriteFile | medium | Moderate risk - system modification capability |
| KeBugCheckEx | medium | Moderate risk - system modification capability |
| ZwCreateKey | medium | Moderate risk - system modification capability |
| PsSetLoadImageNotifyRoutine | medium | Moderate risk - system modification capability |
| ZwSetValueKey | medium | Moderate risk - system modification capability |
| ObReferenceObjectByHandle | medium | Moderate risk - system modification capability |
| ZwQuerySystemInformation | medium | Moderate risk - system modification capability |
| ZwSetInformationFile | medium | Moderate risk - system modification capability |
| CmRegisterCallback | medium | Moderate risk - system modification capability |
| IoGetDeviceObjectPointer | medium | Moderate risk - system modification capability |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| KeDelayExecutionThread | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| ZwOpenKey | low | Standard kernel API - generally benign |
| KeInitializeEvent | low | Standard kernel API - generally benign |
| ZwQueryValueKey | low | Standard kernel API - generally benign |
| ExAllocatePool | low | Standard kernel API - generally benign |
| DbgPrint | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| IoCreateSymbolicLink | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
Showing the 28 highest-relevance imports of 37 resolved.
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 |
|---|---|---|---|
| 0x0034007B | high | METHOD_NEITHER | FILE_DEVICE_DISK Function #30 |
| 0x00340063 | high | METHOD_NEITHER | FILE_DEVICE_DISK Function #24 |
| 0x00340037 | high | METHOD_NEITHER | FILE_DEVICE_DISK Function #13 |
| 0x00340033 | high | METHOD_NEITHER | FILE_DEVICE_DISK Function #12 |
| 0x0022011B | high | METHOD_NEITHER | FILE_DEVICE_UNKNOWN Function #70 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x0080249C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2343 |
| 0x0080EC81 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #2848 |
| 0x0080FF81 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #4064 |
| 0x00803D48 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #3922 |
| 0x00802494 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2341 |
| 0x0080BA30 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #3724 |
| 0x0080BE41 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #3984 |
| 0x0080BA60 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #3736 |
| 0x0080B841 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #3600 |
| 0x0080EBE8 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2810 |
| 0x0080BF05 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #4033 |
| 0x00807305 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #3265 |
| 0x0034C7E8 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #506 |
| 0x0022E820 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #2568 |
| 0x00340036 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_DISK Function #13 |
| 0x00340030 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #12 |
| 0x00340039 | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #14 |
| 0x0034002D | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #11 |
Showing 24 of 40 extracted control codes.
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 | 0x26C48 | 0x26E00 | 6.18 | CODE, EXEC, READ |
| .rdata | 0x1A2C | 0x1C00 | 4.8 | IDATA, READ |
| .data | 0x16EC | 0x1200 | 0.8 | IDATA, READ, WRITE |
| .pdata | 0x0E1C | 0x1000 | 4.84 | IDATA, READ |
| INIT | 0x0C6C | 0x0E00 | 4.98 | CODE, EXEC, READ, DISCARD |
| .rsrc | 0x01B8 | 0x0200 | 3.61 | IDATA, READ, DISCARD |
| .reloc | 0x0048 | 0x0200 | 0.86 | IDATA, READ, DISCARD |
| Control Flow Guard | Not enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 55 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| BYOVD_MemRW | critical | Phys memory mapping + device creation |
| SUSP_PhysMem | high | Physical memory mapping |
| SUSP_Callbacks | medium | Kernel callback registration |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1003 | OS Credential Dumping | Credential Access |
| T1003.001 | OS Credential Dumping: LSASS Memory | Credential Access |
| T1006 | Direct Volume Access | Defense Evasion |
| T1014 | Rootkit | Defense Evasion |
| T1055.001 | Process Injection: DLL Injection | Defense Evasion |
| T1055.012 | Process Hollowing | Defense Evasion |
| T1068 | Exploitation for Privilege Escalation | Privilege Escalation |
| T1112 | Modify Registry | Defense Evasion |
| T1211 | Exploitation for Defense Evasion | Defense Evasion |
| T1489 | Service Stop | Impact |
| T1543.003 | Windows Service | Persistence |
| T1547.001 | Registry Run Keys | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1562.001 | Impair Defenses: Disable/Modify Tools | Defense Evasion |
| T1562.006 | Indicator Blocking | Defense Evasion |
| T1564.001 | Hidden Files and Directories | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
| Signer | Microsoft Windows Hardware Compatibility Publisher |
|---|---|
| Signer organisation | Microsoft Corporation |
| Issuer | Microsoft Windows Third Party Component CA 2014 |
| Serial | 33000000699D42C97675B50882000000000069 |
| Valid from | 2024-01-11 20:09 UTC |
| Valid until | 2025-01-10 20:09 UTC (expired) |
| Signature validity | Not verified |
Engine angr, status completed, 34 paths explored at a maximum depth of 34. Vulnerability classes reached: 0. Exploitable paths: 0.
Based on DriverShield static and dynamic analysis, _SYSDIR_drivers_kboot64_1_.sys shows some suspicious signals and warrants manual review. Its composite risk score is 58/100 (verdict: suspicious). Always validate findings independently before acting.
_SYSDIR_drivers_kboot64_1_.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: b1f9f7759dc39f443002c04cba3e6296dc8ee5a9d4e0b8f684beb776ee0a4a92.
_SYSDIR_drivers_kboot64_1_.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Microsoft Windows Hardware Compatibility Publisher.
Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas