$RTNLAJD.exe threat report
ThreatInfo file report
$RTNLAJD.exe
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as PUP.Reimage. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.
- Detection name
- PUP.Reimage
- Recommended action
- Scan and remove
- Last analysis
- 2022-08-08 23:39:54 (3 years ago)
- File hash
- 2e5d49928703ea786e5bf3e923cc83e3
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as PUP.Reimage.
First seen 2017-05-25 13:07:49 (8 years ago); latest analysis 2022-08-08 23:39:54 (3 years ago).
Company metadata: Reimage. Product metadata: Reimage Repair.
Signed by Reimage Limited. The signature is reported as valid, but signed files can still be bundled or abused.
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
- Compare the MD5 above with the file found on the device.
- Check whether the file appears in the observed locations or under one of the alternate names.
- Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.
File context
$RTNLAJD.exe is a Windows file recorded in the ThreatInfo database. It is associated with Reimage Repair. The reported company name is Reimage. The current detection status is PUP.Reimage, based on the latest analysis from 2022-08-08 23:39:54 (3 years ago).
If $RTNLAJD.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as PUP.Reimage.
File Details
| Product Name: | Reimage Repair |
| Company Name: | Reimage |
| MD5: | 2e5d49928703ea786e5bf3e923cc83e3 |
| Size: | 590 KB |
| First Published: | 2017-05-25 13:07:49 (8 years ago) |
| Latest Published: | 2022-08-08 23:39:54 (3 years ago) |
| Status: | PUP.Reimage (on last analysis) | |
| Analysis Date: | 2022-08-08 23:39:54 (3 years ago) |
Detection screenshot
The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.
Overview
| Signed By: | Reimage Limited |
| Status: | Valid |
The signature on $RTNLAJD.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\reimage repair |
| %localappdata%\microsoft\windows\inetcache\ie\57f4vzzn |
| %profile%\downloads |
| %sysdrive%\adwcleaner\quarantine\files\tsbjtfnfyaaqygrroqbfbnwchghfchtw\reimage repair |
| %profile%\downloads\reimagerepair.rar |
| %localappdata%\microsoft\windows\temporary internet files\content.ie5\rzsydy39 |
| %localappdata%\microsoft\windows\temporary internet files\content.ie5\b4bull0n |
| %profile%\downloads\programs |
| %sysdrive%\adwcleaner\quarantine\files\ywhqyzdyvjmitguiczwgiuwxeqdnzunl\reimage repair |
| %desktop%\reimagen 2017 |
ThreatInfo has observed $RTNLAJD.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.
File Names:
| ReimageRepair.exe |
| ReimageRepair[1].exe |
| ReimageRepair (1).exe |
| ReimageRepair (2).exe |
| ReimageRepair (7).exe |
| ReimageRepair (6).exe |
| ReimageRepair (3).exe |
| ReimageRepair (4).exe |
| ReimageRepair_2.exe |
| ReimageRepair(6).exe |
| ReimageRepair(5).exe |
| ReimageRepair(4).exe |
| ReimageRepair(8).exe |
| ReimageRepair(3).exe |
| ReimageRepair(7).exe |
| ReimageRepair(2).exe |
| ReimageRepair(5) (2017_06_30 06_43_40 UTC).exe |
| ReimageRepair(2) (2017_06_30 06_43_40 UTC).exe |
| ReimageRepair (1) (2017_06_30 06_43_40 UTC).exe |
| ReimageRepair(4) (2017_06_30 06_43_40 UTC).exe |
| ReimageRepair(7) (2017_06_30 06_43_40 UTC).exe |
| ReimageRepair(3) (2017_06_30 06_43_40 UTC).exe |
| ReimageRepair(6) (2017_06_30 06_43_40 UTC).exe |
| ReimageRepair(8) (2017_06_30 06_43_40 UTC).exe |
| ReimageRepair (5).exe |
| ReimageRepair_3.exe |
| $R7OY3AM.exe |
| $R3VU5VT.exe |
| $R7QXIUK.exe |
| ReimageRepair (2017_11_20 10_32_43 UTC).exe |
| ReimageRepair (1) (2017_11_20 10_32_43 UTC).exe |
| ReimageRepair(1).exe |
| ReimageRepair1849.exe |
| $RTNLAJD.exe |
This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.
Geography:
| 18.6% | ||
| 14.6% | ||
| 9.3% | ||
| 6.5% | ||
| 5.3% | ||
| 4.0% | ||
| 3.6% | ||
| 3.2% | ||
| 3.2% | ||
| 3.2% | ||
| 3.2% | ||
| 2.8% | ||
| 2.0% | ||
| 2.0% | ||
| 1.6% | ||
| 1.6% | ||
| 1.6% | ||
| 1.6% | ||
| 1.2% | ||
| 1.2% | ||
| 0.8% | ||
| 0.8% | ||
| 0.8% | ||
| 0.8% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% |
The strongest geographic signal for this file is Germany with 18.6% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
| Windows 10 | 64.8% | |
| Windows 7 | 26.3% | |
| Windows 8.1 | 6.5% | |
| Windows XP | 2.0% | |
| Windows 8 | 0.4% |
The most common operating system signal for $RTNLAJD.exe is Windows 10 with 64.8% 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
$RTNLAJD.exe is identified as pe for 32 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.
| Subsystem: | Windows GUI |
| PE Type: | pe |
| OS Bitness: | 32 |
| Image Base: | 0x00400000 |
| Entry Address: | 0x000039e3 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 28672 | f569e353af0ed51bf4c216faa9bed4e7 |
| .rdata | 11264 | 91eee43954e068e650f7b73a8b0e6915 |
| .data | 512 | db9f7acbf1c3ddfe255077b699955dfa |
| .ndata | 0 | 00000000000000000000000000000000 |
| .rsrc | 27648 | 4bd159f8b797bb96f110a175455c366e |
| .reloc | 4096 | b0c639c0ead6692630a3f20353ddb2ba |
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.
More information:
