HNOs2Ec.sys - Vulnerable (72/100) - DriverShield Analysis

Analysis of HNOs2Ec.sys: vulnerable verdict, risk score 72/100. 3 YARA matches, 0/75 multi-engine detections. SHA256 ebcb856723bd023c. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

HNOs2Ec.sys - Analysis Report

DriverShield analyzed the Windows kernel driver HNOs2Ec.sys and assigned a verdict of Vulnerable with a composite risk score of 72/100, indicating a known or likely vulnerability surface (60-79 band).

VerdictVulnerable (72/100)
YARA matches3
Multi-engine detections0 / 75
File size57152 bytes
Code-signing signerGlobalSign Code Signing Root R45
Analyzed2026-09-06
SHA256ebcb856723bd023c7ecb40fc71b3ff2ed3795fa08313f397569866167655dadf
SHA1bc0e0d6174f8c2330337313fbfc90fbff6de771f
MD561b266601cd36709085ed7bfdd7e0e31

Driver identity

Version resource data embedded in the HNOs2Ec.sys PE header, as extracted by the analysis engine.

File descriptionHNOs2Ec
ProductHonor
CompanyHonor Device Co., Ltd.
Original filenameHNOs2Ec.sys
Internal nameHNOs2Ec
File version1.0.0.1
CopyrightCopyright (C) Honor Device Co., Ltd. 2016-2020. All rights reserved.

How the 72/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 matches85 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface60 / 100
Known-vulnerable corpus0 / 100
Code-signing state0 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (29)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
HalGetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ZwCloselowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 29 resolved.

IOCTL dispatch codes (20)

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
0x0080850FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #323
0x0022BB07highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3777
0x00343D07highMETHOD_NEITHERFILE_DEVICE_DISK Function #3905
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0034EB05mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2753
0x0034DF05mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1985
0x0022B315mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3269
0x00229315mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1221
0x00221B15mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1733
0x0034930DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1219
0x0034770DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #3523
0x00342B05mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #2753
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x0022630DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #2243
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13
0x00808789mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #482
0x00340314mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #197
0x008002A2mediumMETHOD_OUT_DIRECTFILE_DEVICE_CUSTOM Function #168

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x2A040x2C006.09CODE, EXEC, READ
.rdata0x0F3C0x10004.1IDATA, READ
.data0x045C0x04001.27IDATA, READ, WRITE
.pdata0x04680x06003.43IDATA, READ
PAGE0x2A400x2C006.15CODE, EXEC, READ
INIT0x09DC0x0A005.36CODE, EXEC, READ, DISCARD
.rsrc0x03780x04002.94IDATA, READ, DISCARD
.reloc0x00380x02000.73IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score70 / 100

YARA rule matches (3)

RuleSeverityDetects
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (21)

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.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Disable/Modify ToolsDefense Evasion
T1562.006Indicator BlockingDefense Evasion
T1564.001Hidden Files and DirectoriesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerGlobalSign Code Signing Root R45
Signer organisationGlobalSign nv-sa
IssuerGlobalSign
Serial7803184245708A41CF6F01B8EEB4A954
Valid from2020-07-28 00:00 UTC
Valid until2029-03-18 00:00 UTC
Signature validityVerified

Symbolic execution

Engine angr, status completed, 100 paths explored at a maximum depth of 100. Vulnerability classes reached: 0. Exploitable paths: 2.

Frequently asked questions about HNOs2Ec.sys

Is HNOs2Ec.sys safe?

Based on DriverShield static and dynamic analysis, HNOs2Ec.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 72/100 (verdict: vulnerable). Always validate findings independently before acting.

What is the risk score of HNOs2Ec.sys?

HNOs2Ec.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: ebcb856723bd023c7ecb40fc71b3ff2ed3795fa08313f397569866167655dadf.

What is HNOs2Ec.sys?

HNOs2Ec.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 Code Signing Root R45.

Related: Other drivers signed by GlobalSign Code Signing Root R45 · 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