GridinSoft Threat Intelligence
ocl_cpu_task_executor32.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2018-04-22 17:08:48 (8 years ago); latest analysis 2021-08-26 20:41:48 (4 years ago).
Company metadata: Intel Corporation. Product metadata: Intel(R) OpenCL(TM) SDK.
Signed by Microsoft Windows Hardware Compatibility Publisher. ThreatInfo marks this publisher as trusted for this record.
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
ocl_cpu_task_executor32.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 2021-08-26 20:41:48 (4 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: | c6ebfe0d78418a7af3807be827ead777 |
| Size: | 384 KB |
| First Published: | 2018-04-22 17:08:48 (8 years ago) |
| Latest Published: | 2021-08-26 20:41:48 (4 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2021-08-26 20:41:48 (4 years ago) |
Overview
| 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.
Common Places:
| %appdata%\uniblue\driverscanner\drivers\154853\gfx_win10_64_15.65.4.4944 |
| %localappdata%\innovative solutions\drivermax\agent\restore\9r3tj8eaft28q0f18x01gik3l5kng349ka29l5on1524583im3\display |
ThreatInfo has observed ocl_cpu_task_executor32.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 ocl_cpu_task_executor32.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Canada with 33.3% 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 ocl_cpu_task_executor32.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
ocl_cpu_task_executor32.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
2a46bab95c0882f323e6b8e979012796
6e1fd2f253214ba8672aef43ef0a59bc
da483b34af7035df7d17e7e9f6ea565e
51a987df857e903e4c780c4b0600d4b3
134b5956ca7a32f7432044b77c8438ef
12d5e75102bef38b548b79d78b9596ab
a2ff5bf505a7e30ae21531e33423ab2b
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.