GridinSoft Threat Intelligence

unins000.exe file report

Under review File reputation report
MD5 18b065255a6291696bf3e03530bf7d1d
Latest seen 2025-01-06 23:01:09 (a year ago)
First seen 2025-01-06 23:01:09 (a year ago)
Size 1 MB
Signed by Ideakee Inc

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-01-06 23:01:09 (a year ago); latest analysis 2025-01-06 23:01:09 (a year ago).

Digital signature

Signed by Ideakee 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 2025-01-06 23:01:09 (a year 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: 18b065255a6291696bf3e03530bf7d1d
Size: 1 MB
First Published: 2025-01-06 23:01:09 (a year ago)
Latest Published: 2025-01-06 23:01:09 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-01-06 23:01:09 (a year ago)
Signed By: Ideakee 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%

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

PE Sections:

Sections 8
Raw data 1185280

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

.text 1036288 bytes · 87.4% of section data
MD5 f07528ad00ef563f25b078973ab74526
.itext 5120 bytes · 0.4% of section data
Uncommon name
MD5 ee1623fb4bfbf53c6d7a796fee40c5b0
.data 12800 bytes · 1.1% of section data
MD5 a563250498abf40b0297b5b019d7ed90
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 14336 bytes · 1.2% of section data
MD5 81c7429c9619a00840c630c4427dc350
.tls 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 bytes · 0.0% of section data
MD5 543246b7273241d8e173a5d9dcb01e12
.rsrc 116224 bytes · 9.8% of section data
MD5 4fe53ee8e96dd84709c6bb1b96cbce19

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 18b065255a6291696bf3e03530bf7d1d.
  • 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.