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

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

K7RKScan.sys - Analysis Report

DriverShield analyzed the Windows kernel driver K7RKScan.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 detections10 / 75
File size27936 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA256b16e217cdca19e00c1b68bdfb28ead53b20adeabd6edcd91542f9fbf48942877
SHA1468121e7d6952799f92940677268937c4c5f92ed
MD59b04a93e05ccff94667f04bffa7af600

Driver identity

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

File descriptionK7RKScan Kernel Module
ProductK7RKScan
CompanyK7 Computing Pvt. Ltd.
Original filenameK7RKScan
Internal nameK7RKScan.sys
File version15.1.0.6
CopyrightCopyright (C) 2003-2015 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 surface24 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (23)

Kernel-mode APIs resolved from the Import Address Table of K7RKScan.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
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
KeDelayExecutionThreadlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign

IOCTL dispatch codes (8)

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
0x0034E23DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2191
0x0022FB15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3781
0x0080BA41mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3728
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x0080878DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #483
0x0080BA48mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3730
0x00340394mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #229

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x2EF40x30006.13CODE, EXEC, READ
.rdata0x043C0x06003.53IDATA, READ
.data0x01BD0x02000.53IDATA, READ, WRITE
.pdata0x015C0x02002.89IDATA, READ
INIT0x053E0x06004.62CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03F80x04003.28IDATA, READ, DISCARD
.reloc0x003C0x02000.12IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Kcomputingpvtltd_Krkscansys_Krkscan_B16EmediumDetects 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

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 12 paths explored at a maximum depth of 12. 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.sys

Is K7RKScan.sys safe?

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

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

What is K7RKScan.sys?

K7RKScan.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.

Related: Other drivers signed by Symantec Time Stamping Services CA - G2 · 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