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

Analysis of active64.sys: suspicious verdict, risk score 58/100. 3 YARA matches, 1/76 multi-engine detections. SHA256 cb4e4d707da324b3. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

active64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver active64.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	3
Multi-engine detections	1 / 76
File size	12495016 bytes
Code-signing signer	Microsoft Windows Hardware Compatibility Publisher
Analyzed	2026-03-23
SHA256	cb4e4d707da324b3f57dc2b91197bc515f9ddc0762a4886821ae734c63c686dd
SHA1	61c35c4db9cfab79e2a81102fc615684ad95411a
MD5	79d4e5e97619412e6a4dbe0b7e4b15fd

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	85 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	100 / 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 (41)

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

API	Risk	Why it matters
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsLookupProcessByProcessId	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcess	high	Potentially dangerous - could be used for privilege escalation or security bypass
ObRegisterCallbacks	high	Potentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutine	high	Potentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
CmRegisterCallbackEx	medium	Moderate risk - system modification capability
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
ZwCreateKey	medium	Moderate risk - system modification capability
PsSetCreateThreadNotifyRoutine	medium	Moderate risk - system modification capability
PsSetLoadImageNotifyRoutine	medium	Moderate risk - system modification capability
KeBugCheckEx	medium	Moderate risk - system modification capability
ZwQuerySystemInformation	medium	Moderate risk - system modification capability
ZwSetValueKey	medium	Moderate risk - system modification capability
ObOpenObjectByPointer	medium	Moderate risk - system modification capability
MmUnmapIoSpace	medium	Moderate risk - system modification capability
ZwQueryInformationFile	low	Standard kernel API - generally benign
ExFreePool	low	Standard kernel API - generally benign
RtlInitAnsiString	low	Standard kernel API - generally benign
ZwOpenKey	low	Standard kernel API - generally benign
ZwOpenFile	low	Standard kernel API - generally benign
KeSetEvent	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
KeInitializeEvent	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
ZwReadFile	low	Standard kernel API - generally benign

Showing the 28 highest-relevance imports of 41 resolved.

IOCTL dispatch codes (40)

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
0x0080F123	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3144
0x0080BD8B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3938
0x0080BF83	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #4064
0x00347263	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #3224
0x00347473	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #3356
0x0080055B	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #342
0x9C4040EF	high	METHOD_NEITHER	CUSTOM_LENOVO Function #59
0x00800193	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #100
0x008001CB	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #114
0x008001A7	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #105
0x8273700B	high	METHOD_NEITHER	CUSTOM_VIRAGT Function #3074
0x0022D28F	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #1187
0x9C40E3F7	high	METHOD_NEITHER	CUSTOM_LENOVO Function #2301
0x00225AEB	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #1722
0x0080FCFF	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #3903
0x8273019B	high	METHOD_NEITHER	CUSTOM_VIRAGT Function #102
0x0022E6BB	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #2478
0x82730367	high	METHOD_NEITHER	CUSTOM_VIRAGT Function #217
0x00800FDB	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #1014
0xC350C44B	high	METHOD_NEITHER	CUSTOM_MSI Function #274
0x0022BE1F	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #3975
0xC350CE53	high	METHOD_NEITHER	CUSTOM_MSI Function #916
0x9C40FFD7	high	METHOD_NEITHER	CUSTOM_LENOVO Function #4085
0x8273492F	high	METHOD_NEITHER	CUSTOM_VIRAGT Function #587

Showing 24 of 40 extracted control codes.

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	0x32815	0x32A00	7.34	CODE, EXEC, READ
.rdata	0x958C	0x9600	5.22	IDATA, READ
.data	0x11BDFBC	0x14400	2.61	IDATA, READ, WRITE
.pdata	0x2280	0x2400	7.81	IDATA, READ
PAGE	0x1F67	0x2000	6.26	CODE, EXEC, READ
INIT	0x0FDC	0x1000	5.46	CODE, EXEC, READ
.cod0	0xB908D8	0xB90A00	7.59	CODE, EXEC, READ
.reloc	0x199C	0x1A00	5.5	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Enforced
Mitigation score	60 / 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.
• Force Integrity - IMAGE_DLLCHARACTERISTICS_FORCE_INTEGRITY is set - the OS validates the signature before loading.
• Packed Section: .text - Section has entropy 7.34 (threshold: 7.0), indicating possible packing or encrypted content.
• Packed Section: .pdata - Section has entropy 7.81 (threshold: 7.0), indicating possible packing or encrypted content.
• Packed Section: .cod0 - Section has entropy 7.59 (threshold: 7.0), indicating possible packing or encrypted content.

YARA rule matches (3)

Rule	Severity	Detects
BYOVD_MemRW	critical	Phys memory mapping + device creation
SUSP_PhysMem	high	Physical memory mapping
SUSP_Callbacks	medium	Kernel callback registration

MITRE ATT&CK techniques (18)

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.001	Process Injection: DLL Injection	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
T1489	Service Stop	Impact
T1543.003	Windows Service	Persistence
T1547.001	Registry Run Keys	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1562.001	Impair Defenses: Disable/Modify Tools	Defense Evasion
T1562.006	Indicator Blocking	Defense Evasion
T1564.001	Hidden Files and Directories	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 active64.sys

Is active64.sys safe?

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

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

What is active64.sys?

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