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

Analysis of ene.sys: suspicious verdict, risk score 58/100. 0 YARA matches, 2/75 multi-engine detections. SHA256 175eed7a4c6de9c3. 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).

VerdictSuspicious (58/100)
YARA matches0
Multi-engine detections2 / 75
File size20992 bytes
Code-signing signerMicrosoft Windows Hardware Compatibility Publisher
Analyzed2026-09-06
SHA256175eed7a4c6de9c3156c7ae16ae85c554959ec350f1c8aaa6dfe8c7e99de3347
SHA13cd037fbba8aae82c1b111c9f8755349c98bcb3c
MD57e6e2ed880c7ab115fca68136051f9ce

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 matches0 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface15 / 100
Known-vulnerable corpus100 / 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 ene.sys, ranked by exploitation relevance.

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign

IOCTL dispatch codes (5)

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
0x0022B807highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3585
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x008010B9mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1070
0x0080B900mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3648
0x0022B9C0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #3696

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x14B20x16005.98CODE, EXEC, READ
.rdata0x07C40x08005.31IDATA, READ
.data0x00200x02000.28IDATA, READ, WRITE
.pdata0x01800x02003.03IDATA, READ
INIT0x04840x06004.24CODE, EXEC, READ, DISCARD
.reloc0x00140x02000.23IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

MITRE ATT&CK techniques (12)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerMicrosoft Windows Hardware Compatibility Publisher
Signer organisationMicrosoft Corporation
IssuerMicrosoft Windows Third Party Component CA 2014
Serial330000003A6AE333708FDA7A7B00000000003A
Valid from2020-03-11 17:31 UTC
Valid until2021-03-05 17:31 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.

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: 175eed7a4c6de9c3156c7ae16ae85c554959ec350f1c8aaa6dfe8c7e99de3347.

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.

Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact