UcmUcsiAcpiClient.sys - Clean (22/100) - DriverShield Analysis

Analysis of UcmUcsiAcpiClient.sys: clean verdict, risk score 22/100. 1 YARA match. SHA256 3626760aee42ee36. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

UcmUcsiAcpiClient.sys - Analysis Report

DriverShield analyzed the Windows kernel driver UcmUcsiAcpiClient.sys and assigned a verdict of Clean with a composite risk score of 22/100, indicating no notable risk signals (0-29 band).

VerdictClean (22/100)
YARA matches1
File size36864 bytes
Analyzed2026-03-22
SHA2563626760aee42ee36e047da6899a81e0646dfba344a234270eae5d635f049be37
SHA139b846d777767ebf8403afd9e8f5079ceeb32e35
MD57fdc3a6fd8547468ce554c8821640103

Driver identity

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

File descriptionUCM-UCSI ACPI Client Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameUcmUcsiAcpiClient.sys
Internal nameUcmUcsiAcpiClient.sys
File version10.0.19041.1 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 22/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 matches30 / 100
Dangerous kernel imports60 / 100
IOCTL dispatch surface36 / 100
Known-vulnerable corpus0 / 100
Code-signing state50 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (5)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
DbgPrintExlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign

IOCTL dispatch codes (12)

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
0x0022BB07highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3777
0x0022011FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #71
0x0022741FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3335
0x98760D8BhighMETHOD_NEITHERCUSTOM_PROCESS Function #866
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00349705mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1473
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x0034B941mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3664
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x003403BCmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #239

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x23690x24005.96CODE, EXEC, READ
.rdata0x0F900x10005.45IDATA, READ
.data0x04D00x02001.21IDATA, READ, WRITE
.pdata0x042C0x06003.25IDATA, READ
.idata0x036C0x04003.6IDATA, READ
PAGE0x3AF10x3C006.13CODE, EXEC, READ
INIT0x021E0x04003.83CODE, EXEC, READ, DISCARD
GFIDS0x006C0x02000.92IDATA, READ, DISCARD
.rsrc0x04300x06002.53IDATA, READ, DISCARD
.reloc0x02600x04003.71IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (1)

RuleSeverityDetects
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (8)

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
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1553.006Code Signing Policy ModificationDefense Evasion
T1652Device Driver DiscoveryDiscovery

Symbolic execution

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

Frequently asked questions about UcmUcsiAcpiClient.sys

Is UcmUcsiAcpiClient.sys safe?

Based on DriverShield static and dynamic analysis, UcmUcsiAcpiClient.sys is assessed as clean, with no notable risk signals. Its composite risk score is 22/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of UcmUcsiAcpiClient.sys?

UcmUcsiAcpiClient.sys has a DriverShield composite risk score of 22/100, placing it in the clean verdict band. SHA256: 3626760aee42ee36e047da6899a81e0646dfba344a234270eae5d635f049be37.

What is UcmUcsiAcpiClient.sys?

UcmUcsiAcpiClient.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators.

Related: 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