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

Analysis of ProcessCtr.sys: vulnerable verdict, risk score 78/100. 4 YARA matches, 7/75 multi-engine detections. SHA256 d64eeb940daffdc8. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

ProcessCtr.sys - Analysis Report

DriverShield analyzed the Windows kernel driver ProcessCtr.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 matches4
Multi-engine detections7 / 75
File size44440 bytes
Code-signing signerGlobalSign
Analyzed2026-09-06
SHA256d64eeb940daffdc8327fb18b160c20e539088cf8407813655f59efa9fdf0022e
SHA172ffc3e2afc384657bc1559eb69b4651e24d57d6
MD55ee52684ee22f3ad730b6af7e327d82b

Driver identity

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

File descriptionEsafeNet ProcessCtrl
ProductProcessCtrl
CompanyEsafeNet
Original filenameProcessCtrl
Internal nameEsafeNet ProcessCtrl
File version1.0.1.2
CopyrightCopyright (C) 2020

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

Kernel imports (26)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetValueKeymediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeWaitForSingleObjectlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
KeSetEventlowStandard 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
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080B78DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3555
0x003402D8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #182

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x2A7B0x2C006.16CODE, EXEC, READ
.rdata0x07F40x08004.27IDATA, READ
.data0x46BE00x02000.28IDATA, READ, WRITE
.pdata0x02580x04002.66IDATA, READ
INIT0x076A0x08005.15CODE, EXEC, READ, DISCARD
.rsrc0x03380x04002.69IDATA, READ, DISCARD
.reloc0x00140x02000.26IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Esafenet_Esafenetprocessctrl_Processctrl_D64EmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - ProcessCtr.sys. Investigate matches in context: expected filenames or standa...
BYOVD_ProcKillcriticalProcess termination EDR killer
SUSP_CallbacksmediumKernel callback registration
MAL_EDRKillercriticalGeneric EDR killer pattern

MITRE ATT&CK techniques (17)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense 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.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerGlobalSign
Signer organisationGlobalSign
IssuerGlobalSign Root CA
Serial1EE5F169DFF97352B6465D66A
Valid from2018-09-19 00:00 UTC
Valid until2028-01-28 12:00 UTC
Signature validityVerified

Symbolic execution

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

Is ProcessCtr.sys safe?

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

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

What is ProcessCtr.sys?

ProcessCtr.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by GlobalSign.

Related: Other drivers signed by GlobalSign · 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