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

Analysis of PGRHostControl.sys: suspicious verdict, risk score 58/100. 1 YARA match, 3/75 multi-engine detections. SHA256 4b0e9834dd672e4c. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

PGRHostControl.sys - Analysis Report

DriverShield analyzed the Windows kernel driver PGRHostControl.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 matches1
Multi-engine detections3 / 75
File size24824 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-09-06
SHA2564b0e9834dd672e4ce81464d8887c71f9a0942140557cd0ad321da9a1aa849959
SHA18d733095ac1cfcd799f58be3b8a25800f31e6fe2
MD5f0e46578a7fed41c88ec64fdc11d2a72

Driver identity

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

File descriptionPGRHostControl Driver
ProductPGRHostControl.sys
CompanyPoint Grey Research
Original filenamePGRHostControl.sys
Internal namePGRHostControl.sys
File version2, 7, 0, 0
CopyrightCopyright (c) Point Grey Research. All rights reserved.

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

Kernel imports (10)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
KeBugCheckExmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign

IOCTL dispatch codes (4)

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
0x008010B9mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1070
0x00808789mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #482
0x00340378mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #222

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x0A5E0x0C005.59CODE, EXEC, READ
.rdata0x026C0x04002.21IDATA, READ
.data0x00100x02000.28IDATA, READ, WRITE
.pdata0x00780x02001.04IDATA, READ
INIT0x028E0x04003.79CODE, EXEC, READ, DISCARD
.rsrc0x03D80x04003.17IDATA, READ, DISCARD
.reloc0x00100x02000.14IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score55 / 100

YARA rule matches (1)

RuleSeverityDetects
PUA_VULN_Driver_Pointgreyresearch_Pgrhostcontrolsys_Pgrhostcontrolsys_4B0EmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - PGRHostControl.sys. Investigate matches in context: expected filenames or st...

MITRE ATT&CK techniques (8)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1543.003Windows ServicePersistence
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Is PGRHostControl.sys safe?

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

PGRHostControl.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 4b0e9834dd672e4ce81464d8887c71f9a0942140557cd0ad321da9a1aa849959.

What is PGRHostControl.sys?

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

Related: Other drivers signed by Symantec Time Stamping Services CA - G2 · 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