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

Analysis of SysInfoX64.sys: suspicious verdict, risk score 58/100. 2 YARA matches, 0/73 multi-engine detections. SHA256 52c5ffd62eae04b8. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

SysInfoX64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver SysInfoX64.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 matches2
Multi-engine detections0 / 73
File size15160 bytes
Code-signing signerCOMODO Time Stamping Signer
Analyzed2026-04-01
SHA25652c5ffd62eae04b890e0f4c96b84a3305e9b6571975c4352131cfc3d1b73a024
SHA1fd1db5794918d580e3ad0d71f4a559005de90f22
MD544fa80e2e754e679bdefccc8eb3d7a21

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 matches80 / 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 SysInfoX64.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
MmUnmapIoSpacemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard 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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x9C40B941mediumMETHOD_IN_DIRECTCUSTOM_LENOVO Function #3664
0x9C40A440mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2320
0x9C40A448mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2322
0x9C402664mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2457
0x9C406400mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2304
0x9C40A580mediumMETHOD_BUFFEREDCUSTOM_LENOVO Function #2400

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x0E760x10005.77CODE, EXEC, READ
.rdata0x01F40x02004.22IDATA, READ
.data0x01940x02001.02IDATA, READ, WRITE
.pdata0x00A80x02001.48IDATA, READ
INIT0x02E00x04003.99CODE, EXEC, READ, WRITE, DISCARD
.reloc0x00520x02000.56IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (2)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (12)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerCOMODO Time Stamping Signer
Signer organisationCOMODO CA Limited
IssuerUTN-USERFirst-Object
Serial478A8EFB59E1D83F0CE142D2A28707BE
Valid from2010-05-10 00:00 UTC
Valid until2015-05-10 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: 1. Exploitable paths: 0.

Frequently asked questions about SysInfoX64.sys

Is SysInfoX64.sys safe?

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

SysInfoX64.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 52c5ffd62eae04b890e0f4c96b84a3305e9b6571975c4352131cfc3d1b73a024.

What is SysInfoX64.sys?

SysInfoX64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by COMODO Time Stamping Signer.

Related: Other drivers signed by COMODO Time Stamping Signer · 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