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

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

acpi.sys - Analysis Report

DriverShield analyzed the Windows kernel driver acpi.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 / 74
File size873960 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-07-19
SHA25667d6b8d7b0fd4e356bcfa060e0862f9fca51ad541488c62891d55d97bbd9a5cc
SHA12de878614ae76c1e4b86b8fb87d80fb9f3d308a4
MD58cf3b7fb06b77ad8456e6a075fce25b0

Driver identity

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

File descriptionACPI Driver for NT
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameACPI.sys
Internal nameACPI.sys
File version10.0.26100.8521 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

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 surface100 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (32)

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

APIRiskWhy it matters
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetSystemInformationhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
KeWaitForSingleObjectlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ExAllocatePool2lowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
SeSinglePrivilegeChecklowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 32 resolved.

IOCTL dispatch codes (40)

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
0x002283FFhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #255
0x008005BFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #367
0x008004FBhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #318
0x008000FBhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #62
0x008003FBhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #254
0x008004BBhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #302
0x0080850FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #323
0x008004FFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #319
0x008004BFhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #303
0x0080584FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1555
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x0080818BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #98
0x0022E8CFhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #2611
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x0080880FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #515
0x0080830FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #195
0x008007C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #497
0x00343043highMETHOD_NEITHERFILE_DEVICE_DISK Function #3088
0x0034541FhighMETHOD_NEITHERFILE_DEVICE_DISK Function #1287
0x00223413highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3332
0x0022641FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #2311
0x00226427highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #2313
0x00225417highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #1285
0x00226423highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #2312

Showing 24 of 40 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x705A70x710006.32CODE, EXEC, READ
fothk0x10000x10000.03CODE, EXEC, READ
.rdata0x116F00x120005.65IDATA, READ
.data0x66880x40002.38IDATA, READ, WRITE
.pdata0x5FDC0x60005.98IDATA, READ
.idata0x32320x40004.14IDATA, READ
PAGE0x2BB150x2C0006.43CODE, EXEC, READ
.edata0x00770x10000.26IDATA, READ
PAGECONS0x0BE00x10002.86IDATA, READ
INIT0x589A0x60006.16CODE, EXEC, READ, DISCARD
GFIDS0x0C400x10003.8IDATA, READ, DISCARD
.rsrc0x44980x50003.62IDATA, READ, DISCARD
.reloc0x5A2C0x60005.9IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 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
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial3300000518418419ADCBAD294F000000000518
Valid from2025-06-19 18:11 UTC
Valid until2026-06-17 18:11 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about acpi.sys

Is acpi.sys safe?

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

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

What is acpi.sys?

acpi.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.

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