Analysis of Reaper.sys: vulnerable verdict, risk score 72/100. 2 YARA matches, 31/75 multi-engine detections. SHA256 c725919e6357126d. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver Reaper.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 | 31 / 75 |
| File size | 40088 bytes |
| Code-signing signer | DigiCert High Assurance EV Root CA |
| Analyzed | 2026-09-06 |
| SHA256 | c725919e6357126d512c638f993cf572112f323da359645e4088f789eb4c7b8c |
| SHA1 | d8498707f295082f6a95fd9d32c9782951f5a082 |
| MD5 | bbbc9a6cc488cfb0f6c6934b193891eb |
Version resource data embedded in the Reaper.sys PE header, as extracted by the analysis engine.
| File description | KProcessHacker |
|---|---|
| Product | KProcessHacker |
| Company | wj32 |
| Original filename | kprocesshacker.sys |
| File version | 2.8 |
| Copyright | Licensed under the GNU GPL, v3. |
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 | 55 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 24 / 100 |
| Known-vulnerable corpus | 100 / 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 Reaper.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| ZwTerminateProcess | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| MmMapLockedPagesSpecifyCache | 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 |
| ObOpenObjectByPointer | medium | Moderate risk - system modification capability |
| ZwQuerySystemInformation | medium | Moderate risk - system modification capability |
| ObReferenceObjectByHandle | medium | Moderate risk - system modification capability |
| KeBugCheckEx | medium | Moderate risk - system modification capability |
| ZwQueryValueKey | low | Standard kernel API - generally benign |
| ProbeForRead | low | Standard kernel API - generally benign |
| KeInitializeEvent | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| ProbeForWrite | low | Standard kernel API - generally benign |
| KeSetEvent | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
| ZwOpenKey | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| ZwClose | 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 |
|---|---|---|---|
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x00802484 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2337 |
| 0x0080248C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2339 |
| 0x008024A4 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2345 |
| 0x0080E974 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2653 |
| 0x0034EB15 | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #2757 |
| 0x0080249C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2343 |
| 0x00340298 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #166 |
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 | 0x1470 | 0x1600 | 5.83 | CODE, EXEC, READ |
| .rdata | 0x0AD4 | 0x0C00 | 4.16 | IDATA, READ |
| .data | 0x0340 | 0x0200 | 0.64 | IDATA, READ, WRITE |
| .pdata | 0x027C | 0x0400 | 2.94 | IDATA, READ |
| PAGE | 0x3CB2 | 0x3E00 | 6.07 | CODE, EXEC, READ |
| INIT | 0x091A | 0x0A00 | 4.89 | CODE, EXEC, READ, WRITE, DISCARD |
| .rsrc | 0x02F8 | 0x0400 | 2.55 | IDATA, READ, DISCARD |
| Control Flow Guard | Not enabled |
|---|---|
| ASLR | Not enabled |
| DEP | Not enabled |
| Integrity check | Not enforced |
| Mitigation score | 5 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| PUA_VULN_Driver_Wj_Kprocesshacker_C725 | medium | Detects 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_ProcKill | critical | Process termination EDR killer |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1003.001 | OS Credential Dumping: LSASS Memory | Credential Access |
| T1055.001 | Process Injection: DLL Injection | Defense Evasion |
| T1055.012 | Process Hollowing | Defense Evasion |
| T1068 | Exploitation for Privilege Escalation | Privilege Escalation |
| T1071 | Application Layer Protocol | Command and Control |
| T1211 | Exploitation for Defense Evasion | Defense Evasion |
| T1489 | Service Stop | Impact |
| T1543.003 | Windows Service | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1562.001 | Disable/Modify Tools | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
| Signer | DigiCert High Assurance EV Root CA |
|---|---|
| Signer organisation | DigiCert Inc |
| Issuer | Microsoft Code Verification Root |
| Serial | 61204DB4000000000027 |
| Valid from | 2011-04-15 19:45 UTC |
| Valid until | 2021-04-15 19:55 UTC (expired) |
| Signature validity | Not verified |
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.
Based on DriverShield static and dynamic analysis, Reaper.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.
Reaper.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: c725919e6357126d512c638f993cf572112f323da359645e4088f789eb4c7b8c.
Reaper.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert High Assurance EV Root CA.
Related: Other drivers signed by DigiCert High Assurance EV Root CA · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas