WppRecorder.sys - Clean (20/100) - DriverShield Analysis

Analysis of WppRecorder.sys: clean verdict, risk score 20/100. 0 YARA matches. SHA256 16f155138dcd559f. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

WppRecorder.sys - Analysis Report

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

VerdictClean (20/100)
YARA matches0
File size43832 bytes
Code-signing signerMicrosoft Windows
Analyzed2026-03-22
SHA25616f155138dcd559fc1dd5b4f0990969620bba5e2d114730bfa0b36060d4a47a9
SHA1493b0ea0fea38b7a8fae74567965110367890abb
MD5dc0a2ebc38d5b7f396f346b2c3b01699

Driver identity

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

File descriptionWPP Trace Recorder
ProductMicrosoft® Windows® Operating System
CompanyMicrosoft Corporation
Original filenameWppRecorder.sys
Internal nameWppRecorder.sys
File version10.0.19041.1 (WinBuild.160101.0800)
Copyright© Microsoft Corporation. All rights reserved.

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

Kernel imports (11)

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

APIRiskWhy it matters
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwQuerySystemInformationmediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwOpenKeylowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign

IOCTL dispatch codes (11)

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
0x008085C7highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #369
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00808389mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #226
0x0022B70DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3523
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00340032mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #12
0x0080009EmediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #39
0x00223412mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #3332
0x0034011AmediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #70
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
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
.text0x3F690x40006.03CODE, EXEC, READ
.rdata0x17C00x18004.66IDATA, READ
.data0x01C00x02000.41IDATA, READ, WRITE
.pdata0x06E40x08003.92IDATA, READ
.idata0x05980x06004.27IDATA, READ
NONPAGE0x00B00x02000.22IDATA, READ, WRITE
PAGE0x09500x0A005.84CODE, EXEC, READ
.edata0x02860x04003.67IDATA, READ
INIT0x00720x02001.68CODE, EXEC, READ, DISCARD
GFIDS0x00800x02001.11IDATA, READ, DISCARD
.rsrc0x04080x06002.41IDATA, READ, DISCARD
.reloc0x027C0x04003.28IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (7)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Production PCA 2011
Serial330000023241FB59996DCC4DFF000000000232
Valid from2019-05-02 21:24 UTC
Valid until2020-05-02 21:24 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about WppRecorder.sys

Is WppRecorder.sys safe?

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

What is the risk score of WppRecorder.sys?

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

What is WppRecorder.sys?

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