GoFly64.sys - Vulnerable (60/100) - DriverShield Analysis

Analysis of GoFly64.sys: vulnerable verdict, risk score 60/100. 1 YARA match, 3/76 multi-engine detections. SHA256 2fdfdd13a0c548bb. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

GoFly64.sys - Analysis Report

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

VerdictVulnerable (60/100)
YARA matches1
Multi-engine detections3 / 76
File size132088 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-04-14
SHA2562fdfdd13a0c548bb68c9d5aa8599a9265d4659da3e237fe7a42ac6ac06b9a06a
SHA1bc61ef6d7ad9ee878028f24d50e9dcf6d7d88bf2
MD526b2da88cb95b98b46bb985f67f76154

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

Kernel imports (28)

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

APIRiskWhy it matters
ZwTerminateProcesscriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
PsSetCreateProcessNotifyRoutineExhighPotentially dangerous - could be used for privilege escalation or security bypass
ZwOpenProcesshighPotentially dangerous - could be used for privilege escalation or security bypass
ZwWriteFilemediumModerate risk - system modification capability
PsSetLoadImageNotifyRoutinemediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
ZwSetInformationFilemediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwReadFilelowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
ZwQueryInformationFilelowStandard kernel API - generally benign
ExAllocatePoollowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
ZwCreateFilelowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign

IOCTL dispatch codes (17)

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
0x0080870FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #451
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0022ABE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2810
0x00223FE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #4090
0x0022C7E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #506
0x0080B914mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3653
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00800548mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #338
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0x003447E8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #506
0x0034E3E8mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2298
0x002217E8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1530
0x0080B9C0mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #3696
0x00802315mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2245
0x00340076mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #29

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x158B00x15A005.65CODE, EXEC, READ
.rdata0x14540x16005.22IDATA, READ
.data0x06010x02000.63IDATA, READ, WRITE
.pdata0x14580x16004.69IDATA, READ
INIT0x0FFE0x10005.68CODE, EXEC, READ, DISCARD
.reloc0x00440x02001IDATA, READ, DISCARD

Exploit mitigations

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

YARA rule matches (1)

RuleSeverityDetects
SUSP_CallbacksmediumKernel callback registration

MITRE ATT&CK techniques (15)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1014RootkitDefense Evasion
T1055.001Process Injection: DLL InjectionDefense Evasion
T1055.012Process HollowingDefense 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

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 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.

Frequently asked questions about GoFly64.sys

Is GoFly64.sys safe?

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

What is the risk score of GoFly64.sys?

GoFly64.sys has a DriverShield composite risk score of 60/100, placing it in the vulnerable verdict band. SHA256: 2fdfdd13a0c548bb68c9d5aa8599a9265d4659da3e237fe7a42ac6ac06b9a06a.

What is GoFly64.sys?

GoFly64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.

Related: Other drivers signed by Symantec Time Stamping Services 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