GridinSoft Threat Intelligence

ocl_cpu_task_executor64.dll file report

Clean record File reputation report
MD5 9d5038e8d50f8867dab42addf148db0c
Latest seen 2021-08-26 20:37:50 (4 years ago)
First seen 2018-04-22 17:08:48 (8 years ago)
Size 479 KB
Publisher Intel Corporation
Product Intel(R) OpenCL(TM) SDK
Signed by Microsoft Windows Hardware Compatibility Publisher

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-04-22 17:08:48 (8 years ago); latest analysis 2021-08-26 20:37:50 (4 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) OpenCL(TM) SDK.

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.

File context

ocl_cpu_task_executor64.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:37:50 (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: 9d5038e8d50f8867dab42addf148db0c
Size: 479 KB
First Published: 2018-04-22 17:08:48 (8 years ago)
Latest Published: 2021-08-26 20:37:50 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-08-26 20:37:50 (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_executor64.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_executor64.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Canada
Share 33.3%
Low High activity

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:

Windows 10 100.0%

The most common operating system signal for ocl_cpu_task_executor64.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_executor64.dll is identified as pe for 64-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 64-bit
Subsystem Windows CUI
Entry point 0x00026230
Image base 0x0000000180000000

PE Sections:

Sections 8
Raw data 472576

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

.text 287232 bytes · 60.8% of section data
MD5 2a20d0fdc80cddc3def81b7ac528f811
.rdata 130048 bytes · 27.5% of section data
MD5 d68d09662bf6397ad5b797708ce8409b
.data 26112 bytes · 5.5% of section data
MD5 f75c7f2206cff87e30e4b5f228a6dc6e
.pdata 19968 bytes · 4.2% of section data
MD5 d25c3f4bd742c584422cae985d609313
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 bb9615ae9510bf0390f05f456ec99b6a
.tls 512 bytes · 0.1% of section data
MD5 ba27cbc596dced9110bdff8963a62f7e
.rsrc 1536 bytes · 0.3% of section data
MD5 42320ac1c6484a465827aa9d489b6c9b
.reloc 6656 bytes · 1.4% of section data
MD5 4818f52be5c991decb70288de92fa03d

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