GridinSoft Threat Intelligence

ocl_cpu_clang_compiler32.dll file report

Clean record File reputation report
MD5 a644da4f8fdda1f0f78f62c2b4d139ab
Latest seen 2023-12-11 23:11:47 (2 years ago)
First seen 2017-05-22 09:04:49 (8 years ago)
Size 237 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 2017-05-22 09:04:49 (8 years ago); latest analysis 2023-12-11 23:11:47 (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.

File context

ocl_cpu_clang_compiler32.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:11:47 (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.

File Details

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

Overview

Signed By: Microsoft Windows Hardware Compatibility Publisher
Status: Valid

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

Common Places:

%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_clang_compiler32.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_clang_compiler32.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Brazil
Share 50.0%
Low High activity

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.

OS Version:

Windows 10 100.0%

The most common operating system signal for ocl_cpu_clang_compiler32.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_clang_compiler32.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 0x0000d081
Image base 0x10000000

PE Sections:

Sections 6
Raw data 224256

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

.text 152064 bytes · 67.8% of section data
MD5 fe4297db5eb0ea453717364130e87c44
.rdata 39936 bytes · 17.8% of section data
MD5 7f4aae7b65fa3d5831aa2285ed9cad45
.data 7680 bytes · 3.4% of section data
MD5 16bf7fe2fe9cd761da41dc1aa901209c
.tls 512 bytes · 0.2% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1536 bytes · 0.7% of section data
MD5 93be1108ee4801a574c899e68ae95cb3
.reloc 22528 bytes · 10.0% of section data
MD5 2d41fb9ab8a9dc17cb12221ac58a6212

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 a644da4f8fdda1f0f78f62c2b4d139ab.
  • 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.