ocl_cpu_cpu_device32.dll file report

MD5 bc5c989c6ababa2e00752cc0bcaff2f0
Latest seen 2023-12-11 23:33:54 (2 years ago)
First seen 2017-05-22 09:04:42 (8 years ago)
Size 510 KB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-22 09:04:42 (8 years ago); latest analysis 2023-12-11 23:33:54 (2 years ago).

Publisher context

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

Digital signature

Signed by Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.

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.

ocl_cpu_cpu_device32.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-12-11 23:33:54 (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.

Product Name: Intel(R) OpenCL(TM) SDK
Company Name: Intel Corporation
MD5: bc5c989c6ababa2e00752cc0bcaff2f0
Size: 510 KB
First Published: 2017-05-22 09:04:42 (8 years ago)
Latest Published: 2023-12-11 23:33:54 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-12-11 23:33:54 (2 years ago)

The signature on ocl_cpu_cpu_device32.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.

%localappdata%\innovative solutions\drivermax\agent\uploads\55qm5eg6mj3jhs8t9878e2a485a00lbffog7w6ybk1yv266x31\display\pci_ven_8086@amp;dev_0416
%localappdata%\innovative solutions\drivermax\agent\uploads\bbcur974lee8586295185ctc6ep64xl0wu53riscob127mi1tb\display
%localappdata%\innovative solutions\drivermax\agent\uploads\3g8928js2t22o4o26mw3283l0wqb0f5x19de6304t0vvxn0k8a\display
%localappdata%\innovative solutions\drivermax\agent\uploads\227n90436fqy3b9wo9k78xvbg4b0yw4ou8w5c6w31334lt9608\display

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

50.0%
25.0%
25.0%

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

Windows 10 100.0%

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

ocl_cpu_cpu_device32.dll is identified as pe for 32 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.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x0003d01a

PE Sections:

Name Size of data MD5
.text 362496 f0feb20284984c18c496971d61183aab
.rdata 84480 9ba593574e62ad2d4e456bc48faffcc3
.data 19456 ce2186703d12bcabb343efcdb5159ab1
.tls 512 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1536 631e553c352582743ae8eaba088aefc6
.reloc 35840 ca8a1ca712a4b6e0d682105c38934123

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.

More information: