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

Analysis of ene.sys: suspicious verdict, risk score 58/100. 0 YARA matches, 1/74 multi-engine detections. SHA256 16768203a471a19e. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

ene.sys - Analysis Report

DriverShield analyzed the Windows kernel driver ene.sys and assigned a verdict of Suspicious with a composite risk score of 58/100, indicating some risk signals warranting review (30-59 band).

Verdict	Suspicious (58/100)
YARA matches	0
Multi-engine detections	1 / 74
File size	17624 bytes
Code-signing signer	Microsoft Windows Hardware Compatibility Publisher
Analyzed	2026-04-02
SHA256	16768203a471a19ebb541c942f45716e9f432985abbfbe6b4b7d61a798cea354
SHA1	c47b890dda9882f9f37eccc27d58d6a774a2901f
MD5	fd80c3d38669b302de4b4b736941c0d1

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.

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	0 / 100
Dangerous kernel imports	78 / 100
IOCTL dispatch surface	12 / 100
Known-vulnerable corpus	100 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (11)

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

API	Risk	Why it matters
ZwMapViewOfSection	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ObReferenceObjectByHandle	medium	Moderate risk - system modification capability
KeBugCheckEx	medium	Moderate risk - system modification capability
ZwClose	low	Standard kernel API - generally benign
DbgPrint	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign

IOCTL dispatch codes (4)

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
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0080249C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2343
0x00808789	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #482
0x00802484	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2337

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	0x103C	0x1200	5.8	CODE, EXEC, READ
.rdata	0x013C	0x0200	2.64	IDATA, READ
.data	0x0110	0x0200	0.3	IDATA, READ, WRITE
.pdata	0x0054	0x0200	0.77	IDATA, READ
INIT	0x02A6	0x0400	3.73	CODE, EXEC, READ, WRITE, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Not enabled
DEP	Not enabled
Integrity check	Not enforced
Mitigation score	5 / 100

No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
No ASLR - ASLR is disabled. The driver loads at a predictable address, enabling reliable exploitation of memory corruption vulnerabilities.
No DEP - DEP is disabled. Data pages are executable, allowing shellcode execution from stack/heap buffers.
Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

MITRE ATT&CK techniques (7)

Techniques this driver could enable if loaded by an adversary.

ID	Technique	Tactic
T1003.001	OS Credential Dumping: LSASS Memory	Credential Access
T1055.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1543.003	Windows Service	Persistence
T1562.001	Impair Defenses	Defense Evasion
T1569.002	Service Execution	Execution
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Microsoft Windows Hardware Compatibility Publisher
Signer organisation	Microsoft Corporation
Issuer	Microsoft Windows Third Party Component CA 2014
Serial	33000000253A2738690A3451C1000000000025
Valid from	2018-09-06 21:30 UTC
Valid until	2019-09-06 21:30 UTC (expired)
Signature validity	Not verified

Certificate revision: 0x0200
Certificate type: PKCS#7
Chain: Microsoft Windows Third Party Component CA 2014

Symbolic execution

Engine angr, status completed, 29 paths explored at a maximum depth of 29. 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 ene.sys

Is ene.sys safe?

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

ene.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 16768203a471a19ebb541c942f45716e9f432985abbfbe6b4b7d61a798cea354.

What is ene.sys?

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