GridinSoft Threat Intelligence

True Key Setup.exe file report

Clean record File reputation report
MD5 011cf166c2608e8a99c6b63f678f7f45
Latest seen 2023-07-30 23:55:33 (2 years ago)
First seen 2020-12-29 20:50:16 (5 years ago)
Size 293 KB
Publisher McAfee, Inc.
Signed by McAfee, Inc.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-12-29 20:50:16 (5 years ago); latest analysis 2023-07-30 23:55:33 (2 years ago).

Publisher context

Company metadata: McAfee, Inc.. Product metadata: Intel Security True Key.

Digital signature

Signed by McAfee, Inc.. 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.

True Key Setup.exe is a Windows file recorded in the ThreatInfo database. It is associated with Intel Security True Key. The reported company name is McAfee, Inc.. The current detection status is Clean, based on the latest analysis from 2023-07-30 23:55:33 (2 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 Security True Key
Company Name: McAfee, Inc.
MD5: 011cf166c2608e8a99c6b63f678f7f45
Size: 293 KB
First Published: 2020-12-29 20:50:16 (5 years ago)
Latest Published: 2023-07-30 23:55:33 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-07-30 23:55:33 (2 years ago)
Signed By: McAfee, Inc.
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.

%sysdrive%

ThreatInfo has observed True Key Setup.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 8.1 100.0%

The most common operating system signal for True Key Setup.exe is Windows 8.1 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.

True Key Setup.exe 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 0x000436fe
Image base 0x00400000

.NET Info:

MVID: 825430d2-f8af-4f18-980e-4310c1871dc7
Typelib ID: bd3f23c0-d43e-11cf-893b-00aa00bdce1a

PE Sections:

Sections 3
Raw data 279040

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

.text 268288 bytes · 96.1% of section data
MD5 6475225668521604bf6ed3dfa7e7bd89
.rsrc 10240 bytes · 3.7% of section data
MD5 6f05995d86368169b67c1ffdabcdb611
.reloc 512 bytes · 0.2% of section data
MD5 dbc0907c6dd3b499d04215c39b3b0fa9

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 011cf166c2608e8a99c6b63f678f7f45.
  • 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.