ndfltr.sys - Suspicious (35/100) - DriverShield Analysis

Analysis of ndfltr.sys: suspicious verdict, risk score 35/100. 0 YARA matches, 0/75 multi-engine detections. SHA256 b712379ca3ece73e. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

ndfltr.sys - Analysis Report

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

VerdictSuspicious (35/100)
YARA matches0
Multi-engine detections0 / 75
File size147248 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-10-11
SHA256b712379ca3ece73efe1a9dd1bb94bc7ca0c4e3d68fcca9a99888f67e11af00e8
SHA16b6be7f9764c7101279a187bb3d9f207c3128335
MD56f4dfc6d493e49fc0fec69a01cb3577e

Driver identity

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

File descriptionNetworkDirect Support Filter Driver
ProductOpenFabrics Windows
CompanyMellanox
Original filenamendfltr.sys
Internal namendfltr.sys
File version5.50.14695
CopyrightCopyright© 2009 Mellanox Technologies Ltd

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

Kernel imports (10)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeInitializeEventlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign

IOCTL dispatch codes (40)

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
0x0080A383highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2272
0x0080878BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #482
0x0080880FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #515
0x0080968BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #1442
0x0080868BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #418
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x0080A583highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2400
0x0080818BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #98
0x0080858BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #354
0x0080890FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #579
0x00808A8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #674
0x00227427highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3337
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0034BA00mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3712
0x0022BAC0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3760
0x0080E9C0mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2672
0x00809E89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1954
0x0080BB89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3810
0x0080868DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #419
0x00809F8DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2019
0x0080B841mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3600
0x0080A3E8mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2298
0x0080BE38mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3982

Showing 24 of 40 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x1C0880x1C2006.18CODE, EXEC, READ
.rdata0x23840x24005.25IDATA, READ
.data0x11280x04002.38IDATA, READ, WRITE
.pdata0x12C00x14004.9IDATA, READ
PAGE0x052C0x06005.49CODE, EXEC, READ
INIT0x09AC0x0A005.02CODE, EXEC, READ, DISCARD
.rsrc0x05B80x06003.27IDATA, READ, DISCARD
.reloc0x014C0x02003.9IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (14)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial3300000460CF42A912315F6FB3000000000460
Valid from2023-11-16 19:20 UTC
Valid until2024-11-14 19:20 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 58 paths explored at a maximum depth of 58. Vulnerability classes reached: 0. Exploitable paths: 4.

Frequently asked questions about ndfltr.sys

Is ndfltr.sys safe?

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

What is the risk score of ndfltr.sys?

ndfltr.sys has a DriverShield composite risk score of 35/100, placing it in the suspicious verdict band. SHA256: b712379ca3ece73efe1a9dd1bb94bc7ca0c4e3d68fcca9a99888f67e11af00e8.

What is ndfltr.sys?

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