iMonitor64.sys - Vulnerable (78/100) - DriverShield Analysis

Analysis of iMonitor64.sys: vulnerable verdict, risk score 78/100. 3 YARA matches, 0/76 multi-engine detections. SHA256 07990dfdc314e0e2. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

iMonitor64.sys - Analysis Report

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

VerdictVulnerable (78/100)
YARA matches3
Multi-engine detections0 / 76
File size611416 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-24
SHA25607990dfdc314e0e2546529c2e3c9282b8b47427fe6c7a05fc3f383a7e7f072f3
SHA19a95c3b752ab5747f0e3ae68908d96131afa1ae6
MD529734daa03cb29a72e0e4ee35b7a3708

Driver identity

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

File descriptionInfinite Monitor Engine
ProductiMonitor
CompanyTRUSTSING
Original filenameiMonitor
Internal nameiMonitor
File version5.4.0.0
Copyrighthttps://trustsing.com

How the 78/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 matches100 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface100 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (45)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwSetSystemInformationhighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObRegisterCallbackshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
CmRegisterCallbackExmediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
NtQuerySystemInformationmediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
PsSetCreateThreadNotifyRoutinemediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
DbgPrintlowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 45 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.

CodeSeverityTransferDescription
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x0022BB07highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3777
0x0022BE07highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3969
0x00223D13highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3908
0x0022B8FFhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3647
0x008083C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #241
0x0080898BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #610
0x008045C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #369
0x00808D8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #866
0x00343833highMETHOD_NEITHERFILE_DEVICE_DISK Function #3596
0x00220117highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #69
0x00223417highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3333
0x0034341FhighMETHOD_NEITHERFILE_DEVICE_DISK Function #3335
0x00340117highMETHOD_NEITHERFILE_DEVICE_DISK Function #69
0x0034641BhighMETHOD_NEITHERFILE_DEVICE_DISK Function #2310
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00220008mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0xC3502C24mediumMETHOD_BUFFEREDCUSTOM_MSI Function #2825
0x00808A11mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #644
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x00804840mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #528

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.

SectionVirtual sizeRaw sizeEntropyFlags
.text0x671420x672006.42CODE, EXEC, READ
.rdata0x1DD000x1DE005.79IDATA, READ
.data0x39700x10004.06IDATA, READ, WRITE
.pdata0x5DF00x5E005.82IDATA, READ
PAGE0x19870x1A006.24CODE, EXEC, READ
INIT0x254A0x26005.19CODE, EXEC, READ, DISCARD
.rsrc0x03200x04002.61IDATA, READ, DISCARD
.reloc0x25E80x26005.43IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score60 / 100

YARA rule matches (3)

RuleSeverityDetects
BYOVD_ProcKillcriticalProcess termination EDR killer
SUSP_CallbacksmediumKernel callback registration
MAL_EDRKillercriticalGeneric EDR killer pattern

MITRE ATT&CK techniques (17)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense 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

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2012
Serial3300000124E76F6CA813A27C35000000000124
Valid from2025-02-20 20:08 UTC
Valid until2026-02-18 20:08 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status timeout, 71 paths explored at a maximum depth of 71. Vulnerability classes reached: 0. Exploitable paths: 0.

Frequently asked questions about iMonitor64.sys

Is iMonitor64.sys safe?

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

What is the risk score of iMonitor64.sys?

iMonitor64.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 07990dfdc314e0e2546529c2e3c9282b8b47427fe6c7a05fc3f383a7e7f072f3.

What is iMonitor64.sys?

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