wimmount.sys - Clean (21/100) - DriverShield Analysis

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

wimmount.sys - Analysis Report

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

VerdictClean (21/100)
YARA matches0
File size40928 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA256f0d97fbf64bfd07867d82cc3d6e23ce317ce1c7ab2012beff9f4db18749393cd
SHA14891ef181c70416d622c0ac57963df18a537535d
MD54f573d0b8eb65dd544dd7aff27d56ae5

Driver identity

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

File descriptionWim file system Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamewimfltr.sys
Internal namewimfltr.sys
File version10.0.19041.3636 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

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

Kernel imports (14)

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

APIRiskWhy it matters
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
DbgPrintlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ProbeForReadlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ProbeForWritelowStandard kernel API - generally benign

IOCTL dispatch codes (11)

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
0x0022741FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3335
0x0022741BhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3334
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00225705mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1473
0x00804024mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #9
0x00226F05mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3009
0x00803845mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3601
0x00223422mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #3336
0x00340032mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #12
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00340398mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #230

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x1AE90x1C005.95CODE, EXEC, READ
.rdata0x0A080x0C003.95IDATA, READ
.data0x04600x02000.71IDATA, READ, WRITE
.pdata0x02880x04002.91IDATA, READ
.idata0x0CDC0x0E004.19IDATA, READ
PAGE0x260A0x28006.04CODE, EXEC, READ
INIT0x02A60x04004.43CODE, EXEC, READ, DISCARD
GFIDS0x003C0x02000.55IDATA, READ, DISCARD
.rsrc0x05C80x06003.21IDATA, READ, DISCARD
.reloc0x04180x06004.16IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (9)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1055.001Process Injection: DLL InjectionDefense Evasion
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1569.002System Services: Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial33000004158295A1A3D82E2857000000000415
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 wimmount.sys

Is wimmount.sys safe?

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

What is the risk score of wimmount.sys?

wimmount.sys has a DriverShield composite risk score of 21/100, placing it in the clean verdict band. SHA256: f0d97fbf64bfd07867d82cc3d6e23ce317ce1c7ab2012beff9f4db18749393cd.

What is wimmount.sys?

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