_SYSDIR_drivers_kboot64.sys - Suspicious (58/100) - DriverShield Analysis

Analysis of _SYSDIR_drivers_kboot64.sys: suspicious verdict, risk score 58/100. 3 YARA matches, 0/76 multi-engine detections. SHA256 ac33906aa5496b2f. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

_SYSDIR_drivers_kboot64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver _SYSDIR_drivers_kboot64.sys and assigned a verdict of Suspicious with a composite risk score of 58/100, indicating some risk signals warranting review (30-59 band).

VerdictSuspicious (58/100)
YARA matches3
Multi-engine detections0 / 76
File size218776 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-08-05
SHA256ac33906aa5496b2ff142656c1f1d4180cc03d14b6f473043b483f92cdd728224
SHA169bf136cbb51d501f16ac273b975df65af7ddac3
MD584955dd385138c7d8f75b37745afeb53

Driver identity

Version resource data embedded in the _SYSDIR_drivers_kboot64.sys PE header, as extracted by the analysis engine.

File version2025.6.15.23946

How the 58/100 score breaks down

Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches85 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface100 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (37)

Kernel-mode APIs resolved from the Import Address Table of _SYSDIR_drivers_kboot64.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
CmRegisterCallbackmediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
ZwQueryValueKeylowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ProbeForWritelowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 37 resolved.

IOCTL dispatch codes (39)

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.

CodeSeverityTransferDescription
0x0034007BhighMETHOD_NEITHERFILE_DEVICE_DISK Function #30
0x00340063highMETHOD_NEITHERFILE_DEVICE_DISK Function #24
0x00340037highMETHOD_NEITHERFILE_DEVICE_DISK Function #13
0x00340033highMETHOD_NEITHERFILE_DEVICE_DISK Function #12
0x0022011BhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #70
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080FF81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4064
0x00803D48mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3922
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x0080BA30mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3724
0x0080BE41mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3984
0x0080BA60mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3736
0x002293E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1274
0x0080B841mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3600
0x0080E305mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2241
0x00809705mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1473
0x0022E820mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2568
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x00340039mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #14
0x0034002DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #11
0x00340034mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #13

Showing 24 of 39 extracted control codes.

PE sections

Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.

SectionVirtual sizeRaw sizeEntropyFlags
.text0x2D8A80x2DA006.13CODE, EXEC, READ
.rdata0x1AAC0x1C004.9IDATA, READ
.data0x171C0x12000.8IDATA, READ, WRITE
.pdata0x0E640x10005.03IDATA, READ
INIT0x0C8A0x0E004.97CODE, EXEC, READ, DISCARD
.rsrc0x01B80x02003.65IDATA, READ, DISCARD
.reloc0x00480x02000.87IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score55 / 100

YARA rule matches (3)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (18)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial330000006E1229856F0ADE6CFC00000000006E
Valid from2024-10-10 19:04 UTC
Valid until2025-10-08 19:04 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 34 paths explored at a maximum depth of 34. Vulnerability classes reached: 0. Exploitable paths: 0.

Frequently asked questions about _SYSDIR_drivers_kboot64.sys

Is _SYSDIR_drivers_kboot64.sys safe?

Based on DriverShield static and dynamic analysis, _SYSDIR_drivers_kboot64.sys shows some suspicious signals and warrants manual review. Its composite risk score is 58/100 (verdict: suspicious). Always validate findings independently before acting.

What is the risk score of _SYSDIR_drivers_kboot64.sys?

_SYSDIR_drivers_kboot64.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: ac33906aa5496b2ff142656c1f1d4180cc03d14b6f473043b483f92cdd728224.

What is _SYSDIR_drivers_kboot64.sys?

_SYSDIR_drivers_kboot64.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


DriverShield © 2025-2026 · Terms · Privacy · Contact