Analysis of SysFile_X64.sys: malicious verdict, risk score 88/100. 2 YARA matches, 0/75 multi-engine detections. SHA256 5b204e0a24b5ea67. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver SysFile_X64.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).
| Verdict | Malicious (88/100) |
| YARA matches | 2 |
| Multi-engine detections | 0 / 75 |
| File size | 56088 bytes |
| Code-signing signer | GlobalSign Root CA |
| Analyzed | 2026-04-01 |
| SHA256 | 5b204e0a24b5ea67e79329a8c4eb0513cd52a0e7407b99530323fff4c5b59e34 |
| SHA1 | b980dec0bdf7b0925240d002626e56876afeec72 |
| MD5 | 9ddff9a4ec7e38e4e05fd16e2b1037ff |
Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.
| Component | Sub-score |
|---|---|
| Multi-engine consensus | 0 / 100 |
| YARA signature matches | 80 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 100 / 100 |
| Known-vulnerable corpus | 0 / 100 |
| Code-signing state | 0 / 100 |
| Packing and entropy | 0 / 100 |
| Dynamic behaviour | 0 / 100 |
| CVE cross-reference | 0 / 100 |
Kernel-mode APIs resolved from the Import Address Table of SysFile_X64.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmMapIoSpace | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| HalSetBusDataByOffset | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| HalGetBusDataByOffset | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| MmGetSystemRoutineAddress | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| ZwSetValueKey | medium | Moderate risk - system modification capability |
| ObOpenObjectByPointer | medium | Moderate risk - system modification capability |
| ZwCreateKey | medium | Moderate risk - system modification capability |
| MmUnmapIoSpace | medium | Moderate risk - system modification capability |
| DbgPrintEx | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| IoCreateSymbolicLink | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| ZwQueryValueKey | low | Standard kernel API - generally benign |
| IoDeleteSymbolicLink | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| ZwClose | low | Standard kernel API - generally benign |
| ZwOpenKey | low | Standard kernel API - generally benign |
| IoCreateDeviceSecure | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
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.
| Code | Severity | Transfer | Description |
|---|---|---|---|
| 0x9C402088 | critical (known exploit) | METHOD_BUFFERED | MSR write (LnvMSRIO) |
| 0x9C406104 | high (known exploit) | METHOD_BUFFERED | Physical memory read (LnvMSRIO) |
| 0x9C402084 | high (known exploit) | METHOD_BUFFERED | MSR read (LnvMSRIO) |
| 0x00343D07 | high | METHOD_NEITHER | FILE_DEVICE_DISK Function #3905 |
| 0x008012BF | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #1199 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x00802484 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2337 |
| 0x9C402004 | medium | METHOD_BUFFERED | CUSTOM_LENOVO Function #2049 |
| 0x9C402000 | medium | METHOD_BUFFERED | CUSTOM_LENOVO Function #2048 |
| 0x9C40A148 | medium | METHOD_BUFFERED | CUSTOM_LENOVO Function #2130 |
| 0x9C406144 | medium | METHOD_BUFFERED | CUSTOM_LENOVO Function #2129 |
| 0x00340030 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #12 |
| 0x0080248C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2339 |
| 0x008002A2 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_CUSTOM Function #168 |
Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.
| Section | Virtual size | Raw size | Entropy | Flags |
|---|---|---|---|---|
| .text | 0x39BC | 0x3A00 | 6.43 | CODE, EXEC, READ |
| .rdata | 0x0FDC | 0x1000 | 4.81 | IDATA, READ |
| .data | 0x04E8 | 0x0400 | 1.38 | IDATA, READ, WRITE |
| .pdata | 0x02B8 | 0x0400 | 3.07 | IDATA, READ |
| PAGE | 0x1C8C | 0x1E00 | 6.08 | CODE, EXEC, READ |
| INIT | 0x05FE | 0x0600 | 4.98 | CODE, EXEC, READ, DISCARD |
| .reloc | 0x0038 | 0x0200 | 0.7 | IDATA, READ, DISCARD |
| Control Flow Guard | Enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 100 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| BYOVD_MemRW | critical | Phys memory mapping + device creation |
| SUSP_PhysMem | high | Physical memory mapping |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1003 | OS Credential Dumping | Credential Access |
| T1003.001 | OS Credential Dumping: LSASS Memory | Credential Access |
| T1006 | Direct Volume Access | Defense Evasion |
| T1014 | Rootkit | Defense Evasion |
| T1055.012 | Process Hollowing | Defense Evasion |
| T1068 | Exploitation for Privilege Escalation | Privilege Escalation |
| T1112 | Modify Registry | Defense Evasion |
| T1211 | Exploitation for Defense Evasion | Defense Evasion |
| T1542.001 | Pre-OS Boot: System Firmware | Persistence |
| T1543.003 | Windows Service | Persistence |
| T1547.001 | Registry Run Keys | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1601 | Modify System Image | Defense Evasion |
| T1652 | Device Driver Discovery | Discovery |
| Signer | GlobalSign Root CA |
|---|---|
| Signer organisation | GlobalSign nv-sa |
| Issuer | GlobalSign Root CA |
| Serial | 40000000001154B5AC394 |
| Valid from | 1998-09-01 12:00 UTC |
| Valid until | 2028-01-28 12:00 UTC |
| Signature validity | Verified |
Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 4.
Based on DriverShield static and dynamic analysis, SysFile_X64.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.
SysFile_X64.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: 5b204e0a24b5ea67e79329a8c4eb0513cd52a0e7407b99530323fff4c5b59e34.
SysFile_X64.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 Root CA.
Related: Other drivers signed by GlobalSign Root CA · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas