pcw.sys - Clean (27/100) - DriverShield Analysis

Analysis of pcw.sys: clean verdict, risk score 27/100. 0 YARA matches. SHA256 847188b15906af94. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

pcw.sys - Analysis Report

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

VerdictClean (27/100)
YARA matches0
File size60272 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA256847188b15906af94de0658b0f6f5827671ba659eead184b7ef5b274c7f9ae089
SHA16d78112d01b115efc8180ff95e733011649e2733
MD5b1dc8ca902109f8c0a6845ec270b0525

Driver identity

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

File descriptionPerformance Counters for Windows Driver
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenamepcw.sys
Internal namepcw.sys
File version10.0.19041.3636 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

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

Kernel imports (21)

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

APIRiskWhy it matters
MmCopyVirtualMemorycriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetValueKeymediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ProbeForWritelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
PsGetCurrentProcesslowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
SeAccessChecklowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwCloselowStandard 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
0x0080B58BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3426
0x00808D8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #866
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00340031mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #12
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x00340038mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #14
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0034BED8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #4022
0x003403A8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #234

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x06690x08005.13CODE, EXEC, READ
.rdata0x13D00x14004.71IDATA, READ
.data0x04380x04001.59IDATA, READ, WRITE
.pdata0x060C0x08003.62IDATA, READ
.idata0x106E0x12004.31IDATA, READ
PAGE0x71440x72006.14CODE, EXEC, READ
INIT0x03020x04005.03CODE, EXEC, READ, DISCARD
GFIDS0x00840x02001.21IDATA, READ, DISCARD
.rsrc0x04100x06002.49IDATA, READ, DISCARD
.reloc0x08040x0A004.89IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score90 / 100

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 Defenses: Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial33000004158295A1A3D82E2857000000000415
Valid from2023-02-03 00:05 UTC
Valid until2024-02-01 00:05 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about pcw.sys

Is pcw.sys safe?

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

What is the risk score of pcw.sys?

pcw.sys has a DriverShield composite risk score of 27/100, placing it in the clean verdict band. SHA256: 847188b15906af94de0658b0f6f5827671ba659eead184b7ef5b274c7f9ae089.

What is pcw.sys?

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

Related: Other drivers signed by Microsoft Windows · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact