GridinSoft Threat Intelligence

installer.exe file report

Under review File reputation report
MD5 e7e89c69629295a24c566022677b5c3b
Latest seen 2023-11-29 23:00:57 (2 years ago)
First seen 2023-11-29 23:00:57 (2 years ago)
Size 1 MB
Publisher Essentware
Signed by ESSENTWARE S.A.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-11-29 23:00:57 (2 years ago); latest analysis 2023-11-29 23:00:57 (2 years ago).

Publisher context

Company metadata: Essentware. Product metadata: PCKeeper Installer.

Digital signature

Signed by ESSENTWARE S.A.. 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.

installer.exe is a Windows file recorded in the ThreatInfo database. It is associated with PCKeeper Installer. The reported company name is Essentware. The current detection status is Undefined, based on the latest analysis from 2023-11-29 23:00:57 (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: PCKeeper Installer
Company Name: Essentware
MD5: e7e89c69629295a24c566022677b5c3b
Size: 1 MB
First Published: 2023-11-29 23:00:57 (2 years ago)
Latest Published: 2023-11-29 23:00:57 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-11-29 23:00:57 (2 years ago)
Signed By: ESSENTWARE S.A.
Status: Valid

The signature on installer.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.

%commonappdata%

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

installer.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 0x0004b53f
Image base 0x00400000

PE Sections:

Sections 5
Raw data 1407488

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

.text 428032 bytes · 30.4% of section data
MD5 985596248abf95257012013781987db2
.rdata 128000 bytes · 9.1% of section data
MD5 eea17892a418fa24a3f39028f72c88f1
.data 14848 bytes · 1.1% of section data
MD5 7746eef0c7c71c202ea9979f501cfc80
.rsrc 804864 bytes · 57.2% of section data
MD5 e5d4aeefad8d51fc80ba1a7569525025
.reloc 31744 bytes · 2.3% of section data
MD5 5806a1f26c13683bd84ed10fbbcf9dc3

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