fsdepends.sys - Clean (20/100) - DriverShield Analysis

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

fsdepends.sys - Analysis Report

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

VerdictClean (20/100)
YARA matches0
File size71152 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA2562d7676d3c7def0623929d563b3ee60cd6cea44e2c0b9fb4d63bd50c3c85b2912
SHA1675d3130f61e62e873328c5b2369e9be44a6d68e
MD5faf8481b2ebb27b48a4de6a4aa7599dc

Driver identity

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

File descriptionFile System Dependency Manager Mini Filter Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameFsDepends.sys
Internal nameFsDepends.sys
File version10.0.19041.3636 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 20/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 imports54 / 100
IOCTL dispatch surface45 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (15)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwQuerySystemInformationmediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
KeSetEventlowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
SeAccessChecklowStandard 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
0x0022011BhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #70
0x0080978BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1506
0x008086B7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #429
0x008080B7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #45
0x0022BF07highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #4033
0x0022B9FFhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3711
0x0080938BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1250
0x00808B8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #738
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00800028mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #10
0x0022B919mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3654
0x0022BE41mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3984
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00807000mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3072
0x003403D4mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #245

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x12690x14005.83CODE, EXEC, READ
.rdata0x0CC00x0E004.71IDATA, READ
.data0x02580x02000.59IDATA, READ, WRITE
.pdata0x04140x06003.25IDATA, READ
.idata0x0D880x0E004.41IDATA, READ
PAGE0x96860x98006.25CODE, EXEC, READ
.edata0x01C50x02004.53IDATA, READ
INIT0x05520x06005.44CODE, EXEC, READ, DISCARD
GFIDS0x00AC0x02001.35IDATA, READ, DISCARD
.rsrc0x06B00x08002.93IDATA, READ, DISCARD
.reloc0x08140x0A004.9IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (8)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000041331BC198807A90774000000000413
Valid from2023-02-03 00:05 UTC
Valid until2024-02-01 00:05 UTC (expired)
Signature validityNot verified

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 fsdepends.sys

Is fsdepends.sys safe?

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

What is the risk score of fsdepends.sys?

fsdepends.sys has a DriverShield composite risk score of 20/100, placing it in the clean verdict band. SHA256: 2d7676d3c7def0623929d563b3ee60cd6cea44e2c0b9fb4d63bd50c3c85b2912.

What is fsdepends.sys?

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


DriverShield © 2025-2026 · Terms · Privacy · Contact