GridinSoft Threat Intelligence
ocl_cpu_tbb64.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:38:43 (4 years ago).
Company metadata: Intel Corporation. Product metadata: Intel(R) Threading Building Blocks for Windows.
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_tbb64.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Threading Building Blocks for Windows. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2021-08-26 20:38:43 (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) Threading Building Blocks for Windows |
| Company Name: | Intel Corporation |
| MD5: | 0390959d45000282be909b3ec06b2720 |
| Size: | 647 KB |
| First Published: | 2018-04-22 17:08:48 (8 years ago) |
| Latest Published: | 2021-08-26 20:38:43 (4 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2021-08-26 20:38:43 (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_tbb64.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_tbb64.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_tbb64.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_tbb64.dll 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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
291b634eb3beb1471c1166817d74fc9b
a18063dd62054b502425aaff5c4006d1
7be76079c2b2ab14ab3f916dee064cfd
c0b73097e3b68ac8abeb00dacb8ff207
7cd9c590642befe8d114d6ecc71d1de7
42051d48af5f5e37cd8496558b10b26e
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.