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

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

kprocesshacker.sys - Analysis Report

DriverShield analyzed the Windows kernel driver kprocesshacker.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).

VerdictVulnerable (72/100)
YARA matches2
Multi-engine detections28 / 75
File size45208 bytes
Code-signing signerWen Jia Liu
Analyzed2026-09-06
SHA25670211a3f90376bbc61f49c22a63075d1d4ddd53f0aefa976216c46e6ba39a9f4
SHA1a21c84c6bf2e21d69fa06daaf19b4cc34b589347
MD51b5c3c458e31bede55145d0644e88d75

Driver identity

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

File descriptionKProcessHacker
ProductKProcessHacker
Companywj32
Original filenamekprocesshacker.sys
File version3.0
CopyrightLicensed under the GNU GPL, v3.

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.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches55 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface27 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (24)

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

APIRiskWhy it matters
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
ObOpenObjectByPointermediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
KeSetEventlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
ProbeForReadlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ProbeForWritelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign

IOCTL dispatch codes (9)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080FE81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4000
0x0022341AmediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #3334
0x00347B15mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3781
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0022B805mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3585
0x00340298mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #166

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x0FA00x10006.01CODE, EXEC, READ
.rdata0x09D40x0A004.33IDATA, READ
.data0x02D80x02001.94IDATA, READ, WRITE
.pdata0x02340x04002.64IDATA, READ
PAGE0x364E0x38006.05CODE, EXEC, READ
INIT0x0AA00x0C004.8CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x02F80x04002.52IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (2)

RuleSeverityDetects
PUA_VULN_Driver_Wj_Kprocesshacker_7021mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - kprocesshacker.sys. Investigate matches in context: expected filenames or st...
BYOVD_ProcKillcriticalProcess termination EDR killer

MITRE ATT&CK techniques (12)

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
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerWen Jia Liu
Signer organisationWen Jia Liu
IssuerDigiCert High Assurance Code Signing CA-1
SerialFF1EF66BD621C65B74B4DE41425717F
Valid from2013-10-30 00:00 UTC
Valid until2017-01-04 12:00 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. 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 kprocesshacker.sys

Is kprocesshacker.sys safe?

Based on DriverShield static and dynamic analysis, kprocesshacker.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 kprocesshacker.sys?

kprocesshacker.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 70211a3f90376bbc61f49c22a63075d1d4ddd53f0aefa976216c46e6ba39a9f4.

What is kprocesshacker.sys?

kprocesshacker.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Wen Jia Liu.

Related: Other drivers signed by Wen Jia Liu · 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