hidbatt.sys - Clean (18/100) - DriverShield Analysis

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

hidbatt.sys - Analysis Report

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

Verdict	Clean (18/100)
YARA matches	0
File size	39440 bytes
Code-signing signer	Microsoft Windows
Analyzed	2026-03-22
SHA256	d773640f980bf832d74fbb5e19fc1ffc06f9401c10698c0c26cfb7c067f3db73
SHA1	9bfd37d1caa43970f18f1f3fd06ba4758facc908
MD5	05fc1b768acb2d5caddca2f2e89f579c

Driver identity

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

File description	Hid Battery Driver
Product	Microsoft® Windows® Operating System
Company	Microsoft Corporation
Original filename	hidbatt.sys
Internal name	hidbatt.sys
File version	10.0.19041.1 (WinBuild.160101.0800)
Copyright	© Microsoft Corporation. All rights reserved.

How the 18/100 score breaks down

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	60 / 100
IOCTL dispatch surface	21 / 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 imports (11)

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

API	Risk	Why it matters
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
IoBuildDeviceIoControlRequest	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign
ZwOpenFile	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign

IOCTL dispatch codes (7)

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
0x00804F15	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #965
0x0034C3E8	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #250
0x0034DFE8	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #2042
0x0080249C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2343
0x002277E8	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #3578
0x00340384	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #225

PE sections

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	0x4DE9	0x4E00	6.21	CODE, EXEC, READ
.rdata	0x0678	0x0800	3.92	IDATA, READ
.data	0x0108	0x0200	1.18	IDATA, READ, WRITE
.pdata	0x02D0	0x0400	3.11	IDATA, READ
.idata	0x082C	0x0A00	3.89	IDATA, READ
INIT	0x00E2	0x0200	2.92	CODE, EXEC, READ, DISCARD
GFIDS	0x004C	0x0200	0.69	IDATA, READ, DISCARD
.rsrc	0x05A8	0x0600	3.1	IDATA, READ, DISCARD
.reloc	0x0368	0x0400	4.64	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	85 / 100

CFG Enabled - Control Flow Guard is active - indirect calls are validated against a bitmap of valid targets at runtime.
ASLR Enabled - Address Space Layout Randomization is active - base address is randomized on each load.
DEP/NX Enabled - Data Execution Prevention is active - non-executable pages cannot be executed.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

MITRE ATT&CK techniques (6)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1071	Application Layer Protocol	Command and Control
T1211	Exploitation for Defense Evasion	Defense Evasion
T1543.003	Windows Service	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1569.002	System Services: Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Microsoft Windows
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Production PCA 2011
Serial	330000023241FB59996DCC4DFF000000000232
Valid from	2019-05-02 21:24 UTC
Valid until	2020-05-02 21:24 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: Microsoft Windows Production PCA 2011

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 hidbatt.sys

Is hidbatt.sys safe?

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

What is the risk score of hidbatt.sys?

hidbatt.sys has a DriverShield composite risk score of 18/100, placing it in the clean verdict band. SHA256: d773640f980bf832d74fbb5e19fc1ffc06f9401c10698c0c26cfb7c067f3db73.

What is hidbatt.sys?

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