GridinSoft Threat Intelligence

OpenCL.dll.bad file report

Under review File reputation report
MD5 9c70f52eb50eabfb7ff713437a8d9a21
Latest seen 2024-12-16 23:02:08 (a year ago)
First seen 2017-05-22 11:20:50 (9 years ago)
Size 63 KB
Publisher Khronos Group
Product Khronos OpenCL ICD

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:20:50 (9 years ago); latest analysis 2024-12-16 23:02:08 (a year ago).

Publisher context

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

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

File context

OpenCL.dll.bad is a Windows file recorded in the ThreatInfo database. It is associated with Khronos OpenCL ICD. The reported company name is Khronos Group. The current detection status is Undefined, based on the latest analysis from 2024-12-16 23:02:08 (a year 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
Company Name: Khronos Group
MD5: 9c70f52eb50eabfb7ff713437a8d9a21
Size: 63 KB
First Published: 2017-05-22 11:20:50 (9 years ago)
Latest Published: 2024-12-16 23:02:08 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-12-16 23:02:08 (a year ago)

Common Places:

%programfiles%\minergate
%programfiles%
%commonappdata%
%appdata%
%appdata%\monitor
%sysdrive%\miner
%appdata%\win32
%commonappdata%\windows
%sysdrive%
%localappdata%

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

File Names:

3 observed names
OpenCL.dll OpenCL.dll.dwn OpenCL.dll.bad

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Geographic signal

Observed country distribution

ThreatInfo has seen OpenCL.dll.bad across 98 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Russian Federation
Share 20.1%
Low High activity

The strongest geographic signal for this file is Russian Federation with 20.1% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 69.5%
Windows 7 21.6%
Windows 8.1 6.1%
Windows Server 2012 R2 1.1%
Windows 8 0.8%
Windows Server 2008 R2 0.8%
Windows Vista 0.1%
Windows Server 2016 0.1%

The most common operating system signal for OpenCL.dll.bad is Windows 10 with 69.5% 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

OpenCL.dll.bad 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.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x00003840
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 64000

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

.text 37888 bytes · 59.2% of section data
MD5 8b2817206fec4a7563ff5337ffc880d6
.rdata 16384 bytes · 25.6% of section data
MD5 5e7de09fdad174b4892c6ea6b19d1d92
.data 5120 bytes · 8.0% of section data
MD5 a562f2ef881b91c1f4789733057f4848
.pdata 2560 bytes · 4.0% of section data
MD5 07f7254a6367a1ab5833ec2bf88be5e1
.rsrc 1024 bytes · 1.6% of section data
MD5 556b7bee7f73a210823a2a14aeff4344
.reloc 1024 bytes · 1.6% of section data
MD5 d7368447c7918cb598d6e80f5aa0ead2

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.

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 9c70f52eb50eabfb7ff713437a8d9a21.
  • 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.