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

Analysis of ALSysIO64_4_.sys: suspicious verdict, risk score 58/100. 2 YARA matches, 0/76 multi-engine detections. SHA256 082b42d5b2c2b9c4. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

ALSysIO64_4_.sys - Analysis Report

DriverShield analyzed the Windows kernel driver ALSysIO64_4_.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 matches2
Multi-engine detections0 / 76
File size62616 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-25
SHA256082b42d5b2c2b9c4703c9fda09b1ad373b088908f4972a3cd404d69dbddd52c7
SHA17d8d587d0a8041b16c8c49d61036589decdec434
MD5a550c1009ab39bb5cece6a443ab27a8b

Driver identity

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

File descriptionALSysIO64
ProductALSysIO64
CompanyArthur Liberman
Original filenameALSysIO64.sys
Internal nameALSysIO64.sys
File version2.3.1.11
CopyrightCopyright (C) 2003-2024 Arthur Liberman

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 matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface54 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (21)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
KeWaitForSingleObjectlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard 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
0x00808E0FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #899
0x0080938BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1250
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x9C40B941mediumMETHOD_IN_DIRECTCUSTOM_LENOVO Function #3664
0x0080A70DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2499
0x00801B0DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1731
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x0080EF05mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3009
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x008086B8mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #430
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x00808339mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #206
0x00800F00mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #960
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00340032mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #12
0x0034033CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #207

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x9CE10x9E006.31CODE, EXEC, READ
.rdata0x115C0x12004.66IDATA, READ
.data0x06300x02000.38IDATA, READ, WRITE
.pdata0x075C0x08004.22IDATA, READ
PAGE0x01780x02004.7CODE, EXEC, READ
INIT0x04D00x06004.52CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03A00x04003.11IDATA, READ, DISCARD
.reloc0x000C0x02000.08IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (14)

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
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial330000006DAA072F958218C9E300000000006D
Valid from2024-10-10 19:04 UTC
Valid until2025-10-08 19:04 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about ALSysIO64_4_.sys

Is ALSysIO64_4_.sys safe?

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

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

What is ALSysIO64_4_.sys?

ALSysIO64_4_.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Microsoft Windows Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · 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