Analysis of GGProtect64.sys: malicious verdict, risk score 88/100. 6 YARA matches, 2/74 multi-engine detections. SHA256 0aa69aee93c6be9b. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver GGProtect64.sys and assigned a verdict of Malicious with a composite risk score of 88/100, indicating malicious indicators (80-100 band).
| Verdict | Malicious (88/100) |
| YARA matches | 6 |
| Multi-engine detections | 2 / 74 |
| File size | 167592 bytes |
| Code-signing signer | Microsoft Windows Hardware Compatibility Publisher |
| Analyzed | 2026-09-06 |
| SHA256 | 0aa69aee93c6be9bc82680a7df99c114591038ae02e6666fc6e42acb09643111 |
| SHA1 | aaf935918bd7693a85225597439d69a8a1d186a1 |
| MD5 | b6a0d03122bd968b40ce97c145b491c7 |
Version resource data embedded in the GGProtect64.sys PE header, as extracted by the analysis engine.
| File description | GG租号-安全模块 |
|---|---|
| Product | GG租号 |
| Company | 湖南南澳网络科技有限公司 |
| Original filename | GGProtect64.sys |
| Internal name | GGProtect64.sys |
| File version | 2.2.6.6 |
| Copyright | Copyright (C) 2017 |
Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.
| Component | Sub-score |
|---|---|
| Multi-engine consensus | 0 / 100 |
| YARA signature matches | 100 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 75 / 100 |
| Known-vulnerable corpus | 100 / 100 |
| Code-signing state | 80 / 100 |
| Packing and entropy | 0 / 100 |
| Dynamic behaviour | 0 / 100 |
| CVE cross-reference | 0 / 100 |
Kernel-mode APIs resolved from the Import Address Table of GGProtect64.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmMapIoSpace | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| MmMapLockedPagesSpecifyCache | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| ZwTerminateProcess | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| MmGetSystemRoutineAddress | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| PsSetCreateProcessNotifyRoutineEx | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| ZwOpenProcess | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| ObRegisterCallbacks | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| MmGetPhysicalAddress | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| PsLookupProcessByProcessId | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| PsSetCreateProcessNotifyRoutine | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| ZwQuerySystemInformation | medium | Moderate risk - system modification capability |
| PsSetLoadImageNotifyRoutine | medium | Moderate risk - system modification capability |
| IoGetDeviceObjectPointer | medium | Moderate risk - system modification capability |
| KeBugCheckEx | medium | Moderate risk - system modification capability |
| ZwWriteFile | medium | Moderate risk - system modification capability |
| PsSetCreateThreadNotifyRoutine | medium | Moderate risk - system modification capability |
| ObReferenceObjectByHandle | medium | Moderate risk - system modification capability |
| ObOpenObjectByPointer | medium | Moderate risk - system modification capability |
| MmUnmapIoSpace | medium | Moderate risk - system modification capability |
| CmRegisterCallback | medium | Moderate risk - system modification capability |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| IoCreateSymbolicLink | low | Standard kernel API - generally benign |
| ZwClose | low | Standard kernel API - generally benign |
| KeSetEvent | low | Standard kernel API - generally benign |
| RtlInitAnsiString | low | Standard kernel API - generally benign |
| IoDeleteSymbolicLink | low | Standard kernel API - generally benign |
| ProbeForRead | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | low | Standard kernel API - generally benign |
Showing the 28 highest-relevance imports of 39 resolved.
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.
| Code | Severity | Transfer | Description |
|---|---|---|---|
| 0x00221843 | high | METHOD_NEITHER | FILE_DEVICE_UNKNOWN Function #1552 |
| 0x00809A8B | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #1698 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x0080EC81 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #2848 |
| 0x0080249C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2343 |
| 0x0080BA41 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #3728 |
| 0x0080B841 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #3600 |
| 0x0080B9C2 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_CUSTOM Function #3696 |
| 0x0080B8D0 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #3636 |
| 0x9876058A | medium | METHOD_OUT_DIRECT | CUSTOM_PROCESS Function #354 |
| 0x00223C54 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #3861 |
| 0x0022F6E9 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #3514 |
| 0x0022A2E9 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #2234 |
| 0x00223D10 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #3908 |
| 0x00223CE8 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #3898 |
| 0x00223D38 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #3918 |
| 0x0034A7E8 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #2554 |
| 0x0080930D | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #1219 |
| 0x00340030 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #12 |
| 0x00340036 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_DISK Function #13 |
| 0x00340032 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_DISK Function #12 |
| 0x002245C6 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_UNKNOWN Function #369 |
| 0x0022B941 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #3664 |
| 0xC3505BD4 | medium | METHOD_BUFFERED | CUSTOM_MSI Function #1781 |
Showing 24 of 25 extracted control codes.
Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.
| Section | Virtual size | Raw size | Entropy | Flags |
|---|---|---|---|---|
| .text | 0x1906A | 0x19200 | 6.58 | CODE, EXEC, READ |
| .rdata | 0x2124 | 0x2200 | 4.6 | IDATA, READ |
| .data | 0xDBA08 | 0x5000 | 3.71 | IDATA, READ, WRITE |
| .pdata | 0x0AD4 | 0x0C00 | 4.61 | IDATA, READ |
| INIT | 0x1120 | 0x1200 | 5.26 | CODE, EXEC, READ |
| .GGProte | 0x38EB | 0x3A00 | 6.64 | CODE, EXEC, READ |
| .reloc | 0x01EC | 0x0200 | 5.3 | IDATA, READ, DISCARD |
| .rsrc | 0x0310 | 0x0400 | 2.9 | IDATA, READ, DISCARD |
| Control Flow Guard | Enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 85 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| PUA_VULN_Driver_Ggprotectsys_Gg_0AA6 | medium | Detects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - GGProtect64.sys. Investigate matches in context: expected filenames or stand... |
| BYOVD_MemRW | critical | Phys memory mapping + device creation |
| BYOVD_ProcKill | critical | Process termination EDR killer |
| SUSP_PhysMem | high | Physical memory mapping |
| SUSP_Callbacks | medium | Kernel callback registration |
| MAL_EDRKiller | critical | Generic EDR killer pattern |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1003 | OS Credential Dumping | Credential Access |
| T1003.001 | OS Credential Dumping: LSASS Memory | Credential Access |
| T1006 | Direct Volume Access | Defense Evasion |
| T1014 | Rootkit | Defense Evasion |
| T1055.001 | Process Injection: DLL Injection | Defense Evasion |
| T1055.012 | Process Hollowing | Defense Evasion |
| T1068 | Exploitation for Privilege Escalation | Privilege Escalation |
| T1071 | Application Layer Protocol | Command and Control |
| T1211 | Exploitation for Defense Evasion | Defense Evasion |
| T1489 | Service Stop | Impact |
| T1543.003 | Windows Service | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1562.001 | Disable/Modify Tools | Defense Evasion |
| T1562.006 | Indicator Blocking | Defense Evasion |
| T1564.001 | Hidden Files and Directories | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
| Signer | Microsoft Windows Hardware Compatibility Publisher |
|---|---|
| Signer organisation | Microsoft Corporation |
| Issuer | Microsoft Windows Third Party Component CA 2014 |
| Serial | 330000006DAA072F958218C9E300000000006D |
| Valid from | 2024-10-10 19:04 UTC |
| Valid until | 2025-10-08 19:04 UTC (expired) |
| Signature validity | Not verified |
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.
Based on DriverShield static and dynamic analysis, GGProtect64.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.
GGProtect64.sys has a DriverShield composite risk score of 88/100, placing it in the malicious verdict band. SHA256: 0aa69aee93c6be9bc82680a7df99c114591038ae02e6666fc6e42acb09643111.
GGProtect64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Microsoft Windows Hardware Compatibility Publisher.
Related: Other drivers signed by Microsoft Windows Hardware Compatibility Publisher · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas