GridinSoft Threat Intelligence
OpenCL32.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2021-11-05 21:58:28 (4 years ago); latest analysis 2024-03-09 23:05:08 (2 years ago).
Company metadata: Khronos Group. Product metadata: Khronos OpenCL ICD Loader.
Signed by Nvidia Corporation;Microsoft Windows Hardware Compatibility Publisher. 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
OpenCL32.dll is a Windows file recorded in the ThreatInfo database. It is associated with Khronos OpenCL ICD Loader. The reported company name is Khronos Group. The current detection status is Undefined, based on the latest analysis from 2024-03-09 23:05:08 (2 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: | Khronos OpenCL ICD Loader |
| Company Name: | Khronos Group |
| MD5: | 88a6898f65ab1719ef68ba381c421536 |
| Size: | 1 MB |
| First Published: | 2021-11-05 21:58:28 (4 years ago) |
| Latest Published: | 2024-03-09 23:05:08 (2 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2024-03-09 23:05:08 (2 years ago) |
Overview
| Signed By: | Nvidia Corporation;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on OpenCL32.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\uploads\24q56xpunsid12xayjqo5phmy1p0pqkq9028f75251t7l58672\display |
| %localappdata%\innovative solutions\drivermax\agent\restore\bg8rbdnqh0am5m6dhsotclquc9v400635l1s590pm05617t13b\display |
ThreatInfo has observed OpenCL32.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 OpenCL32.dll across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 50.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 OpenCL32.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
OpenCL32.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.
a13ad069b6e0b05126334dde27e955fe
40581f288e611ac38c0f6bf5097b4c4f
2e5787d87d9b0ae1e5392cb83eb3cccf
4fdacb1807e659f597148d576ed29457
d0b8d86e3e442cd4922e447478d309dd
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.