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

Analysis of HW.sys: vulnerable verdict, risk score 78/100. 4 YARA matches, 17/76 multi-engine detections. SHA256 6a4875ae86131a59. 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 matches4
Multi-engine detections17 / 76
File size42976 bytes
Code-signing signerGlobalSign Timestamping CA - G2
Analyzed2026-09-06
SHA2566a4875ae86131a594019dec4abd46ac6ba47e57a88287b814d07d929858fe3e5
SHA14e56e0b1d12664c05615c69697a2f5c5d893058a
MD545c2d133d41d2732f3653ed615a745c8

Driver identity

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

File descriptionHW - Windows NT-8 (32/64 bit) kernel mode driver for PC ports/memory/PCI access
ProductHW
CompanyMarvin Test Solutions, Inc.
Original filenameHW.sys
Internal nameHw.sys
File version4.8.2.0
CopyrightCopyright © 1996-2015 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 matches90 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface36 / 100
Known-vulnerable corpus100 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (22)

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

APIRiskWhy it matters
MmMapLockedPagescriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemoryhighPotentially 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
MmUnmapIoSpacemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign

IOCTL dispatch codes (12)

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
0x00227883highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3616
0x0080888BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #546
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x9C406500mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2368
0x9C40A440mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2320
0x9C406544mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2385
0x9C40A584mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2401
0x9C40A5C0mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2416
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x003403A4mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #233
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x36940x38005.41CODE, EXEC, READ
INIT0x21510x22005.07CODE, EXEC, READ
.rdata0x0AEC0x0C004.27IDATA, READ
.pdata0x03180x04003.26IDATA, READ
.rsrc0x049C0x06004.16IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score20 / 100

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Marvintestsolutionsinc_Hwsys_Hw_6A48mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - hw.sys. Investigate matches in context: expected filenames or standard vendo...
PUA_VULN_Driver_Marvintestsolutionsinc_Hwsys_Hw_FD38mediumDetects 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 (17)

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

Code-signing chain

SignerGlobalSign Timestamping CA - G2
Signer organisationGlobalSign nv-sa
IssuerGlobalSign Root CA
Serial400000000012F4EE152D7
Valid from2011-04-13 10:00 UTC
Valid until2028-01-28 12:00 UTC
Signature validityVerified

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: 6a4875ae86131a594019dec4abd46ac6ba47e57a88287b814d07d929858fe3e5.

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 GlobalSign Timestamping CA - G2.

Related: Other drivers signed by GlobalSign Timestamping CA - G2 · 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