cpuz160_x64.sys - Suspicious (58/100) - DriverShield Analysis

Analysis of cpuz160_x64.sys: suspicious verdict, risk score 58/100. 2 YARA matches, 0/74 multi-engine detections. SHA256 62eb92eab59251ee. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

cpuz160_x64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver cpuz160_x64.sys and assigned a verdict of Suspicious with a composite risk score of 58/100, indicating some risk signals warranting review (30-59 band).

Verdict	Suspicious (58/100)
YARA matches	2
Multi-engine detections	0 / 74
File size	44696 bytes
Code-signing signer	Microsoft Windows Hardware Compatibility Publisher
Analyzed	2026-05-05
SHA256	62eb92eab59251ee0bd3ca0df643b4548127231895ab96e82b302ddc4fdaf5e2
SHA1	f4d99b5aa7e4ff4bc62d4909e626f88e2fb23bcd
MD5	4c24fa0c01f6753c8f181d1d0e248244

Driver identity

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

File description	CPUID Driver
Product	CPUID service
Company	CPUID
Original filename	cpuz.sys
Internal name	cpuz.sys
File version	6.1.7600.16385 built by: WinDDK
Copyright	Copyright(C) 2025 CPUID

How the 58/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	30 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (18)

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

API	Risk	Why it matters
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
HalSetBusDataByOffset	high	Potentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffset	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpace	medium	Moderate risk - system modification capability
IoGetDeviceObjectPointer	medium	Moderate risk - system modification capability
KeBugCheckEx	medium	Moderate risk - system modification capability
IofCompleteRequest	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
RtlInitAnsiString	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
SeSinglePrivilegeCheck	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
IoBuildDeviceIoControlRequest	low	Standard kernel API - generally benign

IOCTL dispatch codes (10)

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
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0080EC81	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #2848
0x0080249C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2343
0x9C402500	medium	METHOD_BUFFERED	CUSTOM_LENOVO Function #2368
0x00223042	medium	METHOD_OUT_DIRECT	FILE_DEVICE_UNKNOWN Function #3088
0x0080248C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2339
0x9C402740	medium	METHOD_BUFFERED	CUSTOM_LENOVO Function #2512
0x00223046	medium	METHOD_OUT_DIRECT	FILE_DEVICE_UNKNOWN Function #3089
0x0022DF2D	medium	METHOD_IN_DIRECT	FILE_DEVICE_UNKNOWN Function #1995
0x003402F0	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #188

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	0x6A56	0x6C00	6.19	CODE, EXEC, READ
.rdata	0x063C	0x0800	3.52	IDATA, READ
.data	0x0440	0x0200	0.43	IDATA, READ, WRITE
.pdata	0x015C	0x0200	2.84	IDATA, READ
INIT	0x0430	0x0600	3.98	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x0350	0x0400	2.92	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 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.
No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

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 (13)

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
T1014	Rootkit	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1211	Exploitation for Defense Evasion	Defense Evasion
T1542.001	Pre-OS Boot: System Firmware	Persistence
T1543.003	Windows Service	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1569.002	Service Execution	Execution
T1601	Modify System Image	Defense Evasion
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, 55 paths explored at a maximum depth of 55. Vulnerability classes reached: 1. Exploitable paths: 0.

Frequently asked questions about cpuz160_x64.sys

Is cpuz160_x64.sys safe?

Based on DriverShield static and dynamic analysis, cpuz160_x64.sys shows some suspicious signals and warrants manual review. Its composite risk score is 58/100 (verdict: suspicious). Always validate findings independently before acting.

What is the risk score of cpuz160_x64.sys?

cpuz160_x64.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 62eb92eab59251ee0bd3ca0df643b4548127231895ab96e82b302ddc4fdaf5e2.

What is cpuz160_x64.sys?

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