GridinSoft Threat Intelligence

uninstall.exe file report

Under review File reputation report
MD5 4b697b715108786358c86fcf85e78807
Latest seen 2024-12-13 23:01:13 (a year ago)
First seen 2019-04-22 21:39:50 (7 years ago)
Size 137 KB
Signed by ROSTPEI LTD

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-04-22 21:39:50 (7 years ago); latest analysis 2024-12-13 23:01:13 (a year ago).

Digital signature

Signed by ROSTPEI LTD. 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.

uninstall.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2024-12-13 23:01:13 (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.

MD5: 4b697b715108786358c86fcf85e78807
Size: 137 KB
First Published: 2019-04-22 21:39:50 (7 years ago)
Latest Published: 2024-12-13 23:01:13 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-12-13 23:01:13 (a year ago)
Signed By: ROSTPEI LTD
Status: Valid

The signature on uninstall.exe 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.

%programfiles%

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

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

uninstall.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 0x000039e3
Image base 0x00400000

PE Sections:

Sections 6
Raw data 67584

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

.text 28672 bytes · 42.4% of section data
MD5 f569e353af0ed51bf4c216faa9bed4e7
.rdata 11264 bytes · 16.7% of section data
MD5 91eee43954e068e650f7b73a8b0e6915
.data 512 bytes · 0.8% of section data
MD5 db9f7acbf1c3ddfe255077b699955dfa
.ndata 0 bytes · 0.0% of section data
Uncommon name
MD5 00000000000000000000000000000000
.rsrc 23040 bytes · 34.1% of section data
MD5 f95d4f3efd226b815894f206423ea4dc
.reloc 4096 bytes · 6.1% of section data
MD5 4c4c939d204970e5bef09baa40d036ca

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 4b697b715108786358c86fcf85e78807.
  • 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.