MsIo64.sys - Suspicious (58/100) - DriverShield Analysis

Analysis of MsIo64.sys: suspicious verdict, risk score 58/100. 2 YARA matches, 1/74 multi-engine detections. SHA256 e6aa2306fa92c382. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

MsIo64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver MsIo64.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	2
Multi-engine detections	1 / 74
File size	34552 bytes
Code-signing signer	Microsoft Windows Hardware Compatibility Publisher
Analyzed	2026-10-05
SHA256	e6aa2306fa92c38274764377be9c1ae000d0a0d94af743577854cdc9ab9b4de8
SHA1	92072f172a6e880d864271f182ff56d252907cd8
MD5	09776b90495b955eda69cca8762ad3dd

Driver identity

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

File description	MICSYS IO driver
Product	MsIo64 Driver Version 1.3
Company	MICSYS Technology Co., LTd
Original filename	MsIo64.sys
Internal name	MsIo64.sys
File version	1.3 x64 built by: WinDDK
Copyright	Copyright (c) 2021 MICSYS

How the 58/100 score breaks down

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	10 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	48 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	40 / 100

Kernel imports (20)

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

API	Risk	Why it matters
ZwMapViewOfSection	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddress	high	Potentially dangerous - could be used for privilege escalation or security bypass
ZwSetValueKey	medium	Moderate risk - system modification capability
ObOpenObjectByPointer	medium	Moderate risk - system modification capability
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
KeBugCheckEx	medium	Moderate risk - system modification capability
ZwCreateKey	medium	Moderate risk - system modification capability
IoCreateDeviceSecure	low	Standard kernel API - generally benign
ZwOpenKey	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
ProbeForRead	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
DbgPrint	low	Standard kernel API - generally benign
ZwQueryValueKey	low	Standard 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.

Code	Severity	Transfer	Description
0x00223047	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #3089
0x008086FB	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #446
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0022B80A	medium	METHOD_OUT_DIRECT	FILE_DEVICE_UNKNOWN Function #3586
0x00808389	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #226
0x0080007E	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #31
0x00340030	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #12
0x0022C421	medium	METHOD_IN_DIRECT	FILE_DEVICE_UNKNOWN Function #264
0x00226408	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #2306
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337
0x0080248C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2339
0x008024B4	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2349
0x0034FE81	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #4000
0x0080249C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2343
0x0034032C	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #203
0x00340036	medium	METHOD_OUT_DIRECT	FILE_DEVICE_DISK Function #13

PE sections

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	0x1B8F	0x1C00	6.37	CODE, EXEC, READ
.rdata	0x0B9C	0x0C00	4.13	IDATA, READ
.data	0x036C	0x0400	1.3	IDATA, READ, WRITE
.pdata	0x027C	0x0400	2.84	IDATA, READ
PAGE	0x1B71	0x1C00	6.03	CODE, EXEC, READ
INIT	0x0698	0x0800	4.42	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x0390	0x0400	3.1	IDATA, READ, DISCARD
.reloc	0x007A	0x0200	0.61	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 100

• No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
• No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
• No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
• Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

YARA rule matches (2)

Rule	Severity	Detects
PUA_VULN_Driver_Micsystechnologycoltd_Msiosys_Msiodriverversion_X_0F03	medium	Detects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - MsIo64.sys. Investigate matches in context: expected filenames or standard v...
PUA_VULN_Driver_Micsystechnologycoltd_Msiosys_Msiodriverversion_X_AE42	medium	Detects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - MsIo64.sys

MITRE ATT&CK techniques (10)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1112	Modify Registry	Defense Evasion
T1211	Exploitation for Defense Evasion	Defense Evasion
T1543.003	Windows Service	Persistence
T1547.001	Registry Run Keys	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Microsoft Windows Hardware Compatibility Publisher
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Third Party Component CA 2014
Serial	3300000074FF3D4A9E7C401E86000000000074
Valid from	2025-07-16 20:48 UTC
Valid until	2026-07-14 20:48 UTC (expired)
Signature validity	Not verified

• Certificate revision: 0x0200
• Certificate type: PKCS#7
• Chain: Microsoft Windows Third Party Component CA 2014

Associated CVEs

• CVE-2020-17382 - MSI Ambient Link driver - physical memory access

Symbolic execution

Engine angr, status completed, 19 paths explored at a maximum depth of 19. Vulnerability classes reached: 0. Exploitable paths: 1.

Frequently asked questions about MsIo64.sys

Is MsIo64.sys safe?

Based on DriverShield static and dynamic analysis, MsIo64.sys shows some suspicious signals and warrants manual review. Its composite risk score is 58/100 (verdict: suspicious). Always validate findings independently before acting.

What is the risk score of MsIo64.sys?

MsIo64.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: e6aa2306fa92c38274764377be9c1ae000d0a0d94af743577854cdc9ab9b4de8.

What is MsIo64.sys?

MsIo64.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 · CVE-2020-17382 · 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