filetrace.sys - Clean (12/100) - DriverShield Analysis

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

filetrace.sys - Analysis Report

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

VerdictClean (12/100)
YARA matches0
File size40448 bytes
Analyzed2026-03-22
SHA25642c56b93ff52cac5b74ce0a16d9d4425e8b3e690b3bd76a5a3c657655b62a34a
SHA1d92b4974b57bc5e4bbefed25c78dc29e1ca6a874
MD5c7f6f4b73e410087c6de5658aad70232

Driver identity

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

File descriptionFile Trace Filter Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamefiletrace.sys
Internal namefiletrace.sys
File version10.0.19041.1 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

How the 12/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 surface30 / 100
Known-vulnerable corpus0 / 100
Code-signing state50 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (7)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
IoGetDeviceObjectPointermediumModerate risk - system modification capability
DbgPrintExlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign

IOCTL dispatch codes (10)

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
0x0080850FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #323
0x0080341BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3334
0x003406C7highMETHOD_NEITHERFILE_DEVICE_DISK Function #433
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x00345715mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1477
0x00340315mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #197
0x0034002DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #11
0x00340035mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #13
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
.text0x2F270x30005.97CODE, EXEC, READ
.rdata0x0CE00x0E004.62IDATA, READ
.data0x0CC00x02001.62IDATA, READ, WRITE
.pdata0x024C0x04002.67IDATA, READ
.idata0x0BB20x0C004.46IDATA, READ
INITCONS0x06000x06001.74IDATA, READ
PAGE0x2AE80x2C005.96CODE, EXEC, READ
INIT0x06AC0x08005.25CODE, EXEC, READ, DISCARD
GFIDS0x00440x02000.63IDATA, READ, DISCARD
.rsrc0x05C00x06003.16IDATA, READ, DISCARD
.reloc0x06AC0x08005.11IDATA, 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 filetrace.sys

Is filetrace.sys safe?

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

What is the risk score of filetrace.sys?

filetrace.sys has a DriverShield composite risk score of 12/100, placing it in the clean verdict band. SHA256: 42c56b93ff52cac5b74ce0a16d9d4425e8b3e690b3bd76a5a3c657655b62a34a.

What is filetrace.sys?

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