HpPortIox64.sys - Suspicious (35/100) - DriverShield Analysis

Analysis of HpPortIox64.sys: suspicious verdict, risk score 35/100. 1 YARA match, 1/75 multi-engine detections. SHA256 c5050a2017490fff. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

HpPortIox64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver HpPortIox64.sys and assigned a verdict of Suspicious with a composite risk score of 35/100, indicating some risk signals warranting review (30-59 band).

VerdictSuspicious (35/100)
YARA matches1
Multi-engine detections1 / 75
File size49176 bytes
Code-signing signerDigiCert SHA2 Assured ID Code Signing CA
Analyzed2026-09-06
SHA256c5050a2017490fff7aa53c73755982b339ddb0fd7cef2cde32c81bc9834331c5
SHA18c377ab4eebc5f4d8dd7bb3f90c0187dfdd3349f
MD5a641e3dccba765a10718c9cb0da7879e

Driver identity

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

File descriptionHpPortIo
ProductHpPortIo
CompanyHP Inc.
Original filenameHpPortIox64.sys
Internal nameHpPortIox64.sys
File version1.2.0.9
CopyrightCopyright (C) 2020-2021 HP Inc. All rights reserved.

How the 35/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 matches5 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface54 / 100
Known-vulnerable corpus100 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (19)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ExAllocatePoolWithTaglowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign

IOCTL dispatch codes (18)

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
0x00808389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #226
0x9C402000mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2048
0x9C4060C4mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2097
0x9C406144mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2129
0x9C40A0D8mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2102
0x9C40A0E0mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2104
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00342444mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2321
0x0034247CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2335
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0080C081mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #32
0x00340344mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #209
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
.text0x5D610x5E005.59CODE, EXEC, READ
.rdata0x0F840x10004.86IDATA, READ
.data0x01B80x02001.13IDATA, READ, WRITE
.pdata0x02700x04002.76IDATA, READ
INIT0x05340x06004.66CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03A80x04003.07IDATA, READ, DISCARD
.reloc0x000C0x02000.08IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score20 / 100

YARA rule matches (1)

RuleSeverityDetects
PUA_VULN_Driver_Hpinc_Hpportioxsys_Hpportio_C505mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - HpPortIox64.sys. Investigate matches in context: expected filenames or stand...

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1014RootkitDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert SHA2 Assured ID Code Signing CA
Signer organisationDigiCert Inc
IssuerDigiCert Assured ID Root CA
Serial409181B5FD5BB66755343B56F955008
Valid from2013-10-22 12:00 UTC
Valid until2028-10-22 12:00 UTC
Signature validityVerified

Symbolic execution

Engine angr, status completed, 19 paths explored at a maximum depth of 19. 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 HpPortIox64.sys

Is HpPortIox64.sys safe?

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

What is the risk score of HpPortIox64.sys?

HpPortIox64.sys has a DriverShield composite risk score of 35/100, placing it in the suspicious verdict band. SHA256: c5050a2017490fff7aa53c73755982b339ddb0fd7cef2cde32c81bc9834331c5.

What is HpPortIox64.sys?

HpPortIox64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert SHA2 Assured ID Code Signing CA.

Related: Other drivers signed by DigiCert SHA2 Assured ID Code Signing CA · 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