GridinSoft Threat Intelligence
REI_Engine.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-06-13 22:05:50 (8 years ago); latest analysis 2021-01-14 09:17:04 (5 years ago).
Company metadata: Reimage. Product metadata: Reimage ActiveX.
Signed by Reimage Limited. 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
REI_Engine.dll is a Windows file recorded in the ThreatInfo database. It is associated with Reimage ActiveX. The reported company name is Reimage. The current detection status is Undefined, based on the latest analysis from 2021-01-14 09:17:04 (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.
File Details
| Product Name: | Reimage ActiveX |
| Company Name: | Reimage |
| MD5: | f1dc12320020a0d21f3c4edeaf34f26e |
| Size: | 10 MB |
| First Published: | 2017-06-13 22:05:50 (8 years ago) |
| Latest Published: | 2021-01-14 09:17:04 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-01-14 09:17:04 (5 years ago) |
Overview
| Signed By: | Reimage Limited |
| Status: | Valid |
The signature on REI_Engine.dll 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\reimage repair |
| %sysdrive%\adwcleaner\quarantine\files\opnwitpgoamhgbslotbpicizbixifvfb |
| %programfiles%\reimage |
| %sysdrive%\adwcleaner\quarantine\rqf69azbla |
| %sysdrive%\adwcleaner\quarantine\files\xlyjgsetxfpnvoxtddawwphywtuinyrd |
ThreatInfo has observed REI_Engine.dll 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 REI_Engine.dll across 14 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 21.7% 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 REI_Engine.dll is Windows 10 with 60.9% 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
REI_Engine.dll is identified as pe for 64-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.
e2c131c066dbb622fdd9ceac4ab00da1
4a3821d479b1aa988fcbbf06e149ef17
b1a474036c339c50fbe0d4b2c6c0a09f
c4afe3aa6433a797ac1ff08b942ed80b
557fd346308f6b38a6dd9dc41a6f534b
709856458e73182f47466ff0d84babad
7d3191b496965269120aa39906aafe84
77e61fca282d120290ca507b7ba24f51
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.