hardwares.sys - Malicious (88/100) - DriverShield Analysis

Analysis of hardwares.sys: malicious verdict, risk score 88/100. 4 YARA matches, 18/76 multi-engine detections. SHA256 d2ac6938ff3b2e06. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

hardwares.sys - Analysis Report

DriverShield analyzed the Windows kernel driver hardwares.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).

VerdictMalicious (88/100)
YARA matches4
Multi-engine detections18 / 76
File size106584 bytes
Code-signing signerVeriSign Class 3 Public Primary Certification Authority - G5
Analyzed2026-10-14
SHA256d2ac6938ff3b2e06e0d52916b448b3feb589be4e8ad58160ad6c4cdd33fe7cad
SHA124030a1fafe5be38ab4a4fe7b0929da629a9d4cf
MD5ca4351904cb316befae1d37fc5741564

Driver identity

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

File descriptionhardware
Producthardware
Companyhardware
Original filenamehardware
Internal namehardware
File version1.0.0.0
CopyrightCopyright (C) 2018

How the 88/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 matches100 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface66 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy80 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (24)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
CmRegisterCallbackmediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ZwDeleteFilemediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ExAllocatePoollowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign

IOCTL dispatch codes (22)

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
0x0080850FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #323
0x00340033highMETHOD_NEITHERFILE_DEVICE_DISK Function #12
0x00227417highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3333
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x002287E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #506
0x00345B0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1731
0x0034470DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #451
0x0022B9C0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3696
0x00225715mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1477
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13
0x0080007EmediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #31
0x00220020mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #8
0x0022011CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #71
0x00229286mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #1185
0x0034F7E9mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3578
0x0080D882mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #1568
0x00800400mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #256
0x00224CB1mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #812
0x003402A0mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #168

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x65D40x66006.33CODE, EXEC, READ
.rdata0x0BE40x0C003.81IDATA, READ
.data0x20180x02003.64IDATA, READ, WRITE
.pdata0x03E40x04004.13IDATA, READ
.gfids0x00040x02000.02IDATA, READ
INIT0x08D20x0A004.9CODE, EXEC, READ
.vmp00xFDD20xFE007.64CODE, IDATA, EXEC, READ
.reloc0x00BC0x02002.4IDATA, READ, DISCARD
.rsrc0x02F80x04002.46IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (4)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
BYOVD_ProcKillcriticalProcess termination EDR killer
SUSP_PhysMemhighPhysical memory mapping
MAL_EDRKillercriticalGeneric EDR killer pattern

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
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerVeriSign Class 3 Public Primary Certification Authority - G5
Signer organisationVeriSign, Inc.
IssuerMicrosoft Code Verification Root
Serial611993E400000000001C
Valid from2011-02-22 19:25 UTC
Valid until2021-02-22 19:35 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about hardwares.sys

Is hardwares.sys safe?

Based on DriverShield static and dynamic analysis, hardwares.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.

What is the risk score of hardwares.sys?

hardwares.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: d2ac6938ff3b2e06e0d52916b448b3feb589be4e8ad58160ad6c4cdd33fe7cad.

What is hardwares.sys?

hardwares.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by VeriSign Class 3 Public Primary Certification Authority - G5.

Related: Other drivers signed by VeriSign Class 3 Public Primary Certification Authority - G5 · 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