lagfilter.sys - Clean (24/100) - DriverShield Analysis

Analysis of lagfilter.sys: clean verdict, risk score 24/100. 0 YARA matches, 0/76 multi-engine detections. SHA256 c59ce8bbf8989c48. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

lagfilter.sys - Analysis Report

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

VerdictClean (24/100)
YARA matches0
Multi-engine detections0 / 76
File size105008 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-16
SHA256c59ce8bbf8989c48698e9e9f005ca243478b2e82335e801ed5060137f1018d3a
SHA13d733e650c45a99b67ebd3992647b57904be8fcc
MD5a1b6804fdc2a0922d5ba8dcaec83547e

Driver identity

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

File descriptionnet_filter 7.0
Productnet_filter_core
Companynet_filter
Original filenamenet_filter.sys
Internal namenet_filter.sys
File version1.0.0.3
CopyrightCopyright (C) 2026

How the 24/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 surface45 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (20)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwQuerySystemInformationmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign

IOCTL dispatch codes (15)

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
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00808111mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #68
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x008085C6mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #369
0x00808011mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00347715mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3525
0x00220B15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #709
0x00340069mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #26
0x00343415mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3333
0x003402D4mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #181
0x827335DDmediumMETHOD_IN_DIRECTCUSTOM_VIRAGT Function #3447
0x987638ECmediumMETHOD_BUFFEREDCUSTOM_PROCESS Function #3643

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0xFF4F0x100006.28CODE, EXEC, READ
.rdata0x16B00x18005IDATA, READ
.data0x1E180x0A002.1IDATA, READ, WRITE
.pdata0x09D80x0A004.86IDATA, READ
INIT0x09A00x0A005.01CODE, EXEC, READ, DISCARD
.rsrc0x03380x04002.66IDATA, READ, DISCARD
.reloc0x019C0x02004.63IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (14)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2012
Serial330000013C4A61FB3578D2B6DD00000000013C
Valid from2025-11-13 19:59 UTC
Valid until2026-11-10 19:59 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about lagfilter.sys

Is lagfilter.sys safe?

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

What is the risk score of lagfilter.sys?

lagfilter.sys has a DriverShield composite risk score of 24/100, placing it in the clean verdict band. SHA256: c59ce8bbf8989c48698e9e9f005ca243478b2e82335e801ed5060137f1018d3a.

What is lagfilter.sys?

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


DriverShield © 2025-2026 · Terms · Privacy · Contact