NSecKrnl.sys - Vulnerable (78/100) - DriverShield Analysis

Analysis of NSecKrnl.sys: vulnerable verdict, risk score 78/100. 4 YARA matches, 28/75 multi-engine detections. SHA256 206f27ae820783b7. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

NSecKrnl.sys - Analysis Report

DriverShield analyzed the Windows kernel driver NSecKrnl.sys and assigned a verdict of Vulnerable with a composite risk score of 78/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (78/100)
YARA matches4
Multi-engine detections28 / 75
File size25056 bytes
Code-signing signerDigiCert High Assurance EV Root CA
Analyzed2026-09-06
SHA256206f27ae820783b7755bca89f83a0fe096dbb510018dd65b63fc80bd20c03261
SHA1b0b912a3fd1c05d72080848ec4c92880004021a1
MD580961850786d6531f075b8a6f9a756ad

Driver identity

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

File descriptionNSecKrnl
ProductNSEC
CompanyNSEC Co.,Ltd
Original filenameNSecKrnl
Internal nameNSecKrnl
File version3.7.40.5314
CopyrightCopyright (C) 2020 NSEC. All Rights Reserved.

How the 78/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 matches100 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface12 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (13)

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

APIRiskWhy it matters
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObRegisterCallbackshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign

IOCTL dispatch codes (4)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x00808389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #226
0x003402E4mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #185

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x072E0x08005.48CODE, EXEC, READ
.rdata0x048C0x06002.9IDATA, READ
.data0x40300x02000.28IDATA, READ, WRITE
.pdata0x00CC0x02001.64IDATA, READ
INIT0x03920x04004.96CODE, EXEC, READ, DISCARD
.rsrc0x03480x04002.84IDATA, READ, DISCARD
.reloc0x00140x02000.26IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Nseccoltd_Nseckrnl_Nsec_206FmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - NSecKrnl.sys. Investigate matches in context: expected filenames or standard...
BYOVD_ProcKillcriticalProcess termination EDR killer
SUSP_CallbacksmediumKernel callback registration
MAL_EDRKillercriticalGeneric EDR killer pattern

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1562.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert High Assurance EV Root CA
Signer organisationDigiCert Inc
IssuerMicrosoft Code Verification Root
Serial61204DB4000000000027
Valid from2011-04-15 19:45 UTC
Valid until2021-04-15 19:55 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Corpus match: this hash is present in the known-vulnerable driver corpus DriverShield cross-references during analysis, which is why the score carries a full weighting on that component.

Frequently asked questions about NSecKrnl.sys

Is NSecKrnl.sys safe?

Based on DriverShield static and dynamic analysis, NSecKrnl.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 78/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of NSecKrnl.sys?

NSecKrnl.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 206f27ae820783b7755bca89f83a0fe096dbb510018dd65b63fc80bd20c03261.

What is NSecKrnl.sys?

NSecKrnl.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 High Assurance EV Root CA.

Related: Other drivers signed by DigiCert High Assurance EV Root CA · 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