GridinSoft Threat Intelligence

unins000.exe file report

Under review File reputation report
MD5 d1e6594e07cde3fd71ff068f65e3fa87
Latest seen 2021-01-11 23:28:12 (5 years ago)
First seen 2020-06-26 20:38:13 (5 years ago)
Size 891 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-06-26 20:38:13 (5 years ago); latest analysis 2021-01-11 23:28:12 (5 years ago).

Digital signature

Signed by Raxco Software, Inc.. 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.

unins000.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-01-11 23:28:12 (5 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: d1e6594e07cde3fd71ff068f65e3fa87
Size: 891 KB
First Published: 2020-06-26 20:38:13 (5 years ago)
Latest Published: 2021-01-11 23:28:12 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-11 23:28:12 (5 years ago)
Signed By: Raxco Software, Inc.
Status: Valid

The signature on unins000.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%\raxco

ThreatInfo has observed unins000.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 unins000.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.

unins000.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 0x0009a490
Image base 0x00400000

PE Sections:

Sections 8
Raw data 897024

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

CODE 628736 bytes · 70.1% of section data
MD5 2a74b7962f783f54fcdef0832526ed44
DATA 4608 bytes · 0.5% of section data
MD5 cf3a4c5c7e4748476aa128c63239a178
BSS 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.idata 10240 bytes · 1.1% of section data
MD5 00f948516778e0a99656590a844e7e06
.tls 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.rdata 512 bytes · 0.1% of section data
MD5 fd99d829f5d6b93951f88b241902df93
.reloc 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.rsrc 252928 bytes · 28.2% of section data
MD5 dc6dfaf0f91b407740727227286744bf

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