GridinSoft Threat Intelligence

pubeforeuninstall.exe file report

Under review File reputation report
MD5 f29ea9780bec3d34f8bb9f427b786c42
Latest seen 2021-01-11 23:27:58 (5 years ago)
First seen 2020-06-26 20:01:23 (5 years ago)
Size 1 MB
Product PerfectUpdater

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-06-26 20:01:23 (5 years ago); latest analysis 2021-01-11 23:27:58 (5 years ago).

Publisher context

Company metadata: Raxco Software, Inc.. Product metadata: PerfectUpdater.

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.

pubeforeuninstall.exe is a Windows file recorded in the ThreatInfo database. It is associated with PerfectUpdater. The reported company name is Raxco Software, Inc.. The current detection status is Undefined, based on the latest analysis from 2021-01-11 23:27:58 (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.

Product Name: PerfectUpdater
Company Name: Raxco Software, Inc.
MD5: f29ea9780bec3d34f8bb9f427b786c42
Size: 1 MB
First Published: 2020-06-26 20:01:23 (5 years ago)
Latest Published: 2021-01-11 23:27:58 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-11 23:27:58 (5 years ago)
Signed By: Raxco Software, Inc.
Status: Valid

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

pubeforeuninstall.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 0x00027514
Image base 0x00400000

PE Sections:

Sections 4
Raw data 1097216

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

.text 231936 bytes · 21.1% of section data
MD5 50703d5d9a1c2acb36a7465da85093b0
.rdata 58368 bytes · 5.3% of section data
MD5 e22de6d57f421802b7393b470c65eefc
.data 16896 bytes · 1.5% of section data
MD5 3371e39c8e9385baede38f527ebdeb72
.rsrc 790016 bytes · 72.0% of section data
MD5 58a98606d1d49be78119f599083f1e0b

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