1.sys - Clean (29/100) - DriverShield Analysis

Analysis of 1.sys: clean verdict, risk score 29/100. 1 YARA match, 0/74 multi-engine detections. SHA256 a08c9e33e2e80c91. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

1.sys - Analysis Report

DriverShield analyzed the Windows kernel driver 1.sys and assigned a verdict of Clean with a composite risk score of 29/100, indicating no notable risk signals (0-29 band).

Verdict	Clean (29/100)
YARA matches	1
Multi-engine detections	0 / 74
File size	36864 bytes
Analyzed	2026-07-30
SHA256	a08c9e33e2e80c9157759abaa02a759231cf347e42df6e3004f0e8a507b4c475
SHA1	f6a1520304f4268140de0adc865b91b731fda869
MD5	4bc5cc270cc5fbdddb4ec71b628eaa95

How the 29/100 score breaks down

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	30 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	36 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	50 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (10)

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

API	Risk	Why it matters
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmUnmapIoSpace	medium	Moderate risk - system modification capability
ZwQuerySystemInformation	medium	Moderate risk - system modification capability
ZwSetValueKey	medium	Moderate risk - system modification capability
ZwClose	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
ZwOpenKey	low	Standard kernel API - generally benign
ZwQueryValueKey	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign

IOCTL dispatch codes (12)

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
0x00340033	high	METHOD_NEITHER	FILE_DEVICE_DISK Function #12
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0034E315	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #2245
0x008001BA	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #110
0x00800080	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #32
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337
0x00340036	medium	METHOD_OUT_DIRECT	FILE_DEVICE_DISK Function #13
0x00344B20	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #712
0x0034003A	medium	METHOD_OUT_DIRECT	FILE_DEVICE_DISK Function #14
0x00340034	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #13
0x0034004E	medium	METHOD_OUT_DIRECT	FILE_DEVICE_DISK Function #19
0x00340041	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #16

PE sections

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	0x5E92	0x6000	6.06	CODE, EXEC, READ
fothk	0x1000	0x1000	0.02	CODE, EXEC, READ
.rdata	0x0C20	0x0E00	3.56	IDATA, READ
.data	0x02B0	0x0400	1.83	IDATA, READ, WRITE
.pdata	0x0204	0x0400	2.4	IDATA, READ
INIT	0x0366	0x0400	4.22	CODE, EXEC, READ, DISCARD
.reloc	0x0120	0x0200	2.68	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	80 / 100

CFG Enabled - Control Flow Guard is active - indirect calls are validated against a bitmap of valid targets at runtime.
ASLR Enabled - Address Space Layout Randomization is active - base address is randomized on each load.
DEP/NX Enabled - Data Execution Prevention is active - non-executable pages cannot be executed.
Unsigned - The driver is not digitally signed. It requires test signing mode or a bootloader exploit to load on 64-bit Windows.

YARA rule matches (1)

Rule	Severity	Detects
SUSP_PhysMem	high	Physical memory mapping

MITRE ATT&CK techniques (12)

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
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
T1543.003	Windows Service	Persistence
T1547.001	Registry Run Keys	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1553.006	Code Signing Policy Modification	Defense Evasion
T1652	Device Driver Discovery	Discovery

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 1.sys

Is 1.sys safe?

Based on DriverShield static and dynamic analysis, 1.sys is assessed as clean, with no notable risk signals. Its composite risk score is 29/100 (verdict: clean). Always validate findings independently before acting.

What is the risk score of 1.sys?

1.sys has a DriverShield composite risk score of 29/100, placing it in the clean verdict band. SHA256: a08c9e33e2e80c9157759abaa02a759231cf347e42df6e3004f0e8a507b4c475.

What is 1.sys?

1.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators.