npcap.sys - Clean (27/100) - DriverShield Analysis

Analysis of npcap.sys: clean verdict, risk score 27/100. 0 YARA matches, 0/76 multi-engine detections. SHA256 91e91ea4c9b48360. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

npcap.sys - Analysis Report

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

VerdictClean (27/100)
YARA matches0
Multi-engine detections0 / 76
File size81568 bytes
Code-signing signerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Analyzed2026-04-01
SHA25691e91ea4c9b48360282eb86ba7f4f0c7476b1666ccfc4a5f49eab91733cae850
SHA14443cc8c1307c5325c183a052c606bbab148f80d
MD517664b0cf0cbaf104aa8f26a8ad1dc26

Driver identity

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

File descriptionnpcap.sys (NT6 AMD64) Kernel Filter Driver
ProductNpcap
CompanyNmap Software LLC
Original filenamenpcap.sys
Internal nameNPCAP
File version1.83
CopyrightCopyright (c) 2025, Nmap Software LLC. All rights reserved.

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

Kernel imports (19)

Kernel-mode APIs resolved from the Import Address Table of npcap.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
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign

IOCTL dispatch codes (22)

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
0x0080868BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #418
0x0080B68BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3490
0x00340033highMETHOD_NEITHERFILE_DEVICE_DISK Function #12
0x00343D07highMETHOD_NEITHERFILE_DEVICE_DISK Function #3905
0x0080BA4BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3730
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080FB15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3781
0x00801715mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1477
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0022BFE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #4090
0x0034CF15mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #965
0x00342315mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2245
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0034002DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #11
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x0034002CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #11
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x00340358mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #214
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13
0x98768869mediumMETHOD_IN_DIRECTCUSTOM_PROCESS Function #538
0x00228024mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #9

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x83360x84006.34CODE, EXEC, READ
.rdata0x16EC0x18004.54IDATA, READ
.data0x02680x04001.32IDATA, READ, WRITE
.pdata0x05D00x06004.45IDATA, READ
PAGE0x1D0B0x1E006.13CODE, EXEC, READ
INIT0x1DE20x1E005.91CODE, EXEC, READ, DISCARD
.rsrc0x03B80x04003.18IDATA, READ, DISCARD
.reloc0x00400x02000.84IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (11)

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
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Signer organisationDigiCert, Inc.
IssuerDigiCert Trusted Root G4
Serial8AD40B260D29C4C9F5ECDA9BD93AED9
Valid from2021-04-29 00:00 UTC
Valid until2036-04-28 23:59 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about npcap.sys

Is npcap.sys safe?

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

What is the risk score of npcap.sys?

npcap.sys has a DriverShield composite risk score of 27/100, placing it in the clean verdict band. SHA256: 91e91ea4c9b48360282eb86ba7f4f0c7476b1666ccfc4a5f49eab91733cae850.

What is npcap.sys?

npcap.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1.

Related: Other drivers signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact