superman.sys - Malicious (88/100) - DriverShield Analysis

Analysis of superman.sys: malicious verdict, risk score 88/100. 2 YARA matches, 40/76 multi-engine detections. SHA256 0052aa88e42055a2. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

superman.sys - Analysis Report

DriverShield analyzed the Windows kernel driver superman.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).

VerdictMalicious (88/100)
YARA matches2
Multi-engine detections40 / 76
File size56592 bytes
Code-signing signerGlobalSign CodeSigning CA - G2
Analyzed2026-09-06
SHA2560052aa88e42055a2eed5ddd17c3499c692360155e5e031a211edfcef577acce3
SHA1c80d7fe8279ddfd466505a24b9c8cc7a68b9d0e4
MD598b8507e725b3d28537fc374eb2de72d

Driver identity

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

File descriptionGMER Driver http://www.gmer.net
ProductGMER
CompanyGMER
Original filenamegmer64.sys
Internal namegmer64.sys
File version2, 0, 6983 built by: WinDDK
CopyrightCopyright (C) GMER 2003-2013

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

Kernel imports (33)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
KeAttachProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
KeBugCheckExmediumModerate risk - system modification capability
ZwQuerySystemInformationmediumModerate risk - system modification capability
ZwDeleteFilemediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ObOpenObjectByPointermediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwDeleteKeymediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
ZwOpenKeylowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 33 resolved.

IOCTL dispatch codes (24)

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
0x9876C094critical (known exploit)METHOD_BUFFEREDProcess termination by PID
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x00808D8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #866
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x9876C004mediumMETHOD_BUFFEREDCUSTOM_PROCESS Function #1
0x9876C050mediumMETHOD_BUFFEREDCUSTOM_PROCESS Function #20
0x9876C040mediumMETHOD_BUFFEREDCUSTOM_PROCESS Function #16
0x9876C008mediumMETHOD_BUFFEREDCUSTOM_PROCESS Function #2
0x9876C084mediumMETHOD_BUFFEREDCUSTOM_PROCESS Function #33
0x9876C088mediumMETHOD_BUFFEREDCUSTOM_PROCESS Function #34
0x00808F05mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #961
0x9876B941mediumMETHOD_IN_DIRECTCUSTOM_PROCESS Function #3664
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0022D315mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1221
0x00228F1DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #967
0x00228B1DmediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #711
0x00220116mediumMETHOD_OUT_DIRECTFILE_DEVICE_UNKNOWN Function #69
0x00220120mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #72
0x00340308mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #194
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x9ED10xA0006.16CODE, EXEC, READ
.rdata0x0E440x10004.18IDATA, READ
.data0x0F500x02000.3IDATA, READ, WRITE
.pdata0x04680x06003.46IDATA, READ
INIT0x0ACE0x0C004.82CODE, EXEC, READ, WRITE, DISCARD
.rsrc0x03680x04002.99IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (2)

RuleSeverityDetects
BYOVD_ProcKillcriticalProcess termination EDR killer
MAL_EDRKillercriticalGeneric EDR killer pattern

MITRE ATT&CK techniques (11)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Disable/Modify ToolsDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerGlobalSign CodeSigning CA - G2
Signer organisationGlobalSign nv-sa
IssuerGlobalSign Root CA
Serial400000000012F4EE1355C
Valid from2011-04-13 10:00 UTC
Valid until2019-04-13 10:00 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. 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 superman.sys

Is superman.sys safe?

Based on DriverShield static and dynamic analysis, superman.sys is flagged as malicious and should be treated as dangerous. Its composite risk score is 88/100 (verdict: malicious). Always validate findings independently before acting.

What is the risk score of superman.sys?

superman.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: 0052aa88e42055a2eed5ddd17c3499c692360155e5e031a211edfcef577acce3.

What is superman.sys?

superman.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 CodeSigning CA - G2.

Related: Other drivers signed by GlobalSign CodeSigning CA - G2 · 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