GridinSoft Threat Intelligence

OpenCL.dll file report

Clean record File reputation report
MD5 2ec4beee45e392007bb3f18c09f73057
Latest seen 2021-01-12 16:13:08 (5 years ago)
First seen 2021-01-12 16:09:30 (5 years ago)
Size 100 KB
Publisher Khronos Group

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-01-12 16:09:30 (5 years ago); latest analysis 2021-01-12 16:13:08 (5 years ago).

Publisher context

Company metadata: Khronos Group. Product metadata: Khronos OpenCL ICD Loader.

Digital signature

Signed by Microsoft Windows Hardware Compatibility Publisher. ThreatInfo marks this publisher as trusted for this record.

Observed locations

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

  1. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

OpenCL.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 Clean, based on the latest analysis from 2021-01-12 16:13:08 (5 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.

Product Name: Khronos OpenCL ICD Loader
Company Name: Khronos Group
MD5: 2ec4beee45e392007bb3f18c09f73057
Size: 100 KB
First Published: 2021-01-12 16:09:30 (5 years ago)
Latest Published: 2021-01-12 16:13:08 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 16:13:08 (5 years ago)
Signed By: Microsoft Windows Hardware Compatibility Publisher
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%localappdata%\slimware utilities inc\slimdrivers\backups\20200430t191843285538\pci

ThreatInfo has observed OpenCL.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.

Windows 10 100.0%

The most common operating system signal for OpenCL.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.

OpenCL.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x00004e88
Image base 0x10000000

PE Sections:

Sections 5
Raw data 93184

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 57344 bytes · 61.5% of section data
MD5 fb70f89d359ccbb02d292ac8d7aa98f2
.rdata 28160 bytes · 30.2% of section data
MD5 93a87717d8c4935084b9781d350f6e0f
.data 2048 bytes · 2.2% of section data
MD5 9658100e63bc8576de700beed6ff8e8a
.rsrc 1536 bytes · 1.6% of section data
MD5 e458ac705e25a5c3bfa9d27a8c39c7b0
.reloc 4096 bytes · 4.4% of section data
MD5 677b17e8fe31b469f09cae629879d03e

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.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 2ec4beee45e392007bb3f18c09f73057.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.