dokan2.sys - Suspicious (35/100) - DriverShield Analysis

Analysis of dokan2.sys: suspicious verdict, risk score 35/100. 0 YARA matches, 0/75 multi-engine detections. SHA256 7d17c08c7e6b0043. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

dokan2.sys - Analysis Report

DriverShield analyzed the Windows kernel driver dokan2.sys and assigned a verdict of Suspicious with a composite risk score of 35/100, indicating some risk signals warranting review (30-59 band).

VerdictSuspicious (35/100)
YARA matches0
Multi-engine detections0 / 75
File size403472 bytes
Code-signing signerGlobalSign CodeSigning CA - SHA256 - G3
Analyzed2026-08-26
SHA2567d17c08c7e6b004371ee65930d59d93c10d6e10a87ce0167ae21766f73b2d4a6
SHA13336df1f77f97db854808201795a031dc02b019e
MD58dbba0f3fdd02ddbb9df119037c318c9

Driver identity

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

File descriptionDokan Driver
ProductDokan
CompanyDokan Project
Original filenamedokan.sys
Internal namedokan.sys
File version2.0.3.1000
CopyrightCopyright (C) 2021

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

Kernel imports (29)

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

APIRiskWhy it matters
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
ObReferenceObjectByHandlemediumModerate risk - system modification capability
IoGetDeviceObjectPointermediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
KeBugCheckExmediumModerate risk - system modification capability
IoCreateSymbolicLinklowStandard kernel API - generally benign
ProbeForWritelowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
ZwCloselowStandard kernel API - generally benign
DbgPrintExlowStandard kernel API - generally benign
KeDelayExecutionThreadlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
KeSetEventlowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
KeInitializeEventlowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoBuildDeviceIoControlRequestlowStandard kernel API - generally benign
DbgPrintlowStandard kernel API - generally benign
ZwOpenFilelowStandard kernel API - generally benign
KeWaitForSingleObjectlowStandard kernel API - generally benign
ProbeForReadlowStandard kernel API - generally benign

Showing the 28 highest-relevance imports of 29 resolved.

IOCTL dispatch codes (40)

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
0x0080850FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #323
0x00808F8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #994
0x0080828BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #162
0x00347983highMETHOD_NEITHERFILE_DEVICE_DISK Function #3680
0x0080818BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #98
0x0080808BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #34
0x00349F87highMETHOD_NEITHERFILE_DEVICE_DISK Function #2017
0x0080B8C3highMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #3632
0x00225A77highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #1693
0x0034365FhighMETHOD_NEITHERFILE_DEVICE_DISK Function #3479
0x00808D8BhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #866
0x0022010FhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #67
0x00226423highMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #2312
0x0022011BhighMETHOD_NEITHERFILE_DEVICE_UNKNOWN Function #70
0x0080840FhighMETHOD_NEITHERFILE_DEVICE_CUSTOM Function #259
0x00343D07highMETHOD_NEITHERFILE_DEVICE_DISK Function #3905
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00808589mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #354
0x0080BE41mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #3984
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x0080958DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1379

Showing 24 of 40 extracted control codes.

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x500470x502006.22CODE, EXEC, READ
.rdata0x27CC0x28004.91IDATA, READ
.data0x05E10x04001.43IDATA, READ, WRITE
.pdata0x0CFC0x0E005.09IDATA, READ
PAGE0x790D0x7A006.33CODE, EXEC, READ
INIT0x1EE00x20005.72CODE, EXEC, READ, DISCARD
.rsrc0x03980x04002.98IDATA, READ, DISCARD
.reloc0x00400x02000.96IDATA, READ, DISCARD

Exploit mitigations

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

MITRE ATT&CK techniques (11)

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
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerGlobalSign CodeSigning CA - SHA256 - G3
Signer organisationGlobalSign nv-sa
IssuerGlobalSign
Serial481B6A0726D2E83F2602D4825ACD
Valid from2016-06-15 00:00 UTC
Valid until2024-06-15 00:00 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 2.

Frequently asked questions about dokan2.sys

Is dokan2.sys safe?

Based on DriverShield static and dynamic analysis, dokan2.sys shows some suspicious signals and warrants manual review. Its composite risk score is 35/100 (verdict: suspicious). Always validate findings independently before acting.

What is the risk score of dokan2.sys?

dokan2.sys has a DriverShield composite risk score of 35/100, placing it in the suspicious verdict band. SHA256: 7d17c08c7e6b004371ee65930d59d93c10d6e10a87ce0167ae21766f73b2d4a6.

What is dokan2.sys?

dokan2.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 CodeSigning CA - SHA256 - G3.

Related: Other drivers signed by GlobalSign CodeSigning CA - SHA256 - G3 · What an IOCTL dispatch code is · BYOVD research index · full driver database · CVE library · code signing atlas


DriverShield © 2025-2026 · Terms · Privacy · Contact