GridinSoft Threat Intelligence

uninstall.exe file report

Under review File reputation report
MD5 ade865c179234b97ae4ccb45adaaca0f
Latest seen 2022-07-28 23:55:11 (3 years ago)
First seen 2020-08-31 12:19:55 (5 years ago)
Size 124 KB
Signed by ROSTPAY LTD

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-08-31 12:19:55 (5 years ago); latest analysis 2022-07-28 23:55:11 (3 years ago).

Digital signature

Signed by ROSTPAY 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 2022-07-28 23:55:11 (3 years 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: ade865c179234b97ae4ccb45adaaca0f
Size: 124 KB
First Published: 2020-08-31 12:19:55 (5 years ago)
Latest Published: 2022-07-28 23:55:11 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-07-28 23:55:11 (3 years ago)
Signed By: ROSTPAY 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%\carambis

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 7 75.0%
Windows 10 25.0%

The most common operating system signal for uninstall.exe is Windows 7 with 75.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 0x0000350d
Image base 0x00400000

PE Sections:

Sections 5
Raw data 60928

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

.text 26112 bytes · 42.9% of section data
MD5 126ee0e9857c3dd1da49a87c83cf68a5
.rdata 5120 bytes · 8.4% of section data
MD5 c0b38cbc803107c82ebed5a1c15c1ffa
.data 1536 bytes · 2.5% of section data
MD5 9e607f846cdaf2d9c5b82d7d05f433ac
.ndata 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.rsrc 28160 bytes · 46.2% of section data
MD5 7d1e1cf6b965f9ad122a4f49ef4ba54f

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