GridinSoft Threat Intelligence

hkcmd.exe file report

Clean record File reputation report
MD5 b27c78752257743baa321e4471a56c14
Latest seen 2021-03-24 21:54:32 (5 years ago)
First seen 2021-03-24 21:54:32 (5 years ago)
Size 384 KB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-03-24 21:54:32 (5 years ago); latest analysis 2021-03-24 21:54:32 (5 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) Common User Interface.

Digital signature

Signed by Intel Corporation - Software and Firmware Products. 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.

hkcmd.exe is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Common User Interface. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2021-03-24 21:54:32 (5 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.

Product Name: Intel(R) Common User Interface
Company Name: Intel Corporation
MD5: b27c78752257743baa321e4471a56c14
Size: 384 KB
First Published: 2021-03-24 21:54:32 (5 years ago)
Latest Published: 2021-03-24 21:54:32 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-03-24 21:54:32 (5 years ago)
Signed By: Intel Corporation - Software and Firmware Products
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.

%localappdata%\slimware utilities inc\slimdrivers\backups\20180606t203110131835\pci

ThreatInfo has observed hkcmd.exe 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 7 100.0%

The most common operating system signal for hkcmd.exe is Windows 7 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.

hkcmd.exe 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 0x000210e0
Image base 0x0000000140000000

PE Sections:

Sections 5
Raw data 385024

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

.text 272896 bytes · 70.9% of section data
MD5 9f252f93163218e86909ac2da313d958
.rdata 75776 bytes · 19.7% of section data
MD5 15537b2861f8802af456c27ba31e19e2
.data 21504 bytes · 5.6% of section data
MD5 8872d34c6e0b3f456e8e848f59a24606
.pdata 11264 bytes · 2.9% of section data
MD5 7e40ddc12a9cf1a6a653a2ad8777b94d
.rsrc 3584 bytes · 0.9% of section data
MD5 18c3e1298ec422b6929d56490eeb241b

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