Analysis of ProcLaunchMon.sys: suspicious verdict, risk score 58/100. 1 YARA match. SHA256 512c2144bc594670. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver ProcLaunchMon.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 |
| File size | 43448 bytes |
| Code-signing signer | Microsoft Windows |
| Analyzed | 2026-03-22 |
| SHA256 | 512c2144bc59467001b5ad79b3c402db2b57c7a359e5110a4ee37c92266f968c |
| SHA1 | 717178d7aeae47644b5c9ead2462b2d1fe999f6f |
| MD5 | 179b06e51e98a274f3ec5bcc492ea658 |
Version resource data embedded in the ProcLaunchMon.sys PE header, as extracted by the analysis engine.
| File description | Time Travel Debugging Process Launch Monitor driver |
|---|---|
| Product | Microsoft® Windows® Operating System |
| Company | Microsoft Corporation |
| Original filename | ProcLaunchMon.sys |
| Internal name | ProcLaunchMon.sys |
| File version | 10.0.19041.1 (WinBuild.160101.0800) |
| Copyright | © Microsoft Corporation. All rights reserved. |
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 | 99 / 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 ProcLaunchMon.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| PsSetCreateProcessNotifyRoutine | 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 |
| ObOpenObjectByPointer | medium | Moderate risk - system modification capability |
| KeBugCheckEx | medium | Moderate risk - system modification capability |
| ObReferenceObjectByHandle | medium | Moderate risk - system modification capability |
| ZwSetValueKey | medium | Moderate risk - system modification capability |
| ZwCreateKey | medium | Moderate risk - system modification capability |
| ZwClose | low | Standard kernel API - generally benign |
| ZwOpenKey | low | Standard kernel API - generally benign |
| KeSetEvent | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| KeInitializeEvent | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| IoDeleteSymbolicLink | 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 |
| ZwQueryValueKey | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
| IofCompleteRequest | 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 |
| 0x0080B58B | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #3426 |
| 0x00808D8B | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #866 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x0080AB89 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #2786 |
| 0x0080AF15 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #3013 |
| 0x008024B4 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2349 |
| 0x00802494 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2341 |
| 0x00340030 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #12 |
| 0x00223412 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_UNKNOWN Function #3332 |
| 0x00220022 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_UNKNOWN Function #8 |
| 0x0022B941 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #3664 |
| 0x0080248C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2339 |
| 0x0034BED8 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #4022 |
| 0x00228341 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #208 |
| 0x003403DC | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #247 |
| 0x00340090 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #36 |
| 0x00228024 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #9 |
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 | 0x2E69 | 0x3000 | 5.99 | CODE, EXEC, READ |
| .rdata | 0x1130 | 0x1200 | 4.37 | IDATA, READ |
| .data | 0x0368 | 0x0400 | 1.34 | IDATA, READ, WRITE |
| .pdata | 0x0354 | 0x0400 | 3.7 | IDATA, READ |
| .idata | 0x0A7A | 0x0C00 | 4.17 | IDATA, READ |
| PAGE | 0x1A39 | 0x1C00 | 6.04 | CODE, EXEC, READ |
| INIT | 0x00A6 | 0x0200 | 2.45 | CODE, EXEC, READ, DISCARD |
| GFIDS | 0x0040 | 0x0200 | 0.56 | IDATA, READ, DISCARD |
| .rsrc | 0x0450 | 0x0600 | 2.58 | IDATA, READ, DISCARD |
| .reloc | 0x041C | 0x0600 | 3.84 | IDATA, READ, DISCARD |
| Control Flow Guard | Enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 85 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| SUSP_Callbacks | medium | Kernel callback registration |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1014 | Rootkit | Defense Evasion |
| 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 |
| T1562.006 | Indicator Blocking | Defense Evasion |
| T1564.001 | Hidden Files and Directories | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
| Signer | Microsoft Windows |
|---|---|
| Signer organisation | Microsoft Corporation |
| Issuer | Microsoft Windows Production PCA 2011 |
| Serial | 330000023241FB59996DCC4DFF000000000232 |
| Valid from | 2019-05-02 21:24 UTC |
| Valid until | 2020-05-02 21:24 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: 1.
Based on DriverShield static and dynamic analysis, ProcLaunchMon.sys shows some suspicious signals and warrants manual review. Its composite risk score is 58/100 (verdict: suspicious). Always validate findings independently before acting.
ProcLaunchMon.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 512c2144bc59467001b5ad79b3c402db2b57c7a359e5110a4ee37c92266f968c.
ProcLaunchMon.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.
Related: Other drivers signed by Microsoft Windows · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas