Analysis of procxp64.sys: suspicious verdict, risk score 58/100. 1 YARA match, 1/75 multi-engine detections. SHA256 de8c232652527045. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver procxp64.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 | 1 |
| Multi-engine detections | 1 / 75 |
| File size | 36408 bytes |
| Code-signing signer | Microsoft Windows Hardware Compatibility Publisher |
| Analyzed | 2026-09-06 |
| SHA256 | de8c232652527045b3c9e1ea719d4981bd919e5e4624720d2f8448c908d337e2 |
| SHA1 | e52b94df2af81d5df3fb1cfb141edba3cc41d8b8 |
| MD5 | d63e07b5e1e071c8d0788916744e27c2 |
Version resource data embedded in the procxp64.sys PE header, as extracted by the analysis engine.
| File description | Process Explorer |
|---|---|
| Product | Process Explorer |
| Company | Sysinternals - www.sysinternals.com |
| Original filename | procexp.Sys |
| Internal name | procexp.sys |
| File version | 16.27 |
| Copyright | Copyright (C) Mark Russinovich 1996-2019 |
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 | 5 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 72 / 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-mode APIs resolved from the Import Address Table of procxp64.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| ZwOpenProcess | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| 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 |
| ZwCreateKey | medium | Moderate risk - system modification capability |
| ObReferenceObjectByHandle | medium | Moderate risk - system modification capability |
| ObOpenObjectByPointer | medium | Moderate risk - system modification capability |
| ZwSetValueKey | medium | Moderate risk - system modification capability |
| KeBugCheckEx | medium | Moderate risk - system modification capability |
| ZwQuerySystemInformation | medium | Moderate risk - system modification capability |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| ZwClose | low | Standard kernel API - generally benign |
| ZwOpenKey | low | Standard kernel API - generally benign |
| ZwQueryValueKey | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| IoCreateSymbolicLink | low | Standard kernel API - generally benign |
| IoCreateDeviceSecure | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| IoDeleteSymbolicLink | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
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 |
|---|---|---|---|
| 0x00222000 | medium (known exploit) | METHOD_BUFFERED | Driver communication init |
| 0x00808689 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #418 |
| 0x00802484 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2337 |
| 0x0022B9C0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #3696 |
| 0x0022B800 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #3584 |
| 0x0080C481 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #288 |
| 0x0080007E | medium | METHOD_OUT_DIRECT | FILE_DEVICE_CUSTOM Function #31 |
| 0x00340030 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #12 |
| 0x00340320 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #200 |
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 | 0x25A0 | 0x2600 | 6.1 | CODE, EXEC, READ |
| .rdata | 0x0F68 | 0x1000 | 4.19 | IDATA, READ |
| .data | 0x022C | 0x0200 | 2.07 | IDATA, READ, WRITE |
| .pdata | 0x02F4 | 0x0400 | 3.31 | IDATA, READ |
| PAGE | 0x1A1B | 0x1C00 | 6.03 | CODE, EXEC, READ |
| INIT | 0x0818 | 0x0A00 | 4.52 | CODE, EXEC, READ, DISCARD |
| .rsrc | 0x0380 | 0x0400 | 2.99 | IDATA, READ, DISCARD |
| .reloc | 0x0030 | 0x0200 | 0.64 | IDATA, READ, DISCARD |
| Control Flow Guard | Not enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Enforced |
| Mitigation score | 60 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| PUA_VULN_Driver_Sysinternalswwwsysinternalscom_Procexpsys_Processexplorer_9B6A | medium | Detects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - procexp.Sys. Investigate matches in context: expected filenames or standard ... |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1055.001 | Process Injection: DLL Injection | Defense Evasion |
| T1068 | Exploitation for Privilege Escalation | Privilege Escalation |
| T1071 | Application Layer Protocol | Command and Control |
| 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 |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
| Signer | Microsoft Windows Hardware Compatibility Publisher |
|---|---|
| Signer organisation | Microsoft Corporation |
| Issuer | Microsoft Windows Third Party Component CA 2012 |
| Serial | 3300000082C88BA15B1C3EF710000000000082 |
| Valid from | 2019-05-02 20:49 UTC |
| Valid until | 2020-05-02 20:49 UTC (expired) |
| Signature validity | Not verified |
Engine angr, status completed, 10 paths explored at a maximum depth of 10. Vulnerability classes reached: 0. Exploitable paths: 0.
Based on DriverShield static and dynamic analysis, procxp64.sys shows some suspicious signals and warrants manual review. Its composite risk score is 58/100 (verdict: suspicious). Always validate findings independently before acting.
procxp64.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: de8c232652527045b3c9e1ea719d4981bd919e5e4624720d2f8448c908d337e2.
procxp64.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