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

Analysis of s.sys: vulnerable verdict, risk score 60/100. 0 YARA matches. SHA256 d9f203d2e0cdefab. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

s.sys - Analysis Report

DriverShield analyzed the Windows kernel driver s.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 matches0
File size23080 bytes
Code-signing signerHangzhou HollySys Automation Co., Ltd
Analyzed2026-10-05
SHA256d9f203d2e0cdefab407bcbaed424e9690d9b05c3eb80a71a69b1f8c6fd895944
SHA1d9c4553224bb71b9bb1f30b9d82d5da5ad82afc6
MD5d2533f77ded92d8eb830c682418f1a08

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 matches0 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface21 / 100
Known-vulnerable corpus0 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (12)

Kernel-mode APIs resolved from the Import Address Table of s.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
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
MmAllocateContiguousMemoryhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
RtlInitAnsiStringlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign

IOCTL dispatch codes (7)

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
0x00343123highMETHOD_NEITHERFILE_DEVICE_DISK Function #3144
0x00343323highMETHOD_NEITHERFILE_DEVICE_DISK Function #3272
0x00343523highMETHOD_NEITHERFILE_DEVICE_DISK Function #3400
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00342811mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2564
0x00802811mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2564
0x002245E9mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #378

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x0FCA0x10006.27CODE, EXEC, READ
.rdata0x033C0x04003.63IDATA, READ
.data0x27B80x28003.84IDATA, READ, WRITE
.pdata0x01080x02002.2IDATA, READ
INIT0x02EA0x04003.81IDATA, READ, WRITE, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (12)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerHangzhou HollySys Automation Co., Ltd
Signer organisationHangzhou HollySys Automation Co., Ltd
IssuerVeriSign Class 3 Code Signing 2010 CA
Serial72A5990618823715C3F8A40FE42FB732
Valid from2012-06-11 00:00 UTC
Valid until2013-06-11 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

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

Frequently asked questions about s.sys

Is s.sys safe?

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

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

What is s.sys?

s.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Hangzhou HollySys Automation Co., Ltd.

Related: Other drivers signed by Hangzhou HollySys Automation Co., Ltd · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact