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

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

atdcm64a.sys - Analysis Report

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

Verdict	Suspicious (58/100)
YARA matches	2
Multi-engine detections	0 / 76
File size	51808 bytes
Code-signing signer	Symantec Time Stamping Services CA - G2
Analyzed	2026-04-02
SHA256	8b4800b6c640248a60a4e75af889119c4832b0a7bee7dd5e650a7c1bed19aeef
SHA1	11b5dda6c26a3d033845bfbe7f69b2c0b0123f77
MD5	3ee5927eba601e8b84cfc2158ac4af81

Driver identity

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

File description	ATI DSM Dynamic Driver
Product	ATI DSM Dynamic Driver
Company	Advanced Micro Devices, Inc.
Original filename	atidsmxx.sys
Internal name	atidsmxx.sys
File version	9.0.000.4
Copyright	Copyright (c) 2007, Advanced Micro Devices, Inc.

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.

Component	Sub-score
Multi-engine consensus	0 / 100
YARA signature matches	80 / 100
Dangerous kernel imports	100 / 100
IOCTL dispatch surface	36 / 100
Known-vulnerable corpus	0 / 100
Code-signing state	80 / 100
Packing and entropy	0 / 100
Dynamic behaviour	0 / 100
CVE cross-reference	0 / 100

Kernel imports (19)

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

API	Risk	Why it matters
MmMapIoSpace	critical	Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination
HalGetBusDataByOffset	high	Potentially dangerous - could be used for privilege escalation or security bypass
IoGetDeviceObjectPointer	medium	Moderate risk - system modification capability
MmUnmapIoSpace	medium	Moderate risk - system modification capability
ZwSetValueKey	medium	Moderate risk - system modification capability
KeInitializeEvent	low	Standard kernel API - generally benign
IofCompleteRequest	low	Standard kernel API - generally benign
KeDelayExecutionThread	low	Standard kernel API - generally benign
DbgPrint	low	Standard kernel API - generally benign
ZwOpenKey	low	Standard kernel API - generally benign
IoDeleteSymbolicLink	low	Standard kernel API - generally benign
ZwClose	low	Standard kernel API - generally benign
IoBuildDeviceIoControlRequest	low	Standard kernel API - generally benign
RtlInitUnicodeString	low	Standard kernel API - generally benign
KeWaitForSingleObject	low	Standard kernel API - generally benign
IoCreateSymbolicLink	low	Standard kernel API - generally benign
IoCreateDevice	low	Standard kernel API - generally benign
ExAllocatePoolWithTag	low	Standard kernel API - generally benign
IoDeleteDevice	low	Standard kernel API - generally benign

IOCTL dispatch codes (12)

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
0x0080880F	high	METHOD_NEITHER	FILE_DEVICE_CUSTOM Function #515
0x0022010F	high	METHOD_NEITHER	FILE_DEVICE_UNKNOWN Function #67
0x002200F0	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #60
0x0080249C	medium	METHOD_BUFFERED	FILE_DEVICE_CUSTOM Function #2343
0x0034C715	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #453
0x00347B15	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #3781
0x00344B15	medium	METHOD_IN_DIRECT	FILE_DEVICE_DISK Function #709
0x002247E8	medium	METHOD_BUFFERED	FILE_DEVICE_UNKNOWN Function #506
0x0080898D	medium	METHOD_IN_DIRECT	FILE_DEVICE_CUSTOM Function #611
0x0022470D	medium	METHOD_IN_DIRECT	FILE_DEVICE_UNKNOWN Function #451
0x00340354	medium	METHOD_BUFFERED	FILE_DEVICE_DISK Function #213
0x008002A2	medium	METHOD_OUT_DIRECT	FILE_DEVICE_CUSTOM Function #168

PE sections

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	0x38B9	0x3A00	6.07	CODE, EXEC, READ
.rdata	0x174C	0x1800	5.28	IDATA, READ
.data	0x0540	0x0200	0.28	IDATA, READ, WRITE
.pdata	0x01C8	0x0200	3.72	IDATA, READ
INIT	0x04DA	0x0600	4.39	CODE, EXEC, READ, WRITE, DISCARD
.rsrc	0x03B8	0x0400	3.12	IDATA, READ, DISCARD
.reloc	0x000C	0x0200	0.08	IDATA, READ, DISCARD

Exploit mitigations

Control Flow Guard	Not enabled
ASLR	Enabled
DEP	Enabled
Integrity check	Not enforced
Mitigation score	55 / 100

• No CFG - Control Flow Guard is not enabled. Indirect call targets are not validated, making the driver susceptible to control flow hijacking via corrupted function pointers or vtables.
• ASLR Enabled - Address Space Layout Randomization is active - base address is randomized on each load.
• DEP/NX Enabled - Data Execution Prevention is active - non-executable pages cannot be executed.
• Expired Certificate - The driver is signed but the certificate has expired. Windows may still load it depending on revocation policy.

YARA rule matches (2)

Rule	Severity	Detects
BYOVD_MemRW	critical	Phys memory mapping + device creation
SUSP_PhysMem	high	Physical memory mapping

MITRE ATT&CK techniques (16)

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.012	Process Hollowing	Defense Evasion
T1068	Exploitation for Privilege Escalation	Privilege Escalation
T1071	Application Layer Protocol	Command and Control
T1112	Modify Registry	Defense Evasion
T1211	Exploitation for Defense Evasion	Defense Evasion
T1542.001	Pre-OS Boot: System Firmware	Persistence
T1543.003	Windows Service	Persistence
T1547.001	Registry Run Keys	Persistence
T1553.002	Subvert Trust Controls: Code Signing	Defense Evasion
T1569.002	Service Execution	Execution
T1601	Modify System Image	Defense Evasion
T1652	Device Driver Discovery	Discovery

Code-signing chain

Signer	Symantec Time Stamping Services CA - G2
Signer organisation	Symantec Corporation
Issuer	Thawte Timestamping CA
Serial	7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from	2012-12-21 00:00 UTC
Valid until	2020-12-30 23:59 UTC (expired)
Signature validity	Not verified

• Certificate revision: 0x0200
• Certificate type: PKCS#7
• Chain: Symantec Time Stamping Services Signer - G4
• Chain: Advanced Micro Devices, Inc.
• Chain: VeriSign Class 3 Public Primary Certification Authority - G5
• Chain: VeriSign Class 3 Code Signing 2010 CA

Symbolic execution

Engine angr, status completed, 51 paths explored at a maximum depth of 51. Vulnerability classes reached: 1. Exploitable paths: 0.

Frequently asked questions about atdcm64a.sys

Is atdcm64a.sys safe?

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

atdcm64a.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 8b4800b6c640248a60a4e75af889119c4832b0a7bee7dd5e650a7c1bed19aeef.

What is atdcm64a.sys?

atdcm64a.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