MyPortIO_x64.sys - Vulnerable (72/100) - DriverShield Analysis

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

MyPortIO_x64.sys - Analysis Report

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

VerdictVulnerable (72/100)
YARA matches3
Multi-engine detections1 / 75
File size29184 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA25618bf6cf0224a41058ba3944ff0df9e12fa256c7c353d6fa6132a464cd5db5709
SHA1f6bbd1917bcb4df7550bb42c50cd7ceef2ea1837
MD55a55272db2de6f37b30a0515b0c08383

Driver identity

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

File descriptionPort I/O Driver for Win32/64
ProductNuvoton Port I/O Driver
CompanyNuvoton Technology Corp.
Original filenameMyPortIO.sys
Internal nameMyPortIO.sys
File version3,0,2009,325
CopyrightCopyright (C) 2009 Nuvoton Technology Corp.

How the 72/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 matches85 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface69 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (12)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign

IOCTL dispatch codes (23)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00341F0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1987
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00342444mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2321
0x0080B941mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3664
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x9C4065C0mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2416
0x9C406640mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2448
0x9C40A5C4mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2417
0x9C40A644mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2449
0x9C406580mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2400
0x9C406600mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2432
0x9C406680mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2464
0x9C40A584mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2401
0x9C40A604mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2433
0x008086BAmediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #430
0x008086B9mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #430
0x0034B841mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3600
0x0022EB05mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2753
0x9C406408mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2306
0x9C40A444mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2321
0x00340408mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #258
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x3A360x3C005.63CODE, EXEC, READ
.rdata0x02A40x04002.36IDATA, READ
.data0x00160x02000.28IDATA, READ, WRITE
.pdata0x018C0x02003.11IDATA, READ
INIT0x029C0x04003.84CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x04680x06002.65IDATA, READ, DISCARD
.reloc0x00100x02000.14IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score55 / 100

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Nuvotontechnologycorp_Myportiosys_Nuvotonportiodriver_18BFmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - MyPortIO_x64.sys, MyPortIO_x86.sys, MyPortIO0. Investigate matches in contex...
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (13)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 100 paths explored at a maximum depth of 100. Vulnerability classes reached: 1. 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 MyPortIO_x64.sys

Is MyPortIO_x64.sys safe?

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

What is the risk score of MyPortIO_x64.sys?

MyPortIO_x64.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 18bf6cf0224a41058ba3944ff0df9e12fa256c7c353d6fa6132a464cd5db5709.

What is MyPortIO_x64.sys?

MyPortIO_x64.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 Time Stamping Services CA - G2.

Related: Other drivers signed by Symantec Time Stamping Services CA - G2 · 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