kbdclass.sys - Clean (24/100) - DriverShield Analysis

Analysis of kbdclass.sys: clean verdict, risk score 24/100. 0 YARA matches. SHA256 7639dcd4328c14f3. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

kbdclass.sys - Analysis Report

DriverShield analyzed the Windows kernel driver kbdclass.sys and assigned a verdict of Clean with a composite risk score of 24/100, indicating no notable risk signals (0-29 band).

VerdictClean (24/100)
YARA matches0
File size71480 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA2567639dcd4328c14f3fb522ec501f4df374ccbe87699eb4a2b238c9f9c526fdf59
SHA14751624f4cbdf55c69d89af43f8354a4ca47bc61
MD502a6967d5aef2f15aa9c838dbf3e1c04

Driver identity

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

File descriptionKeyboard Class Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamekbdclass.sys
Internal namekbdclass.sys
File version10.0.19041.1 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 24/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 matches0 / 100
Dangerous kernel imports72 / 100
IOCTL dispatch surface51 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (16)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
IoCreateDevicelowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
SeSinglePrivilegeChecklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign

IOCTL dispatch codes (17)

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
0x0080002FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #11
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00221284mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1185
0x00223B85mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3809
0x00226885mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2593
0x00224985mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #609
0x00221585mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1377
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0022B7E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3578
0x00805F15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1989
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0034E30DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2243
0x0080007EmediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #31
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x0080808DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #35
0x00340390mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #228

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x644D0x66005.97CODE, EXEC, READ
.rdata0x1B380x1C004.86IDATA, READ
.data0x05A80x02000.78IDATA, READ, WRITE
.pdata0x08A00x0A004.15IDATA, READ
.idata0x0B8C0x0C004.47IDATA, READ
PAGE0x2CB70x2E006.06CODE, EXEC, READ
INIT0x0FED0x10005.98CODE, EXEC, READ, DISCARD
GFIDS0x00980x02001.31IDATA, READ, DISCARD
.rsrc0x0E180x10003.16IDATA, READ, DISCARD
.reloc0x07880x08005.39IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

MITRE ATT&CK techniques (6)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000023241FB59996DCC4DFF000000000232
Valid from2019-05-02 21:24 UTC
Valid until2020-05-02 21:24 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about kbdclass.sys

Is kbdclass.sys safe?

Based on DriverShield static and dynamic analysis, kbdclass.sys is assessed as clean, with no notable risk signals. Its composite risk score is 24/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of kbdclass.sys?

kbdclass.sys has a DriverShield composite risk score of 24/100, placing it in the clean verdict band. SHA256: 7639dcd4328c14f3fb522ec501f4df374ccbe87699eb4a2b238c9f9c526fdf59.

What is kbdclass.sys?

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

Related: Other drivers signed by Microsoft Windows · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact