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

Analysis of GameDriverX64.sys: malicious verdict, risk score 88/100. 4 YARA matches, 10/75 multi-engine detections. SHA256 9ddae47ff968343a. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

GameDriverX64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver GameDriverX64.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 matches4
Multi-engine detections10 / 75
File size57552 bytes
Code-signing signerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Analyzed2026-09-06
SHA2569ddae47ff968343a8c32a5344060257fdc08e2a7bdb9a227c8b3a584ee3c9f1e
SHA17556ae58c215b8245a43f764f0676c7a8f0fdd1a
MD58f0577d28c4ff5f71b149f444bfaba8e

Driver identity

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

File descriptionGameDriverX64
ProductGameDriverX64
CompanyGameDriver
Original filenameGameDriverX64.sys
File version7.23.04.07

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 surface90 / 100
Known-vulnerable corpus100 / 100
Code-signing state0 / 100
Packing and entropy80 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (26)

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

APIRiskWhy it matters
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutinehighPotentially dangerous - could be used for privilege escalation or security bypass
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsLookupProcessByProcessIdhighPotentially dangerous - could be used for privilege escalation or security bypass
ObRegisterCallbackshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwDeleteFilemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
ZwWriteFilemediumModerate risk - system modification capability
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
RtlInitAnsiStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign

IOCTL dispatch codes (15)

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
0x00222000medium (known exploit)METHOD_BUFFEREDDriver communication init
0x0022BB07highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3777
0x00227417highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3333
0x00223417highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #3333
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x003437E8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #3578
0x00802824mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2569
0x0022EDE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2938
0x0080C8E9mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #570
0x0080A1E9mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2170
0x00340049mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #18
0x002202E9mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #186
0x0022B941mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3664
0x00340254mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #149
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
.text0x454D0x46006.51CODE, EXEC, READ
.rdata0x0D740x0E004.59IDATA, READ
.data0x168C0x06007.24IDATA, READ, WRITE
.pdata0x03900x04007.39IDATA, READ
PAGE0x05100x06007.06CODE, EXEC, READ
INIT0x0D740x0E005.92CODE, EXEC, READ
.uo100x1B300x1C005.76CODE, EXEC, READ
.reloc0x00240x02000.43IDATA, READ, DISCARD
.rsrc0x02AC0x04002.33IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (4)

RuleSeverityDetects
PUA_VULN_Driver_Gamedriver_Gamedriverx_9DDAmediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - GameDriverX64.sys. Investigate matches in context: expected filenames or sta...
BYOVD_ProcKillcriticalProcess termination EDR killer
SUSP_CallbacksmediumKernel callback registration
MAL_EDRKillercriticalGeneric EDR killer pattern

MITRE ATT&CK techniques (13)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1489Service StopImpact
T1543.003Windows ServicePersistence
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
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
Signer organisationDigiCert, Inc.
IssuerDigiCert Trusted Root G4
Serial8AD40B260D29C4C9F5ECDA9BD93AED9
Valid from2021-04-29 00:00 UTC
Valid until2036-04-28 23:59 UTC
Signature validityVerified

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 GameDriverX64.sys

Is GameDriverX64.sys safe?

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

GameDriverX64.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: 9ddae47ff968343a8c32a5344060257fdc08e2a7bdb9a227c8b3a584ee3c9f1e.

What is GameDriverX64.sys?

GameDriverX64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1.

Related: Other drivers signed by DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1 · 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