PnkBstrK.sys - Clean (16/100) - DriverShield Analysis

Analysis of PnkBstrK.sys: clean verdict, risk score 16/100. 0 YARA matches, 1/75 multi-engine detections. SHA256 f1e02f0f967becb8. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

PnkBstrK.sys - Analysis Report

DriverShield analyzed the Windows kernel driver PnkBstrK.sys and assigned a verdict of Clean with a composite risk score of 16/100, indicating no notable risk signals (0-29 band).

VerdictClean (16/100)
YARA matches0
Multi-engine detections1 / 75
File size22328 bytes
Code-signing signerVeriSign Time Stamping Services Signer - G2
Analyzed2026-03-22
SHA256f1e02f0f967becb82873910eb9e0d8a037c73eecdd55a381df68c05cf878dbb0
SHA11f853885bcdc6ac58bca13a1e843d5fe13497036
MD58bb94087cef0256f5ead973d7524bf58

How the 16/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 imports66 / 100
IOCTL dispatch surface0 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (8)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x34E20x36005.79CODE, EXEC, READ
.rdata0x01D40x02004.51IDATA, READ
.data0x0E000x02001.03IDATA, READ, WRITE
.reloc0x03480x04005.68IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (6)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerVeriSign Time Stamping Services Signer - G2
Signer organisationVeriSign, Inc.
IssuerVeriSign Time Stamping Services CA
Serial3825D7FAF861AF9EF490E726B5D65AD5
Valid from2007-06-15 00:00 UTC
Valid until2012-06-14 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about PnkBstrK.sys

Is PnkBstrK.sys safe?

Based on DriverShield static and dynamic analysis, PnkBstrK.sys is assessed as clean, with no notable risk signals. Its composite risk score is 16/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of PnkBstrK.sys?

PnkBstrK.sys has a DriverShield composite risk score of 16/100, placing it in the clean verdict band. SHA256: f1e02f0f967becb82873910eb9e0d8a037c73eecdd55a381df68c05cf878dbb0.

What is PnkBstrK.sys?

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

Related: Other drivers signed by VeriSign Time Stamping Services Signer - G2 · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact