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

Analysis of MsIo32.sys: suspicious verdict, risk score 58/100. 1 YARA match, 1/77 multi-engine detections. SHA256 2270a8144dabaf15. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

MsIo32.sys - Analysis Report

DriverShield analyzed the Windows kernel driver MsIo32.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
Multi-engine detections	1 / 77
File size	14720 bytes
Code-signing signer	Symantec Class 3 Extended Validation Code Signing CA - G2
Analyzed	2026-09-06
SHA256	2270a8144dabaf159c2888519b11b61e5e13acdaa997820c09798137bded3dd6
SHA1	fbc6d2448739ddec35bb5d6c94b46df4148f648d
MD5	564d84a799db39b381a582a0b2f738c4

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	5 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	0 / 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 imports (14)

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

API	Risk	Why it matters
ZwMapViewOfSection	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
WRITE_PORT_UCHAR	high	Potentially dangerous - could be used for privilege escalation or security bypass
WRITE_PORT_ULONG	high	Potentially dangerous - could be used for privilege escalation or security bypass
READ_PORT_UCHAR	high	Potentially dangerous - could be used for privilege escalation or security bypass
READ_PORT_ULONG	high	Potentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
DbgPrint	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign

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	0x09F0	0x0A00	6.26	CODE, EXEC, READ
.rdata	0x00C3	0x0200	2.01	IDATA, READ
.data	0x0008	0x0200	0.12	IDATA, READ, WRITE
INIT	0x032E	0x0400	4.67	CODE, EXEC, READ, WRITE, DISCARD
.reloc	0x00E8	0x0200	2.38	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 (1)

Rule	Severity	Detects
SUSP_PortIO	medium	Direct port I/O

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1014	Rootkit	Defense Evasion
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1542.001	Pre-OS Boot: System Firmware	Persistence
T1543.003	Windows Service	Persistence
T1562.001	Impair Defenses	Defense Evasion
T1569.002	Service Execution	Execution
T1601	Modify System Image	Defense Evasion
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Symantec Class 3 Extended Validation Code Signing CA - G2
Signer organisation	Symantec Corporation
Issuer	VeriSign Class 3 Public Primary Certification Authority - G5
Serial	191A32CB759C97B8CFAC118DD5127F49
Valid from	2014-03-04 00:00 UTC
Valid until	2024-03-03 23:59 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: MICSYS Technology Co., Ltd.
Chain: VeriSign Class 3 Public Primary Certification Authority - G5

Symbolic execution

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

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 MsIo32.sys

Is MsIo32.sys safe?

Based on DriverShield static and dynamic analysis, MsIo32.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 MsIo32.sys?

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

What is MsIo32.sys?

MsIo32.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Class 3 Extended Validation Code Signing CA - G2.