Analysis of dbk64.sys: vulnerable verdict, risk score 78/100. 3 YARA matches, 10/75 multi-engine detections. SHA256 18e1707b319c279c. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver dbk64.sys and assigned a verdict of Vulnerable with a composite risk score of 78/100, indicating a known or likely vulnerability surface (60-79 band).
| Verdict | Vulnerable (78/100) |
| YARA matches | 3 |
| Multi-engine detections | 10 / 75 |
| File size | 136048 bytes |
| Code-signing signer | GlobalSign Timestamping CA - G2 |
| Analyzed | 2026-09-06 |
| SHA256 | 18e1707b319c279c7e0204074088cc39286007a1cf6cb6e269d5067d8d0628c6 |
| SHA1 | 6053d258096bccb07cb0057d700fe05233ab1fbb |
| MD5 | 1c294146fc77565030603878fd0106f9 |
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 | 85 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 57 / 100 |
| Known-vulnerable corpus | 100 / 100 |
| Code-signing state | 0 / 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 dbk64.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| ZwMapViewOfSection | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| 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 |
| PsLookupProcessByProcessId | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| MmGetSystemRoutineAddress | 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 |
| KeAttachProcess | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| MmAllocateContiguousMemorySpecifyCache | 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 |
| MmAllocateContiguousMemory | 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 |
| ObOpenObjectByPointer | medium | Moderate risk - system modification capability |
| PsSetCreateThreadNotifyRoutine | medium | Moderate risk - system modification capability |
| KeBugCheckEx | medium | Moderate risk - system modification capability |
| ZwWriteFile | medium | Moderate risk - system modification capability |
| ObReferenceObjectByHandle | medium | Moderate risk - system modification capability |
| MmUnmapIoSpace | medium | Moderate risk - system modification capability |
| ZwDeleteFile | medium | Moderate risk - system modification capability |
| IoDeleteSymbolicLink | low | Standard kernel API - generally benign |
| ZwOpenKey | low | Standard kernel API - generally benign |
| KeDelayExecutionThread | low | Standard kernel API - generally benign |
| ZwCreateFile | low | Standard kernel API - generally benign |
| KeWaitForSingleObject | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| DbgPrint | low | Standard kernel API - generally benign |
| SeSinglePrivilegeCheck | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
Showing the 28 highest-relevance imports of 38 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 |
|---|---|---|---|
| 0x0080908B | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #1058 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x00809089 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #1058 |
| 0x0080248C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2339 |
| 0x00808289 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #162 |
| 0x00802484 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2337 |
| 0x00802494 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2341 |
| 0x0022E000 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #2048 |
| 0x00805424 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #1289 |
| 0xC350B999 | medium | METHOD_IN_DIRECT | CUSTOM_MSI Function #3686 |
| 0x0022E840 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #2576 |
| 0x0034247C | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #2335 |
| 0x0080E900 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2624 |
| 0x00805B0D | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #1731 |
| 0x00808B15 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #709 |
| 0x0022F4E8 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #3386 |
| 0x002224E8 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #2362 |
| 0x0080B908 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #3650 |
| 0x00808305 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #193 |
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 | 0x18FFF | 0x19000 | 5.97 | CODE, EXEC, READ |
| .rdata | 0x130C | 0x1400 | 4.37 | IDATA, READ |
| .data | 0xAEC4 | 0x0200 | 3.25 | IDATA, READ, WRITE |
| .pdata | 0x0A74 | 0x0C00 | 4.43 | IDATA, READ |
| INIT | 0x1020 | 0x1200 | 4.97 | CODE, EXEC, READ, DISCARD |
| .reloc | 0x0038 | 0x0200 | 0.68 | IDATA, READ, DISCARD |
| Control Flow Guard | Enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Enforced |
| Mitigation score | 100 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| BYOVD_MemRW | critical | Phys memory mapping + device creation |
| SUSP_PhysMem | high | Physical memory mapping |
| SUSP_Callbacks | medium | Kernel callback registration |
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 |
| 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 | Impair Defenses | 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 | GlobalSign Timestamping CA - G2 |
|---|---|
| Signer organisation | GlobalSign nv-sa |
| Issuer | GlobalSign Root CA |
| Serial | 400000000012F4EE152D7 |
| Valid from | 2011-04-13 10:00 UTC |
| Valid until | 2028-01-28 12:00 UTC |
| Signature validity | 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, dbk64.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 78/100 (verdict: vulnerable). Always validate findings independently before acting.
dbk64.sys has a DriverShield composite risk score of 78/100, placing it in the vulnerable verdict band. SHA256: 18e1707b319c279c7e0204074088cc39286007a1cf6cb6e269d5067d8d0628c6.
dbk64.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 Timestamping CA - G2.
Related: Other drivers signed by GlobalSign Timestamping 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