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

Analysis of KKYUM.sys: suspicious verdict, risk score 58/100. 0 YARA matches, 16/75 multi-engine detections. SHA256 72bd55f4459c992b. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

KKYUM.sys - Analysis Report

DriverShield analyzed the Windows kernel driver KKYUM.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 matches0
Multi-engine detections16 / 75
File size26768 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-06
SHA25672bd55f4459c992b9caa1a33cb6862f1f3085ca35839c58dee8b75db22ca605f
SHA14d0708b4a6adee830c30b72add84172fb62fd049
MD58516410b49bb79c08c19a37c516dad72

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 matches0 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface21 / 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 KKYUM.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmCopyVirtualMemorycriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
ZwQuerySystemInformationmediumModerate risk - system modification capability
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign

IOCTL dispatch codes (7)

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
0x0034BF1DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #4039
0x0022B805mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3585
0x0022C715mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #453
0x0022D315mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1221
0x0022A305mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2241
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x25E00x26006.29CODE, EXEC, READ
.rdata0x0B800x0C004.58IDATA, READ
.data0x04E00x02000.82IDATA, READ, WRITE
.pdata0x01F80x02003.98IDATA, READ
INIT0x04F40x06004.33CODE, EXEC, READ, DISCARD
.reloc0x00380x02000.69IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (13)

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
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2012
Serial3300000124E76F6CA813A27C35000000000124
Valid from2025-02-20 20:08 UTC
Valid until2026-02-18 20:08 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Is KKYUM.sys safe?

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

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

What is KKYUM.sys?

KKYUM.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 · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact