STProcessMonitorNew.sys - Vulnerable (60/100) - DriverShield Analysis

Analysis of STProcessMonitorNew.sys: vulnerable verdict, risk score 60/100. 2 YARA matches, 7/75 multi-engine detections. SHA256 5b4f59236a9b950b. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

STProcessMonitorNew.sys - Analysis Report

DriverShield analyzed the Windows kernel driver STProcessMonitorNew.sys and assigned a verdict of Vulnerable with a composite risk score of 60/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (60/100)
YARA matches2
Multi-engine detections7 / 75
File size37456 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-06
SHA2565b4f59236a9b950bcd5191b35d19125f60cfb9e1a1e1aa2e4f914b6745dde9df
SHA168fec379f2ae76c3d2ce913f7be650cea1d06990
MD55761bd63da03686fc480245da7bd1e9f

Driver identity

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

File descriptionProcessMonitor Driver
ProductSafetica
CompanySafetica Technologies
Original filenameProcessMonitorDriver
Internal nameSTProcessMonitor
File version11,26,18,0
CopyrightCopyright (C) 2026, Safetica

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

Kernel imports (20)

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

APIRiskWhy it matters
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwWriteFilemediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
DbgPrintExlowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign

IOCTL dispatch codes (10)

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
0x00345B15mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1733
0x00348315mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #197
0x00346B05mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2753
0x00228F15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #965
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x0022CB15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #709
0x0034DF05mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1985
0x0034011DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #71
0x0034036CmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #219

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x47460x48006.39CODE, EXEC, READ
.rdata0x0A100x0C003.11IDATA, READ
.data0x05B80x02000.72IDATA, READ, WRITE
.pdata0x01EC0x02003.86IDATA, READ
.edata0x005C0x02001.04IDATA, READ
INIT0x06C40x08004.58CODE, EXEC, READ, DISCARD
.rsrc0x03D00x04003.1IDATA, READ, DISCARD
.reloc0x00380x02000.73IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkEnforced
Mitigation score100 / 100

YARA rule matches (2)

RuleSeverityDetects
PUA_VULN_Driver_Safeticatechnologies_Stprocessmonitor_Safetica_5B4FmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - STProcessMonitor.sys, ProcessMonitorDriver.sys, STProcessMonitor_v114.sys. I...
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (12)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
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

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2012
Serial330000013C4A61FB3578D2B6DD00000000013C
Valid from2025-11-13 19:59 UTC
Valid until2026-11-10 19:59 UTC
Signature validityVerified

Symbolic execution

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

Is STProcessMonitorNew.sys safe?

Based on DriverShield static and dynamic analysis, STProcessMonitorNew.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 60/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of STProcessMonitorNew.sys?

STProcessMonitorNew.sys has a DriverShield composite risk score of 60/100, placing it in the vulnerable verdict band. SHA256: 5b4f59236a9b950bcd5191b35d19125f60cfb9e1a1e1aa2e4f914b6745dde9df.

What is STProcessMonitorNew.sys?

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