hvservice.sys - Clean (26/100) - DriverShield Analysis

Analysis of hvservice.sys: clean verdict, risk score 26/100. 0 YARA matches, 0/76 multi-engine detections. SHA256 f44b2395dfe6e097. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

hvservice.sys - Analysis Report

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

VerdictClean (26/100)
YARA matches0
Multi-engine detections0 / 76
File size99752 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-04-01
SHA256f44b2395dfe6e0972309bb4d5060b48ce0b0bdde9082f024869a1bb3bc4ef37a
SHA1db09c900099512b753e0dd03c8f01e481db4440a
MD505938a14d0e3a3be9b78dd1e499d36bf

Driver identity

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

File descriptionHypervisor Boot Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameHvService.sys
Internal nameHvService.sys
File version10.0.26100.7309 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 26/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 imports100 / 100
IOCTL dispatch surface60 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (21)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwSetValueKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
PsGetCurrentProcesslowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ExAllocatePool2lowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign

IOCTL dispatch codes (20)

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
0x0022341FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3335
0x0080858BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #354
0x00805AB3highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1708
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00808189mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #98
0x00800046mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #17
0x0022706DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3099
0x0080009DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #39
0x00220020mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #8
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x0022F981mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3680
0x00802500mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2368
0x0022800CmediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3
0x00228040mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #16
0x0080B900mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3648
0x00808389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #226
0x00223D00mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3904
0x003403A0mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #232
0x00228024mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #9

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x2CF70x30005.89CODE, EXEC, READ
fothk0x10000x10000.03CODE, EXEC, READ
.rdata0x1E480x20005.01IDATA, READ
.data0x05200x10000.26IDATA, READ, WRITE
.pdata0x07C80x10002.6IDATA, READ
.idata0x19060x20003.88IDATA, READ
INITCONS0x00340x10000.07IDATA, READ
PAGE0x5D7B0x60006.1CODE, EXEC, READ
INIT0x03660x10001.86CODE, EXEC, READ, DISCARD
GFIDS0x00900x10000.23IDATA, READ, DISCARD
.rsrc0x06280x10001.53IDATA, READ, DISCARD
.reloc0x07940x10003.1IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (14)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
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.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial3300000518418419ADCBAD294F000000000518
Valid from2025-06-19 18:11 UTC
Valid until2026-06-17 18:11 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about hvservice.sys

Is hvservice.sys safe?

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

What is the risk score of hvservice.sys?

hvservice.sys has a DriverShield composite risk score of 26/100, placing it in the clean verdict band. SHA256: f44b2395dfe6e0972309bb4d5060b48ce0b0bdde9082f024869a1bb3bc4ef37a.

What is hvservice.sys?

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

Related: Other drivers signed by Microsoft Windows · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact