scfilter.sys - Clean (13/100) - DriverShield Analysis

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

scfilter.sys - Analysis Report

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

VerdictClean (13/100)
YARA matches0
File size44032 bytes
Analyzed2026-03-22
SHA2564f51b7d83689fb2625473cf6b4f7744deeec622ed2968cfa26af0be0bb8a3dc2
SHA1cf976f185fc010fb6df0fefb9affb14902fe151b
MD5e0d79317611a46d2db5101f902fe02b2

Driver identity

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

File descriptionMicrosoft Smart Card Reader Filter Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamescfilter.sys
Internal namescfilter
File version10.0.19041.4648 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

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

Kernel imports (4)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
RtlInitAnsiStringlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign

IOCTL dispatch codes (12)

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
0x0022BA15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3717
0x008087C6mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #497
0x0080DF15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1989
0x0080AB15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2757
0x0034002DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #11
0x00220118mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #70
0x0022011AmediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #70
0x00808529mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #330
0x003403BCmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #239
0x0034002EmediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #11
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x63AA0x64006.31CODE, EXEC, READ
.rdata0x0BF80x0C004.94IDATA, READ
.data0x13200x02000.86IDATA, READ, WRITE
.pdata0x039C0x04003.9IDATA, READ
.idata0x02FA0x04003.32IDATA, READ
PAGE0x1A490x1C006CODE, EXEC, READ
INIT0x026C0x04004.3CODE, EXEC, READ, DISCARD
GFIDS0x00600x02000.89IDATA, READ, DISCARD
.rsrc0x06500x08002.76IDATA, READ, DISCARD
.reloc0x02700x04003.87IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (5)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1553.006Code Signing Policy ModificationDefense Evasion
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 scfilter.sys

Is scfilter.sys safe?

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

What is the risk score of scfilter.sys?

scfilter.sys has a DriverShield composite risk score of 13/100, placing it in the clean verdict band. SHA256: 4f51b7d83689fb2625473cf6b4f7744deeec622ed2968cfa26af0be0bb8a3dc2.

What is scfilter.sys?

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