GridinSoft Threat Intelligence

cpuidsdk.dll file report

Under review File reputation report
MD5 5bbf77961224a6773df7ddf52579e91d
Latest seen 2023-11-22 23:06:23 (2 years ago)
First seen 2017-05-22 11:16:18 (9 years ago)
Size 1 MB
Publisher CPUID

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:16:18 (9 years ago); latest analysis 2023-11-22 23:06:23 (2 years ago).

Publisher context

Company metadata: CPUID. Product metadata: CPUID SDK Dynamic Link Library.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

cpuidsdk.dll is a Windows file recorded in the ThreatInfo database. It is associated with CPUID SDK Dynamic Link Library. The reported company name is CPUID. The current detection status is Undefined, based on the latest analysis from 2023-11-22 23:06:23 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: CPUID SDK Dynamic Link Library
Company Name: CPUID
MD5: 5bbf77961224a6773df7ddf52579e91d
Size: 1 MB
First Published: 2017-05-22 11:16:18 (9 years ago)
Latest Published: 2023-11-22 23:06:23 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-11-22 23:06:23 (2 years ago)
%sysdrive%\rei
%commonappdata%\reimage express
%commonappdata%
%sysdrive%

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

Windows 10 59.2%
Windows 7 22.9%
Windows 8.1 13.5%
Windows 8 4.1%
Windows Vista 0.4%

The most common operating system signal for cpuidsdk.dll is Windows 10 with 59.2% 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.

cpuidsdk.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.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x000d6be0
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 1402368

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

.text 975360 bytes · 69.6% of section data
MD5 2141f2780752172a561725174d7dd75c
.rdata 196096 bytes · 14.0% of section data
MD5 3e3813c3746848472c3d82a4722b82be
.data 91648 bytes · 6.5% of section data
MD5 43cc5dcc3805f86bcf6e1bd478afe167
.pdata 42496 bytes · 3.0% of section data
MD5 4b8b1206c4782bc62e9fbd7bcced445d
.rsrc 80896 bytes · 5.8% of section data
MD5 1fe4f7deb0ac0b7b56b8b27bf779a4ab
.reloc 15872 bytes · 1.1% of section data
MD5 d94397010b87e870bf2d4a813f76de8a

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 5bbf77961224a6773df7ddf52579e91d.
  • 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.