applockerfltr.sys - Clean (19/100) - DriverShield Analysis

Analysis of applockerfltr.sys: clean verdict, risk score 19/100. 0 YARA matches. SHA256 ff748d1412aa3872. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

applockerfltr.sys - Analysis Report

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

VerdictClean (19/100)
YARA matches0
File size18432 bytes
Analyzed2026-03-22
SHA256ff748d1412aa387251ea636cef758d8a0f21173821c2e4d56ca50239f3ee4592
SHA170550e2c651070a873130d63b7086621e4971078
MD5c782d6ec9e9accd02e1daa847d8c66ba

Driver identity

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

File descriptionApplocker Filter
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameapplockerfltr.sys
Internal nameapplockerfltr.sys
File version10.0.19041.5072 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 19/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 imports72 / 100
IOCTL dispatch surface27 / 100
Known-vulnerable corpus0 / 100
Code-signing state50 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (8)

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

APIRiskWhy it matters
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwOpenKeylowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign

IOCTL dispatch codes (9)

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
0x00340032mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #12
0x0034341AmediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #3334
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00228341mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #208
0x0022A018mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2054
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x0022A014mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2053
0x003403A4mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #233

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x0A690x0C005.39CODE, EXEC, READ
.rdata0x0A900x0C004.1IDATA, READ
.data0x01200x02000.5IDATA, READ, WRITE
.pdata0x01800x02003.05IDATA, READ
.idata0x075E0x08004.13IDATA, READ
PAGE0x0F520x10005.68CODE, EXEC, READ
INIT0x04820x06004.97CODE, EXEC, READ, DISCARD
GFIDS0x00380x02000.51IDATA, READ, DISCARD
.rsrc0x04080x06002.48IDATA, READ, DISCARD
.reloc0x01BC0x02004.44IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1055.001Process Injection: DLL InjectionDefense Evasion
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1553.006Code Signing Policy ModificationDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1569.002System Services: Service ExecutionExecution
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 applockerfltr.sys

Is applockerfltr.sys safe?

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

What is the risk score of applockerfltr.sys?

applockerfltr.sys has a DriverShield composite risk score of 19/100, placing it in the clean verdict band. SHA256: ff748d1412aa387251ea636cef758d8a0f21173821c2e4d56ca50239f3ee4592.

What is applockerfltr.sys?

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


DriverShield © 2025-2026 · Terms · Privacy · Contact