GridinSoft Threat Intelligence

dptf_cpu.sys file report

Under review File reputation report
MD5 0cebb21bca178b68f288b16c28ea981f
Latest seen 2024-12-27 23:01:38 (a year ago)
First seen 2020-10-28 16:20:58 (5 years ago)
Size 66 KB
Publisher Intel Corporation
Product Dynamic Platform Thermal Framework
Signed by Intel Corporation;Microsoft Windows Hardware Compatibility Publisher

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-10-28 16:20:58 (5 years ago); latest analysis 2024-12-27 23:01:38 (a year ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Dynamic Platform Thermal Framework.

Digital signature

Signed by Intel Corporation;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. 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.

File context

dptf_cpu.sys is a Windows file recorded in the ThreatInfo database. It is associated with Dynamic Platform Thermal Framework. The reported company name is Intel Corporation. The current detection status is Undefined, based on the latest analysis from 2024-12-27 23:01:38 (a year 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.

File Details

Product Name: Dynamic Platform Thermal Framework
Company Name: Intel Corporation
MD5: 0cebb21bca178b68f288b16c28ea981f
Size: 66 KB
First Published: 2020-10-28 16:20:58 (5 years ago)
Latest Published: 2024-12-27 23:01:38 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-12-27 23:01:38 (a year ago)

Overview

Signed By: Intel Corporation;Microsoft Windows Hardware Compatibility Publisher
Status: Valid

The signature on dptf_cpu.sys 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%\slimware utilities inc\slimdrivers\backups\20180213t073951595498\pci
%localappdata%\slimware utilities inc\driverupdate\backups\20180305t090738920\pci

ThreatInfo has observed dptf_cpu.sys 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 dptf_cpu.sys across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country India
Share 50.0%
Low High activity

The strongest geographic signal for this file is India 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 dptf_cpu.sys 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

dptf_cpu.sys is identified as pe for 64-bit systems. The subsystem is Native. 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 Native
Entry point 0x00005c10
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 48128

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

.text 26624 bytes · 55.3% of section data
MD5 0f04389fb75859c35a8a51d858bec947
.rdata 3072 bytes · 6.4% of section data
MD5 ad165d1b75aa8da1cc1d70ef656e1c51
.data 2048 bytes · 4.3% of section data
MD5 3a93ae6a540e74e773df25118b6bdf55
.pdata 1024 bytes · 2.1% of section data
MD5 f5c3eb5691dd4eaa79feec0085bba8a2
.gfids 512 bytes · 1.1% of section data
Uncommon name
MD5 844088389eb8bb381e1e67cf91a2462b
PAGE 6656 bytes · 13.8% of section data
Uncommon name
MD5 2e717f5a20886f37a34af30d3a16ea38
INIT 2048 bytes · 4.3% of section data
Uncommon name
MD5 03437cfd51b6259ab4cb902be27c65ab
.rsrc 5632 bytes · 11.7% of section data
MD5 c476c3ea902bb4107308bb781d792839
.reloc 512 bytes · 1.1% of section data
MD5 85a6a3495818fd835dfab272de3a6055

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 0cebb21bca178b68f288b16c28ea981f.
  • 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.