GridinSoft Threat Intelligence
ReiGuard.exe file report
Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2020-04-04 19:12:05 (6 years ago); latest analysis 2021-03-15 21:51:47 (5 years ago).
Company metadata: Reimage?. Product metadata: Reimage Real Time Protection.
Signed by Reimage LTD.. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
ReiGuard.exe is a Windows file recorded in the ThreatInfo database. It is associated with Reimage Real Time Protection. The reported company name is Reimage?. The current detection status is Undefined, based on the latest analysis from 2021-03-15 21:51:47 (5 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
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.
File Details
| Product Name: | Reimage Real Time Protection |
| Company Name: | Reimage? |
| MD5: | 2f9d6589b8c8e42bf0d8c3db5784a364 |
| Size: | 6 MB |
| First Published: | 2020-04-04 19:12:05 (6 years ago) |
| Latest Published: | 2021-03-15 21:51:47 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-03-15 21:51:47 (5 years ago) |
Overview
| Signed By: | Reimage LTD. |
| Status: | Valid |
The signature on ReiGuard.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.
Common Places:
| %programfiles%\reimage |
| %sysdrive%\adwcleaner\quarantine\files\bxfsvzmqncwuzqkisqrlbcwolmntiuic |
ThreatInfo has observed ReiGuard.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.
Geographic signal
Observed country distribution
ThreatInfo has seen ReiGuard.exe across 23 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Egypt with 17.9% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for ReiGuard.exe is Windows 7 with 53.3% 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.
Analysis
ReiGuard.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
57e899c90331b9b4361aebff1b788f78
fe48076cff98f53e4e49055467650373
3554e8569507d282dc20d402822bb0af
17cbaa3ecb7e207e844e5a95b000770c
0f97916bf5e871fe86caa066dc8fc398
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.