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

Analysis of K7RKScan_2310.sys: vulnerable verdict, risk score 78/100. 3 YARA matches, 3/75 multi-engine detections. SHA256 5c6ce55a85f5d464. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

K7RKScan_2310.sys - Analysis Report

DriverShield analyzed the Windows kernel driver K7RKScan_2310.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 matches3
Multi-engine detections3 / 75
File size55824 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-06
SHA2565c6ce55a85f5d4640bd1485a72d0812bc4f5188ee966c5fe334248a7175d9040
SHA168360966329b74dfb1d4bb0ecc0b6fdbbed15a3e
MD5d690827cdb58631444dfd8607d99b9c1

Driver identity

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

File descriptionK7RKScan Kernel Module
ProductK7RKScan
CompanyK7 Computing Pvt. Ltd.
Original filenameK7RKScan
Internal nameK7RKScan.sys
File version23.0.0.10
CopyrightCopyright (C) 2003-2024 K7 Computing Pvt. Ltd.

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 surface42 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (22)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
IoDeleteDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign

IOCTL dispatch codes (14)

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
0x0022445FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #279
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0022BB05mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3777
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x00342715mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2501
0x00808389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #226
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00221B0DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1731
0x0080858DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #355
0x0034B8DDmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3639
0x0080898DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #611
0x00808D8DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #867
0x00340394mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #229
0x98768869mediumMETHOD_IN_DIRECTCUSTOM_PROCESS Function #538

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x31400x32006.15CODE, EXEC, READ
.rdata0x08F40x0A003.87IDATA, READ
.data0x00880x02000.14IDATA, READ, WRITE
.pdata0x02280x04002.46IDATA, READ
INIT0x05960x06004.72CODE, EXEC, READ, DISCARD
.rsrc0x03F80x04003.27IDATA, READ, DISCARD
.reloc0x00140x02000.27IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score90 / 100

YARA rule matches (3)

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

MITRE ATT&CK techniques (12)

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
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial330000006DAA072F958218C9E300000000006D
Valid from2024-10-10 19:04 UTC
Valid until2025-10-08 19:04 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 8 paths explored at a maximum depth of 8. Vulnerability classes reached: 0. 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 K7RKScan_2310.sys

Is K7RKScan_2310.sys safe?

Based on DriverShield static and dynamic analysis, K7RKScan_2310.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 K7RKScan_2310.sys?

K7RKScan_2310.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 5c6ce55a85f5d4640bd1485a72d0812bc4f5188ee966c5fe334248a7175d9040.

What is K7RKScan_2310.sys?

K7RKScan_2310.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 Hardware Compatibility Publisher.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · 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