bttflt.sys - Suspicious (30/100) - DriverShield Analysis

Analysis of bttflt.sys: suspicious verdict, risk score 30/100. 1 YARA match. SHA256 8de3b7c87d88cf37. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

bttflt.sys - Analysis Report

DriverShield analyzed the Windows kernel driver bttflt.sys and assigned a verdict of Suspicious with a composite risk score of 30/100, indicating some risk signals warranting review (30-59 band).

VerdictSuspicious (30/100)
YARA matches1
File size43832 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA2568de3b7c87d88cf375417355a7c5052b2de38805b563d61d0e483db4ad96bd741
SHA119187f28846ad507f06baf416ce4cc5a4cc70cd7
MD54ff20e869fe2b5a0b8ce2e8be61c7f7f

Driver identity

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

File descriptionVHD BTT Filter Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamebttflt.sys
Internal namebttflt.sys
File version10.0.19041.1 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 30/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 matches30 / 100
Dangerous kernel imports100 / 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 (11)

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

APIRiskWhy it matters
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
KeInitializeEventlowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard 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
0x0080878BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #482
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x002203E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #250
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x00808311mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #196
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00340388mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #226

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x38A90x3A006.13CODE, EXEC, READ
.rdata0x10D80x12005.15IDATA, READ
.data0x02600x02000.34IDATA, READ, WRITE
.pdata0x048C0x06003.43IDATA, READ
.idata0x06760x08003.96IDATA, READ
PAGE0x1BC60x1C006.22CODE, EXEC, READ
INIT0x02520x04003.91CODE, EXEC, READ, DISCARD
GFIDS0x00780x02001.08IDATA, READ, DISCARD
.rsrc0x03F80x04003.3IDATA, READ, DISCARD
.reloc0x03040x04004.27IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (1)

RuleSeverityDetects
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (9)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002System Services: Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000023241FB59996DCC4DFF000000000232
Valid from2019-05-02 21:24 UTC
Valid until2020-05-02 21:24 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 bttflt.sys

Is bttflt.sys safe?

Based on DriverShield static and dynamic analysis, bttflt.sys shows some suspicious signals and warrants manual review. Its composite risk score is 30/100 (verdict: suspicious). Always validate findings independently before acting.

What is the risk score of bttflt.sys?

bttflt.sys has a DriverShield composite risk score of 30/100, placing it in the suspicious verdict band. SHA256: 8de3b7c87d88cf375417355a7c5052b2de38805b563d61d0e483db4ad96bd741.

What is bttflt.sys?

bttflt.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 · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact