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

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

AsIO2.sys - Analysis Report

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

VerdictSuspicious (58/100)
YARA matches0
Multi-engine detections1 / 75
File size33832 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA2565ae23f1fcf3fb735fcf1fa27f27e610d9945d668a149c7b7b0c84ffd6409d99a
SHA1aa2ea973bb248b18973e57339307cfb8d309f687
MD509672532194b4bff5e0f7a7d782c7bf2

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.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches0 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface15 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 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 AsIO2.sys, ranked by exploitation relevance.

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemoryhighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ZwQueryInformationFilelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign

IOCTL dispatch codes (5)

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
0x00808189mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #98
0x0022E381mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2272
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
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
.text0x24D20x26006.4CODE, EXEC, READ
.rdata0x08740x0A004.79IDATA, READ
.data0x00200x02000.28IDATA, READ, WRITE
.pdata0x018C0x02003.21IDATA, READ
INIT0x04360x06004.06CODE, EXEC, READ, DISCARD
.reloc0x00140x02000.26IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

MITRE ATT&CK techniques (10)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
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, 20 paths explored at a maximum depth of 20. 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 AsIO2.sys

Is AsIO2.sys safe?

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

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

What is AsIO2.sys?

AsIO2.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 · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact