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

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

4444.sys - Analysis Report

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

Verdict	Vulnerable (72/100)
YARA matches	2
Multi-engine detections	3 / 75
File size	855240 bytes
Code-signing signer	Microsoft Windows Hardware Compatibility Publisher
Analyzed	2026-09-03
SHA256	65dc75921d43bb73f06ed27fb8dc9b4f92234ccbbc8dd180c68f94e5be565bad
SHA1	15f808e447708994a006275008ac88b1fcf2ab93
MD5	15abf6dac1cccf53b556e656554c8084

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.

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	80 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	42 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	80 / 100
Packing and entropy	80 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (21)

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

API	Risk	Why it matters
MmMapLockedPagesSpecifyCache	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
IoGetDeviceObjectPointer	medium	Moderate risk - system modification capability
ZwQuerySystemInformation	medium	Moderate risk - system modification capability
MmUnmapIoSpace	medium	Moderate risk - system modification capability
ZwOpenKey	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
ZwReadFile	low	Standard kernel API - generally benign
ZwQueryInformationFile	low	Standard kernel API - generally benign
ExAllocatePool2	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
ZwQueryValueKey	low	Standard kernel API - generally benign
ZwCreateFile	low	Standard kernel API - generally benign

IOCTL dispatch codes (14)

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.

Code	Severity	Transfer	Description
0x0022358B	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #3426
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x008024AC	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2347
0x98765C35	medium	METHOD_IN_DIRECT	CUSTOM_PROCESS Function #1805
0x98763569	medium	METHOD_IN_DIRECT	CUSTOM_PROCESS Function #3418
0x8273BA48	medium	METHOD_BUFFERED	CUSTOM_VIRAGT Function #3730
0x00348D42	medium	METHOD_OUT_DIRECT	FILE_DEVICE_DISK Function #848
0x00345FC2	medium	METHOD_OUT_DIRECT	FILE_DEVICE_DISK Function #2032
0x00348D41	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #848
0x00220005	medium	METHOD_IN_DIRECT	FILE_DEVICE_UNKNOWN Function #1
0x0080CFF0	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #1020
0x9C4065F2	medium	METHOD_OUT_DIRECT	CUSTOM_LENOVO Function #2428
0x8273AC0D	medium	METHOD_IN_DIRECT	CUSTOM_VIRAGT Function #2819
0x9C403C75	medium	METHOD_IN_DIRECT	CUSTOM_LENOVO Function #3869

PE sections

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

Section	Virtual size	Raw size	Entropy	Flags
.text	0x9D466	0x9D600	6.97	CODE, EXEC, READ
.rdata	0x0FF0	0x1000	5.3	IDATA, READ
.data	0x2F59C	0x2EC00	7.99	IDATA, READ, WRITE
.pdata	0x0444	0x0600	4.2	IDATA, READ
INIT	0x05FD	0x0600	5.07	IDATA, READ, WRITE, DISCARD
.reloc	0x0130	0x0200	3.59	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	55 / 100

• No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
• ASLR Enabled - Address Space Layout Randomization is active - base address is randomized on each load.
• DEP/NX Enabled - Data Execution Prevention is active - non-executable pages cannot be executed.
• Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.
• Packed Section: .data - Section has entropy 7.99 (threshold: 7.0), indicating possible packing or encrypted content.

YARA rule matches (2)

Rule	Severity	Detects
BYOVD_MemRW	critical	Phys memory mapping + device creation
SUSP_PhysMem	high	Physical memory mapping

MITRE ATT&CK techniques (12)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003	OS Credential Dumping	Credential Access
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1006	Direct Volume Access	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1112	Modify Registry	Defense Evasion
T1211	Exploitation for Defense Evasion	Defense Evasion
T1543.003	Windows Service	Persistence
T1547.001	Registry Run Keys	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Microsoft Windows Hardware Compatibility Publisher
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Third Party Component CA 2014
Serial	330000006DAA072F958218C9E300000000006D
Valid from	2024-10-10 19:04 UTC
Valid until	2025-10-08 19:04 UTC (expired)
Signature validity	Not verified

• Certificate revision: 0x0200
• Certificate type: PKCS#7
• Chain: Microsoft Windows Third Party Component CA 2014

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 4444.sys

Is 4444.sys safe?

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

4444.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 65dc75921d43bb73f06ed27fb8dc9b4f92234ccbbc8dd180c68f94e5be565bad.

What is 4444.sys?

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