GridinSoft Threat Intelligence

Uninstall.exe file report

Under review File reputation report
MD5 f8853834f401a8f7e62e50a4b1e70d30
Latest seen 2024-09-27 23:06:45 (2 years ago)
First seen 2021-01-06 13:43:11 (5 years ago)
Size 108 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-06 13:43:11 (5 years ago); latest analysis 2024-09-27 23:06:45 (2 years ago).

Publisher context

Company metadata: DriverPack Solution. Product metadata: DriverPack Cloud.

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. It is associated with DriverPack Cloud. The reported company name is DriverPack Solution. The current detection status is Undefined, based on the latest analysis from 2024-09-27 23:06:45 (2 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.

Product Name: DriverPack Cloud
Company Name: DriverPack Solution
MD5: f8853834f401a8f7e62e50a4b1e70d30
Size: 108 KB
First Published: 2021-01-06 13:43:11 (5 years ago)
Latest Published: 2024-09-27 23:06:45 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-09-27 23:06:45 (2 years ago)
%appdata%\drpsu
%desktop%\oem\appdata\roaming\drpsu

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 10 66.7%
Windows 7 33.3%

The most common operating system signal for Uninstall.exe is Windows 10 with 66.7% 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 0x0000433c
Image base 0x00400000

PE Sections:

Sections 7
Raw data 103936

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

.text 36864 bytes · 35.5% of section data
MD5 f71817a41c2b4fd6e049a4cc6fc8ee39
.data 512 bytes · 0.5% of section data
MD5 dc5ad88ad7a5abfbb93f86af0de9f73f
.rdata 29696 bytes · 28.6% of section data
MD5 7eb48fb024a95830fbb6c6258f17c88c
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 5120 bytes · 4.9% of section data
MD5 64e1f11bb3a2df037fb0363fdd40b645
.ndata 512 bytes · 0.5% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 31232 bytes · 30.0% of section data
MD5 939c0ff6fbbbae33cb879684a0972e30

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