GridinSoft Threat Intelligence

uninstall.exe file report

Clean record File reputation report
MD5 4aa61184bf09bd3cd37fb7b2de3f86ea
Latest seen 2021-03-05 04:43:55 (5 years ago)
First seen 2021-03-05 04:43:55 (5 years ago)
Size 8 MB
Publisher Comodo
Product Comodo Dragon

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-03-05 04:43:55 (5 years ago); latest analysis 2021-03-05 04:43:55 (5 years ago).

Publisher context

Company metadata: Comodo. Product metadata: Comodo Dragon.

Digital signature

Signed by Comodo Security Solutions. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

uninstall.exe is a Windows file recorded in the ThreatInfo database. It is associated with Comodo Dragon. The reported company name is Comodo. The current detection status is Clean, based on the latest analysis from 2021-03-05 04:43:55 (5 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Comodo Dragon
Company Name: Comodo
MD5: 4aa61184bf09bd3cd37fb7b2de3f86ea
Size: 8 MB
First Published: 2021-03-05 04:43:55 (5 years ago)
Latest Published: 2021-03-05 04:43:55 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-03-05 04:43:55 (5 years ago)
Signed By: Comodo Security Solutions
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%\comodo

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

PE Sections:

Sections 5
Raw data 104448

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

.text 24576 bytes · 23.5% of section data
MD5 b46cdd345517700b251a2cb55d7f9fff
.rdata 5120 bytes · 4.9% of section data
MD5 848ecd58951d0a4cfe8ec8cfce6b20d1
.data 1536 bytes · 1.5% of section data
MD5 3953dbb7217e7539ee75e90871f7aef9
.ndata 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.rsrc 73216 bytes · 70.1% of section data
MD5 66cffcb6da91982e765bc63152734db3

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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