GridinSoft Threat Intelligence
Uninstall.exe file report
Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2020-01-07 15:42:49 (6 years ago); latest analysis 2021-06-11 20:18:57 (4 years ago).
Company metadata: SweetLabs,Inc.. Product metadata: App Explorer.
Signed by SweetLabs Inc.. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
Uninstall.exe is a Windows file recorded in the ThreatInfo database. It is associated with App Explorer. The reported company name is SweetLabs,Inc.. The current detection status is Undefined, based on the latest analysis from 2021-06-11 20:18:57 (4 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
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.
File Details
| Product Name: | App Explorer |
| Company Name: | SweetLabs,Inc. |
| MD5: | cc0b93e69510d27215d889617eef763e |
| Size: | 1 MB |
| First Published: | 2020-01-07 15:42:49 (6 years ago) |
| Latest Published: | 2021-06-11 20:18:57 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-06-11 20:18:57 (4 years ago) |
Overview
| Signed By: | SweetLabs Inc. |
| 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.
Common Places:
| %localappdata% |
| %temp% |
| %sysdrive%\adwcleaner\quarantine\v1\20200502.055421\1 |
| %sysdrive%\windows.old\users\al-wafi\appdata\local |
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.
Geographic signal
Observed country distribution
ThreatInfo has seen Uninstall.exe across 17 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is India with 16.7% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for Uninstall.exe is Windows 10 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.
Analysis
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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
bfe2b726d49cbd922b87bad5eea65e61
d45dcba8ca646543f7e339e20089687e
8575fc5e872ca789611c386779287649
00000000000000000000000000000000
e3568bcd1db537cd5690f1cd267a7b12
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.