GridinSoft Threat Intelligence
IntelOpenCL64.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-05-22 10:19:33 (9 years ago); latest analysis 2023-06-19 23:02:28 (2 years ago).
Company metadata: Intel Corporation. Product metadata: Intel(R) OpenCL(TM) SDK.
Signed by 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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
IntelOpenCL64.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) OpenCL(TM) SDK. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2023-06-19 23:02:28 (2 years ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Intel(R) OpenCL(TM) SDK |
| Company Name: | Intel Corporation |
| MD5: | 0170c6fc9138e52e0be7bc36f29bf04d |
| Size: | 244 KB |
| First Published: | 2017-05-22 10:19:33 (9 years ago) |
| Latest Published: | 2023-06-19 23:02:28 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2023-06-19 23:02:28 (2 years ago) |
Overview
| Signed By: | Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on IntelOpenCL64.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\2v4o3739c65y4xm7p9j5fodo665meik7f8qy3qju788v8vs11o\display\pci_ven_8086@amp;dev_0106 |
| %programfiles%\drivertoolkit\backup |
| %localappdata%\innovative solutions\drivermax\agent\tmp\display |
| %localappdata%\innovative solutions\drivermax\agent\uploads\7v0m39h2cib217m2clxx8y8fct3efssc83u8pp767igyqgwyo9\display |
ThreatInfo has observed IntelOpenCL64.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 IntelOpenCL64.dll across 4 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Germany with 25.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 IntelOpenCL64.dll is Windows 10 with 50.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
IntelOpenCL64.dll is identified as pe for 64-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.
b2fabd8deda2eaeaea9727ffea89c09f
126574c48bc11e19820e1777e3e2d64c
698c47f75cf095bc8689467e47b0c4be
c279ffbce3360bb52d644f0331e97358
93de640c5ca02c39c670d73eec2a7adc
cfa26d50a39f4a6ffaa840156e27173d
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 hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.