BS_HWMIo64.sys - Vulnerable (72/100) - DriverShield Analysis

Analysis of BS_HWMIo64.sys: vulnerable verdict, risk score 72/100. 2 YARA matches, 5/75 multi-engine detections. SHA256 60c6f4f34c7319cb. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

BS_HWMIo64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver BS_HWMIo64.sys and assigned a verdict of Vulnerable with a composite risk score of 72/100, indicating a known or likely vulnerability surface (60-79 band).

Verdict	Vulnerable (72/100)
YARA matches	2
Multi-engine detections	5 / 75
File size	18632 bytes
Code-signing signer	Symantec Time Stamping Services CA - G2
Analyzed	2026-09-06
SHA256	60c6f4f34c7319cb3f9ca682e59d92711a05a2688badbae4891b1303cd384813
SHA1	9c24dd75e4074041dbe03bf21f050c77d748b8e9
MD5	338a98e1c27bc76f09331fcd7ae413a5

How the 72/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	80 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	9 / 100
Known-vulnerable corpus	100 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (16)

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

API	Risk	Why it matters
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
HalSetBusDataByOffset	high	Potentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffset	high	Potentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
KeBugCheckEx	medium	Moderate risk - system modification capability
MmUnmapIoSpace	medium	Moderate risk - system modification capability
KeSetEvent	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign

IOCTL dispatch codes (3)

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
0x00226000	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #2048
0x0022B305	medium	METHOD_IN_DIRECT	FILE_DEVICE_UNKNOWN Function #3265

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	0x169A	0x1800	6.11	CODE, EXEC, READ
.rdata	0x0274	0x0400	3.1	IDATA, READ
.data	0x013C	0x0200	0.3	IDATA, READ, WRITE
.pdata	0x0108	0x0200	2.24	IDATA, READ
INIT	0x0560	0x0600	4.98	CODE, EXEC, READ, WRITE, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 100

No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

YARA rule matches (2)

Rule	Severity	Detects
BYOVD_MemRW	critical	Phys memory mapping + device creation
SUSP_PhysMem	high	Physical memory mapping

MITRE ATT&CK techniques (13)

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.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1542.001	Pre-OS Boot: System Firmware	Persistence
T1543.003	Windows Service	Persistence
T1562.001	Impair Defenses	Defense Evasion
T1569.002	Service Execution	Execution
T1601	Modify System Image	Defense Evasion
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Symantec Time Stamping Services CA - G2
Signer organisation	Symantec Corporation
Issuer	Thawte Timestamping CA
Serial	7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from	2012-12-21 00:00 UTC
Valid until	2020-12-30 23:59 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: Symantec Time Stamping Services Signer - G4
Chain: BIOSTAR MICROTECH INT'L CORP
Chain: VeriSign Class 3 Public Primary Certification Authority - G5
Chain: VeriSign Class 3 Code Signing 2010 CA

Symbolic execution

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

Corpus match: this hash is present in the known-vulnerable driver corpus DriverShield cross-references during analysis, which is why the score carries a full weighting on that component.

Frequently asked questions about BS_HWMIo64.sys

Is BS_HWMIo64.sys safe?

Based on DriverShield static and dynamic analysis, BS_HWMIo64.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 72/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of BS_HWMIo64.sys?

BS_HWMIo64.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 60c6f4f34c7319cb3f9ca682e59d92711a05a2688badbae4891b1303cd384813.

What is BS_HWMIo64.sys?

BS_HWMIo64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.