Analysis of fdc.sys: clean verdict, risk score 26/100. 1 YARA match. SHA256 26bc9c2f1d42ce5b. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver fdc.sys and assigned a verdict of Clean with a composite risk score of 26/100, indicating no notable risk signals (0-29 band).
| Verdict | Clean (26/100) |
| YARA matches | 1 |
| File size | 34816 bytes |
| Analyzed | 2026-03-22 |
| SHA256 | 26bc9c2f1d42ce5bef55e98dc0da557f09b747186580c796003cf84229f6d151 |
| SHA1 | 74b58a9f98377510874b0c6f40c4b8ed5e1e7c21 |
| MD5 | f567a0c101aecf4548e0bf61ee25d332 |
Version resource data embedded in the fdc.sys PE header, as extracted by the analysis engine.
| File description | Floppy Disk Controller Driver |
|---|---|
| Product | Microsoft® Windows® Operating System |
| Company | Microsoft Corporation |
| Original filename | fdc.sys |
| Internal name | fdc.sys |
| File version | 10.0.19041.1 (WinBuild.160101.0800) |
| Copyright | © Microsoft Corporation. All rights reserved. |
Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.
| Component | Sub-score |
|---|---|
| Multi-engine consensus | 0 / 100 |
| YARA signature matches | 30 / 100 |
| Dangerous kernel imports | 84 / 100 |
| IOCTL dispatch surface | 36 / 100 |
| Known-vulnerable corpus | 0 / 100 |
| Code-signing state | 50 / 100 |
| Packing and entropy | 0 / 100 |
| Dynamic behaviour | 0 / 100 |
| CVE cross-reference | 0 / 100 |
Kernel-mode APIs resolved from the Import Address Table of fdc.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmGetSystemRoutineAddress | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| ZwSetValueKey | medium | Moderate risk - system modification capability |
| ObReferenceObjectByHandle | medium | Moderate risk - system modification capability |
| KeDelayExecutionThread | low | Standard kernel API - generally benign |
| KeInitializeEvent | low | Standard kernel API - generally benign |
| KeSetEvent | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| ZwOpenKey | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| RtlInitAnsiString | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| ZwClose | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | low | Standard kernel API - generally benign |
| IoBuildDeviceIoControlRequest | low | Standard kernel API - generally benign |
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.
| Code | Severity | Transfer | Description |
|---|---|---|---|
| 0x00808F8B | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #994 |
| 0x0080898B | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #610 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x00806715 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #2501 |
| 0x0034BA00 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #3712 |
| 0x0080B841 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #3600 |
| 0x0080BA00 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #3712 |
| 0x0080248C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2339 |
| 0x00340025 | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #9 |
| 0x0080EC81 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #2848 |
| 0x0080AD89 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #2914 |
| 0x00340388 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #226 |
Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.
| Section | Virtual size | Raw size | Entropy | Flags |
|---|---|---|---|---|
| .text | 0x4DA9 | 0x4E00 | 6.16 | CODE, EXEC, READ |
| .rdata | 0x0A88 | 0x0C00 | 4.21 | IDATA, READ |
| .data | 0x0188 | 0x0200 | 1.76 | IDATA, READ, WRITE |
| .pdata | 0x0300 | 0x0400 | 3.38 | IDATA, READ |
| .idata | 0x0A92 | 0x0C00 | 4.17 | IDATA, READ |
| PAGE | 0x038F | 0x0400 | 5.81 | CODE, EXEC, READ |
| INIT | 0x0782 | 0x0800 | 5.64 | CODE, EXEC, READ, DISCARD |
| GFIDS | 0x0060 | 0x0200 | 0.88 | IDATA, READ, DISCARD |
| .rsrc | 0x03F8 | 0x0400 | 3.28 | IDATA, READ, DISCARD |
| .reloc | 0x044C | 0x0600 | 4.29 | IDATA, READ, DISCARD |
| Control Flow Guard | Enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 80 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| SUSP_PhysMem | high | Physical memory mapping |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1112 | Modify Registry | Defense Evasion |
| T1211 | Exploitation for Defense Evasion | Defense Evasion |
| T1543.003 | Windows Service | Persistence |
| T1547.001 | Registry Run Keys | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1553.006 | Code Signing Policy Modification | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
Engine angr, status no_findings, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 0.
Based on DriverShield static and dynamic analysis, fdc.sys is assessed as clean, with no notable risk signals. Its composite risk score is 26/100 (verdict: clean). Always validate findings independently before acting.
fdc.sys has a DriverShield composite risk score of 26/100, placing it in the clean verdict band. SHA256: 26bc9c2f1d42ce5bef55e98dc0da557f09b747186580c796003cf84229f6d151.
fdc.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 · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas