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

Analysis of pskmad.sys: vulnerable verdict, risk score 78/100. 2 YARA matches, 0/75 multi-engine detections. SHA256 9bf3b737afa4d4f5. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

pskmad.sys - Analysis Report

DriverShield analyzed the Windows kernel driver pskmad.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 matches2
Multi-engine detections0 / 75
File size63360 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-10-18
SHA2569bf3b737afa4d4f5e7b00ec749d4b75656ad66d9a2b402e1e81934e95ba7df5b
SHA17be590049b5396056f2384a3b56bf2db11b286e1
MD543fe428d3e109c81bb1737afd0f9bfa6

Driver identity

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

File descriptionPanda Kernel Memory Access Driver (x64)
ProductPanda Technologies
CompanyPanda Security, S.L.U.
Original filenamePSKMAD_64
Internal namePSKMAD_64
File version1.1.0.23
Copyright© Panda 2023

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 matches80 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface27 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (30)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetValueKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
IoCreateDeviceSecurelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 30 resolved.

IOCTL dispatch codes (9)

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
0x0022DFE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2042
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x00340308mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #194
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x58E80x5A006.26CODE, EXEC, READ
.rdata0x0DA00x0E004.47IDATA, READ
.data0x14C00x04001.12IDATA, READ, WRITE
.pdata0x04F80x06003.81IDATA, READ
PAGE0x1A470x1C006.05CODE, EXEC, READ
INIT0x0EB20x10004.92CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03680x04002.94IDATA, READ, DISCARD
.reloc0x00600x02000.32IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkEnforced
Mitigation score10 / 100

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (16)

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
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
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 2014
Serial3300000061C88B129C2A7F1D87000000000061
Valid from2023-04-06 19:16 UTC
Valid until2024-04-03 19:16 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Is pskmad.sys safe?

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

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

What is pskmad.sys?

pskmad.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