GLCKIO2.sys - Suspicious (58/100) - DriverShield Analysis

Analysis of GLCKIO2.sys: suspicious verdict, risk score 58/100. 0 YARA matches, 2/75 multi-engine detections. SHA256 61a1bdddd3c512e6. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

GLCKIO2.sys - Analysis Report

DriverShield analyzed the Windows kernel driver GLCKIO2.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 matches0
Multi-engine detections2 / 75
File size19392 bytes
Code-signing signerASUSTeK Computer Inc.
Analyzed2026-09-06
SHA25661a1bdddd3c512e681818debb5bee94db701768fc25e674fcad46592a3259bd0
SHA1cc51be79ae56bc97211f6b73cc905c3492da8f9d
MD5d253c19194a18030296ae62a10821640

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 matches0 / 100
Dangerous kernel imports93 / 100
IOCTL dispatch surface3 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (11)

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

APIRiskWhy it matters
ZwMapViewOfSectioncriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObReferenceObjectByHandlemediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign

IOCTL dispatch codes (1)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x13740x14006.31CODE, EXEC, READ
.rdata0x06D40x08004.99IDATA, READ
.data0x02180x02000.28IDATA, READ, WRITE
.pdata0x00FC0x02002.1IDATA, READ
INIT0x02B20x04003.93CODE, EXEC, READ, DISCARD
.reloc0x00140x02000.23IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (10)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerASUSTeK Computer Inc.
Signer organisationASUSTeK Computer Inc.
IssuerDigiCert SHA2 High Assurance Code Signing CA
Serial81666295845159F57AE88F441BF237E
Valid from2015-07-27 00:00 UTC
Valid until2018-08-01 12:00 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 20 paths explored at a maximum depth of 20. Vulnerability classes reached: 1. 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 GLCKIO2.sys

Is GLCKIO2.sys safe?

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

GLCKIO2.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 61a1bdddd3c512e681818debb5bee94db701768fc25e674fcad46592a3259bd0.

What is GLCKIO2.sys?

GLCKIO2.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by ASUSTeK Computer Inc..

Related: Other drivers signed by ASUSTeK Computer Inc. · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact