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

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

AsUpIO.sys - Analysis Report

DriverShield analyzed the Windows kernel driver AsUpIO.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	0
Multi-engine detections	1 / 75
File size	14464 bytes
Code-signing signer	VeriSign Time Stamping Services Signer - G2
Analyzed	2026-09-06
SHA256	b4d47ea790920a4531e3df5a4b4b0721b7fea6b49a35679f0652f1e590422602
SHA1	8b6aa5b2bff44766ef7afbe095966a71bc4183fa
MD5	1392b92179b07b672720763d9b1028a5

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

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

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

IOCTL dispatch codes (4)

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
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337
0x0080EC81	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #2848
0x0080C481	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #288
0x00808389	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #226

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	0x10FC	0x1200	5.93	CODE, EXEC, READ
.rdata	0x01A0	0x0200	3.85	IDATA, READ
.data	0x000C	0x0000	0	IDATA, READ, WRITE
.pdata	0x0090	0x0200	1.24	IDATA, READ
INIT	0x024A	0x0400	3.02	CODE, EXEC, READ, WRITE, 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.

MITRE ATT&CK techniques (8)

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
T1071	Application Layer Protocol	Command and Control
T1543.003	Windows Service	Persistence
T1562.001	Impair Defenses	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	VeriSign Time Stamping Services Signer - G2
Signer organisation	VeriSign, Inc.
Issuer	VeriSign Time Stamping Services CA
Serial	3825D7FAF861AF9EF490E726B5D65AD5
Valid from	2007-06-15 00:00 UTC
Valid until	2012-06-14 23:59 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: VeriSign Time Stamping Services CA
Chain: VeriSign Class 3 Code Signing 2009-2 CA
Chain: ASUSTeK Computer Inc.

Symbolic execution

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

Is AsUpIO.sys safe?

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

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

What is AsUpIO.sys?

AsUpIO.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by VeriSign Time Stamping Services Signer - G2.