Intel_GPA_Intel_GPA_emon_bin64... - Suspicious (58/100) - DriverShield Analysis

Analysis of Intel_GPA_Intel_GPA_emon_bin64_sepdrv_win7_sepdrv5.sys: suspicious verdict, risk score 58/100. 3 YARA matches, 0/73 multi-engine detections. SHA256 4e12003cc153512d. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

Intel_GPA_Intel_GPA_emon_bin64_sepdrv_win7_sepdrv5.sys - Analysis Report

DriverShield analyzed the Windows kernel driver Intel_GPA_Intel_GPA_emon_bin64_sepdrv_win7_sepdrv5.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 matches3
Multi-engine detections0 / 73
File size224128 bytes
Code-signing signerAddTrust External CA Root
Analyzed2026-10-10
SHA2564e12003cc153512d6791db3f6d741378d16c5552e5b96cdaa5e124bf3babda25
SHA192edcdf5954c59c923c4b15ce0bd4fc02317c2ab
MD5538b063201161f23eff427193dc7493f

Driver identity

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

File descriptionSampling Enabling Product
ProductSampling Enabling Product
CopyrightCopyright(C) 2007-2020 Intel Corporation. All rights reserved.

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

Kernel imports (31)

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

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially 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
MmAllocateContiguousMemoryhighPotentially dangerous - could be used for privilege escalation or security bypass
HalSetBusDataByOffsethighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetPhysicalAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwSetValueKeymediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
KeWaitForSingleObjectlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 31 resolved.

IOCTL dispatch codes (34)

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
0x0080A183highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #2144
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x00801BA4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #1769
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0080A7E8mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2554
0x008087E8mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #506
0x00800FE8mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #1018
0x0034A7E8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2554
0x00342BE8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2810
0x008024ACmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2347
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x002257E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1530
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00222024mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2057
0x00808D89mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #866
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x00802024mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2057
0x0080B688mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3490
0x0080A801mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2560
0x008024A4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2345
0x008000B8mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #46
0x008024B4mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2349
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343

Showing 24 of 34 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x2400E0x242006.52CODE, EXEC, READ
.rdata0x1B600x1C004.53IDATA, READ
.data0x1CF2C80x64001.79IDATA, READ, WRITE
.pdata0x0F240x10005.15IDATA, READ
PAGE0x1A470x1C006.07CODE, EXEC, READ
INIT0x0B620x0C005.15CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x02C00x04002.4IDATA, READ, DISCARD
.reloc0x1AA60x1C002.1IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLRNot enabled
DEPNot enabled
Integrity checkNot enforced
Mitigation score5 / 100

YARA rule matches (3)

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

MITRE ATT&CK techniques (18)

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

Code-signing chain

SignerAddTrust External CA Root
Signer organisationAddTrust AB
IssuerMicrosoft Code Verification Root
Serial3300000035D8D5595B0671412B000000000035
Valid from2013-08-15 20:26 UTC
Valid until2023-08-15 20:36 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status timeout, 38 paths explored at a maximum depth of 38. Vulnerability classes reached: 0. Exploitable paths: 1.

Frequently asked questions about Intel_GPA_Intel_GPA_emon_bin64_sepdrv_win7_sepdrv5.sys

Is Intel_GPA_Intel_GPA_emon_bin64_sepdrv_win7_sepdrv5.sys safe?

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

Intel_GPA_Intel_GPA_emon_bin64_sepdrv_win7_sepdrv5.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 4e12003cc153512d6791db3f6d741378d16c5552e5b96cdaa5e124bf3babda25.

What is Intel_GPA_Intel_GPA_emon_bin64_sepdrv_win7_sepdrv5.sys?

Intel_GPA_Intel_GPA_emon_bin64_sepdrv_win7_sepdrv5.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by AddTrust External CA Root.

Related: Other drivers signed by AddTrust External CA Root · 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