GridinSoft Threat Intelligence

cpuidsdk.dll file report

Clean record File reputation report
MD5 71feadd9d56c1907ed828dfb0306e84c
Latest seen 2026-01-27 23:00:59 (4 months ago)
First seen 2024-04-12 23:00:49 (2 years ago)
Size 1 MB
Publisher CPUID
Signed by CPUID

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-04-12 23:00:49 (2 years ago); latest analysis 2026-01-27 23:00:59 (4 months ago).

Publisher context

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

Digital signature

Signed by CPUID. 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.

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 Clean, based on the latest analysis from 2026-01-27 23:00:59 (4 months 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: CPUID SDK Dynamic Link Library
Company Name: CPUID
MD5: 71feadd9d56c1907ed828dfb0306e84c
Size: 1 MB
First Published: 2024-04-12 23:00:49 (2 years ago)
Latest Published: 2026-01-27 23:00:59 (4 months ago)
Status: Clean (on last analysis)
Analysis Date: 2026-01-27 23:00:59 (4 months ago)
Signed By: CPUID
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.

%programfiles%

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 100.0%

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

cpuidsdk.dll is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x0003c555
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1916928

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

.text 1072128 bytes · 55.9% of section data
MD5 01e7fc02a4346370397637a26fe8f8d6
.rdata 505856 bytes · 26.4% of section data
MD5 64c01dcd457eadf01dbf64d56af84eaf
.data 18944 bytes · 1.0% of section data
MD5 29b50d50723e95a2870d532d816b4949
.rsrc 243712 bytes · 12.7% of section data
MD5 488831d7ec54c0e0ac387bf831f01a92
.reloc 76288 bytes · 4.0% of section data
MD5 720c42bfd195ec563883df8a80ffc73a

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 71feadd9d56c1907ed828dfb0306e84c.
  • 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.