GridinSoft Threat Intelligence
amdocl.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2021-12-06 21:18:13 (4 years ago); latest analysis 2021-12-06 21:18:13 (4 years ago).
Company metadata: Advanced Micro Devices Inc.. Product metadata: OpenCL 2.0 AMD-APP (2117.13).
Signed by Advanced Micro Devices, Inc.;Advanced Micro Devices Inc.. The signature is reported as valid, but signed files can still be bundled or abused.
ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.
Recommended action
What to do next
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
amdocl.dll is a Windows file recorded in the ThreatInfo database. It is associated with OpenCL 2.0 AMD-APP (2117.13). The reported company name is Advanced Micro Devices Inc.. The current detection status is Undefined, based on the latest analysis from 2021-12-06 21:18:13 (4 years ago).
ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.
File Details
| Product Name: | OpenCL 2.0 AMD-APP (2117.13) |
| Company Name: | Advanced Micro Devices Inc. |
| MD5: | 5d99a1bc0665c449abd060e6e1a0c691 |
| Size: | 36 MB |
| First Published: | 2021-12-06 21:18:13 (4 years ago) |
| Latest Published: | 2021-12-06 21:18:13 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-12-06 21:18:13 (4 years ago) |
Overview
| Signed By: | Advanced Micro Devices, Inc.;Advanced Micro Devices Inc. |
| Status: | Valid |
The signature on amdocl.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %localappdata%\innovative solutions\drivermax\agent\restore\3sly1iw1nvy5v0sak4h12b6sr5u9574q73p3f199669ai3x980\display\pci_ven_1002&dev_9993 |
ThreatInfo has observed amdocl.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.
Geographic signal
Observed country distribution
ThreatInfo has seen amdocl.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Egypt with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for amdocl.dll is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.
Analysis
amdocl.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
07335cfaa480222e2a3155e96f72c70a
3b357324a5e0e7944a71c6a02626c53e
8b88e6e85ebf74218eab792239b1c2b1
bf619eac0cdf3f68d496ea9344137e8b
e3b980243f509802ffda493d5f65bf17
9c183bd1bfcd4318728cfa7457602931
PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.
Report conclusion
This file is still under review
ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.