MonProcessEX.sys - Vulnerable (60/100) - DriverShield Analysis

Analysis of MonProcessEX.sys: vulnerable verdict, risk score 60/100. 2 YARA matches, 1/75 multi-engine detections. SHA256 72d0b5615b996cbb. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

MonProcessEX.sys - Analysis Report

DriverShield analyzed the Windows kernel driver MonProcessEX.sys and assigned a verdict of Vulnerable with a composite risk score of 60/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (60/100)
YARA matches2
Multi-engine detections1 / 75
File size57576 bytes
Code-signing signerGlobalSign Code Signing Root R45
Analyzed2026-08-14
SHA25672d0b5615b996cbb01b1ca139e627079094f734da48a0435ffd8480a25d0a258
SHA1e674c507ca0c61854c61e316acdf711c790f5d24
MD5b32a250d1ef99bb62dd66cea60311f43

Driver identity

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

File descriptionMonProcess
ProductHonor
CompanyHonor Device Co., Ltd.
Original filenameMonProcess.sys
Internal nameMonProcess
File version1.0.0.1
CopyrightCopyright (C) Honor Device Co., Ltd. 2016-2020. All rights reserved.

How the 60/100 score breaks down

Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches10 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface48 / 100
Known-vulnerable corpus100 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (24)

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

APIRiskWhy it matters
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetValueKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePool2lowStandard kernel API - generally benign

IOCTL dispatch codes (16)

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.

CodeSeverityTransferDescription
0x0022BB07highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3777
0x00343D07highMETHOD_NEITHERFILE_DEVICE_DISK Function #3905
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00342444mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2321
0x00808B00mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #704
0x0080C730mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #460
0x00808B50mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #724
0x0034B30DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3267
0x00227B15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3781
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0022F30DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3267
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x0034032CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #203
0x008002A2mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #168

PE sections

Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.

SectionVirtual sizeRaw sizeEntropyFlags
.text0x34050x36005.8CODE, EXEC, READ
.rdata0x0E780x10003.93IDATA, READ
.data0x23400x04001.26IDATA, READ, WRITE
.pdata0x04380x06003.21IDATA, READ
PAGE0x25060x26006.13CODE, EXEC, READ
INIT0x08BA0x0A005.1CODE, EXEC, READ, DISCARD
.rsrc0x03900x04002.98IDATA, READ, DISCARD
.reloc0x003C0x02000.77IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score100 / 100

YARA rule matches (2)

RuleSeverityDetects
PUA_VULN_Driver_Honordevicecoltd_Monprocess_Honor_72D0mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - MonProcessEX.sys. Investigate matches in context: expected filenames or stan...
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (15)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerGlobalSign Code Signing Root R45
Signer organisationGlobalSign nv-sa
IssuerGlobalSign
Serial7803184245708A41CF6F01B8EEB4A954
Valid from2020-07-28 00:00 UTC
Valid until2029-03-18 00:00 UTC
Signature validityVerified

Symbolic execution

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.

Frequently asked questions about MonProcessEX.sys

Is MonProcessEX.sys safe?

Based on DriverShield static and dynamic analysis, MonProcessEX.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 60/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of MonProcessEX.sys?

MonProcessEX.sys has a DriverShield composite risk score of 60/100, placing it in the vulnerable verdict band. SHA256: 72d0b5615b996cbb01b1ca139e627079094f734da48a0435ffd8480a25d0a258.

What is MonProcessEX.sys?

MonProcessEX.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by GlobalSign Code Signing Root R45.

Related: Other drivers signed by GlobalSign Code Signing Root R45 · 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