HW.sys - Vulnerable (78/100) - DriverShield Analysis

Analysis of HW.sys: vulnerable verdict, risk score 78/100. 3 YARA matches, 0/76 multi-engine detections. SHA256 0483b32f9544e9c3. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

HW.sys - Analysis Report

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

VerdictVulnerable (78/100)
YARA matches3
Multi-engine detections0 / 76
File size53336 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-04-02
SHA2560483b32f9544e9c3cc3f206e7bc983ea83f5a9ca44864f2af9b8fc10ff45949f
SHA101e74172e10d8b5f589e26ee8e3e4aec485edc6f
MD59347fbeeaf917fc4a1d64a0b4d61187a

Driver identity

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

File descriptionHW - Windows XP-11 (32/64 bit) kernel mode driver for PC ports/memory/PCI access
ProductHW
CompanyMarvin Test Solutions, Inc.
Original filenameHW.sys
Internal nameHw.sys
File version5.0.2.0
CopyrightCopyright © 1996-2023 Marvin Test Solutions, Inc. All Rights Reserved.

How the 78/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 surface51 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (25)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagescriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemoryhighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
IoCreateSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard 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
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x0080B883highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3616
0x0080928BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1186
0x0080888BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #546
0x0080860FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #387
0x00227883highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3616
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x9C40A440mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2320
0x9C406400mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2304
0x9C40A584mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2401
0x9C40A5C4mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2417
0x9C40A604mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2433
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x9876CCADmediumMETHOD_IN_DIRECTCUSTOM_PROCESS Function #811
0x00340032mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #12
0x003403A8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #234

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x79090x7A005.49CODE, EXEC, READ
.rdata0x1AC60x1C005.97IDATA, READ
.data0x01000x02004.98IDATA, READ, WRITE
.pdata0x04380x06003.18IDATA, READ
.rsrc0x04080x06002.48IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Marvintestsolutionsinc_Hwsys_Hw_0483mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - hw.sys
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (19)

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
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial3300000061C88B129C2A7F1D87000000000061
Valid from2023-04-06 19:16 UTC
Valid until2024-04-03 19:16 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 100 paths explored at a maximum depth of 100. 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 HW.sys

Is HW.sys safe?

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

What is the risk score of HW.sys?

HW.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 0483b32f9544e9c3cc3f206e7bc983ea83f5a9ca44864f2af9b8fc10ff45949f.

What is HW.sys?

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