GridinSoft Threat Intelligence

UnInstX64.exe file report

Clean record File reputation report
MD5 532de3850a02f604348adb8955333e03
Latest seen 2022-09-06 23:59:21 (3 years ago)
First seen 2020-12-31 10:19:53 (5 years ago)
Size 472 KB
Publisher McAfee, LLC.
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-31 10:19:53 (5 years ago); latest analysis 2022-09-06 23:59:21 (3 years ago).

Publisher context

Company metadata: McAfee, LLC.. Product metadata: McAfee Endpoint Anti-Malware Protection.

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.

UnInstX64.exe is a Windows file recorded in the ThreatInfo database. It is associated with McAfee Endpoint Anti-Malware Protection. The reported company name is McAfee, LLC.. The current detection status is Clean, based on the latest analysis from 2022-09-06 23:59:21 (3 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: McAfee Endpoint Anti-Malware Protection
Company Name: McAfee, LLC.
MD5: 532de3850a02f604348adb8955333e03
Size: 472 KB
First Published: 2020-12-31 10:19:53 (5 years ago)
Latest Published: 2022-09-06 23:59:21 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-09-06 23:59:21 (3 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.

%commonappdata%

ThreatInfo has observed UnInstX64.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 50.0%
Windows 10 50.0%

The most common operating system signal for UnInstX64.exe is Windows 8.1 with 50.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.

UnInstX64.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 0x0002b0a4
Image base 0x0000000140000000

PE Sections:

Sections 5
Raw data 460288

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

.text 328192 bytes · 71.3% of section data
MD5 ecd8152762d7f6da09d2bd8c72c9d6dd
.rdata 99328 bytes · 21.6% of section data
MD5 0712abf5b056c8d3724849161d89f7ce
.data 9216 bytes · 2.0% of section data
MD5 0fae7dc15c29a441ecc5dbad9400a3e4
.pdata 20992 bytes · 4.6% of section data
MD5 5533c67b919e92c0d25431b4da84598a
.rsrc 2560 bytes · 0.6% of section data
MD5 8a01223fe0dd1543f110e0988af3aa67

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 532de3850a02f604348adb8955333e03.
  • 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.