hidusb.sys - Clean (20/100) - DriverShield Analysis

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

hidusb.sys - Analysis Report

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

VerdictClean (20/100)
YARA matches0
File size44032 bytes
Analyzed2026-03-22
SHA25625c7fca105b711b284ada9a4581107fbb43123818b171d09aee286240ec41fd5
SHA10f76d7a2a2ada1e022541a2e24a58323d4689c36
MD5a45230fcaab58d9bb95f06e80bedfe81

Driver identity

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

File descriptionUSB Miniport Driver for Input Devices
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameHIDUSB.SYS
Internal nameHIDUSB.SYS
File version10.0.19041.3636 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 20/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 imports60 / 100
IOCTL dispatch surface48 / 100
Known-vulnerable corpus0 / 100
Code-signing state50 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (10)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExFreePoollowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign

IOCTL dispatch codes (16)

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
0x008083C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #241
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00808589mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #354
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0022430DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #195
0x0034630DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2243
0x00808311mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #196
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080002AmediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #10
0x0034744CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3347
0x0022341CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3335
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00808789mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #482
0x008087B6mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #493
0x003403B4mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #237

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x58510x5A005.99CODE, EXEC, READ
.rdata0x15D80x16004.9IDATA, READ
.data0x01A80x02000.62IDATA, READ, WRITE
.pdata0x06B40x08003.92IDATA, READ
.idata0x06FE0x08004.03IDATA, READ
PAGE0x16FF0x18005.99CODE, EXEC, READ
INIT0x00720x02001.68CODE, EXEC, READ, DISCARD
GFIDS0x00580x02000.83IDATA, READ, DISCARD
.rsrc0x04180x06002.52IDATA, READ, DISCARD
.reloc0x03980x04004.84IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (8)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1553.006Code Signing Policy ModificationDefense Evasion
T1652Device Driver DiscoveryDiscovery

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

Is hidusb.sys safe?

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

What is the risk score of hidusb.sys?

hidusb.sys has a DriverShield composite risk score of 20/100, placing it in the clean verdict band. SHA256: 25c7fca105b711b284ada9a4581107fbb43123818b171d09aee286240ec41fd5.

What is hidusb.sys?

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


DriverShield © 2025-2026 · Terms · Privacy · Contact