GridinSoft Threat Intelligence

uninstall.exe file report

Under review File reputation report
MD5 b7754d6963c1ae4fa66f60605618fd7a
Latest seen 2025-07-24 23:01:13 (10 months ago)
First seen 2025-07-24 23:01:13 (10 months ago)
Size 91 KB
Publisher Conduit Ltd.
Signed by Conduit Ltd.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-07-24 23:01:13 (10 months ago); latest analysis 2025-07-24 23:01:13 (10 months ago).

Publisher context

Company metadata: Conduit Ltd.. Product metadata: Conduit Engine Uninstall.

Digital signature

Signed by Conduit 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. It is associated with Conduit Engine Uninstall. The reported company name is Conduit Ltd.. The current detection status is Undefined, based on the latest analysis from 2025-07-24 23:01:13 (10 months 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: Conduit Engine Uninstall
Company Name: Conduit Ltd.
MD5: b7754d6963c1ae4fa66f60605618fd7a
Size: 91 KB
First Published: 2025-07-24 23:01:13 (10 months ago)
Latest Published: 2025-07-24 23:01:13 (10 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-07-24 23:01:13 (10 months ago)
Signed By: Conduit 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 10 100.0%

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.

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 0x00003a7a
Image base 0x00400000

PE Sections:

Sections 5
Raw data 89600

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

.text 59904 bytes · 66.9% of section data
MD5 aee1c1e4795aa048b0886f6e979679f4
.rdata 12288 bytes · 13.7% of section data
MD5 f5702e4dc8688a69076a11c16d6e3c98
.data 5632 bytes · 6.3% of section data
MD5 1e775d0c7c53b7bb4746dd3df0a02822
.rsrc 4608 bytes · 5.1% of section data
MD5 6aec4f286a81a77d8c7a18ed0c983c13
.reloc 7168 bytes · 8.0% of section data
MD5 318d2c4df819027a0dc86f78d75d6997

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