KslD.sys - Suspicious (58/100) - DriverShield Analysis

Analysis of KslD.sys: suspicious verdict, risk score 58/100. 1 YARA match, 0/76 multi-engine detections. SHA256 bd17231833aa369b. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

KslD.sys - Analysis Report

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

VerdictSuspicious (58/100)
YARA matches1
Multi-engine detections0 / 76
File size333216 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-04-03
SHA256bd17231833aa369b3b2b6963899bf05dbefd673db270aec15446f2fab4a17b5a
SHA1b6378e15a617b5eab802493bfc470fb9a3ecfd72
MD5fa5d2f0dfe198a70b07613342f76afb3

Driver identity

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

File descriptionKSLD
ProductMicrosoft Malware Protection
CompanyMicrosoft Corporation
Original filenameKSLD.sys
Internal nameKSLD
File version1.1.25081.3013 (d424131329b747790bb109abf13b5905156a2100)
Copyright© Microsoft Corporation. All rights reserved.

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

Kernel imports (31)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
NtQuerySystemInformationmediumModerate risk - system modification capability
ZwDeleteFilemediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
PsSetCreateThreadNotifyRoutinemediumModerate risk - system modification capability
KeWaitForSingleObjectlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 31 resolved.

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
0x008083C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #241
0x0080818BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #98
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x00347263highMETHOD_NEITHERFILE_DEVICE_DISK Function #3224
0x0022011FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #71
0x00220123highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #72
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080BB89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3810
0x0080938DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1251
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0034B941mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3664
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0034A845mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2577
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x008086B9mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #430
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x00809F89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2018
0x0080AF89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3042
0x00229FE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2042
0x00808D11mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #836

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
.text0x3CC900x3D0006.3CODE, EXEC, READ
awesome0x00090x04000.1CODE, EXEC, READ
.rdata0xA2040xA4005.09IDATA, READ
.data0x10F80x04000.55IDATA, READ, WRITE
.pdata0x2CA00x30005.14IDATA, READ
PAGE0x05560x08004.69CODE, EXEC, READ
INIT0x15680x18005.83CODE, EXEC, READ, DISCARD
.rsrc0x03D80x04003.33IDATA, READ, DISCARD
.reloc0x18280x1C006.1IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score100 / 100

YARA rule matches (1)

RuleSeverityDetects
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (19)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair Defenses: Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial3300000519DADDAA8BDC44B292000000000519
Valid from2025-06-19 18:11 UTC
Valid until2026-06-17 18:11 UTC
Signature validityVerified

Symbolic execution

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

Frequently asked questions about KslD.sys

Is KslD.sys safe?

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

What is the risk score of KslD.sys?

KslD.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: bd17231833aa369b3b2b6963899bf05dbefd673db270aec15446f2fab4a17b5a.

What is KslD.sys?

KslD.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 · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact