storufs.sys - Clean (9/100) - DriverShield Analysis

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

storufs.sys - Analysis Report

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

VerdictClean (9/100)
YARA matches0
File size66528 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA256e1caaf59ba4cf4bd80a4f472e9944fc3254bae90d893e1cf9e3fb659e71f8d10
SHA1e125c1b30102886cc0475a539974f47eb25f2b04
MD5a245762cf5d2d3ce0cd69470ca769963

Driver identity

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

File descriptionMS UFS Storport Miniport Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamestorufs.sys
Internal namestorufs.sys
File version10.0.19041.4474 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

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

Kernel imports (6)

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

APIRiskWhy it matters
KeBugCheckExmediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
KeInitializeEventlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign

IOCTL dispatch codes (13)

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
0x008086C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #433
0x00223417highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3333
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00809189mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1122
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x0080FF81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4064
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0022E8CAmediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #2610
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080E281mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2208
0x003403A8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #234
0x0034002EmediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #11

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x9F290xA0006.33CODE, EXEC, READ
.rdata0x10E80x12005.19IDATA, READ
.data0x00A80x02000.28IDATA, READ, WRITE
.pdata0x05E80x06004.49IDATA, READ
.idata0x07B60x08004.44IDATA, READ
PAGE0x02F50x04005.06CODE, EXEC, READ
.edata0x006B0x02001.29IDATA, READ
INIT0x02920x04004.54CODE, EXEC, READ, DISCARD
GFIDS0x00780x02000.88IDATA, READ, DISCARD
.rsrc0x04100x06002.49IDATA, READ, DISCARD
.reloc0x04100x06003.86IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (3)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1071Application Layer ProtocolCommand and Control
T1543.003Windows ServicePersistence
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial3300000460CF42A912315F6FB3000000000460
Valid from2023-11-16 19:20 UTC
Valid until2024-11-14 19:20 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 storufs.sys

Is storufs.sys safe?

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

What is the risk score of storufs.sys?

storufs.sys has a DriverShield composite risk score of 9/100, placing it in the clean verdict band. SHA256: e1caaf59ba4cf4bd80a4f472e9944fc3254bae90d893e1cf9e3fb659e71f8d10.

What is storufs.sys?

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