GridinSoft Threat Intelligence

ReimageRepair (2016_03_12 17_38_49 UTC).exe threat report

Detected as PUP.Reimage File reputation report
MD5 72cb31555da5996b6dc008f2f6bcbbff
Latest seen 2025-11-27 23:00:37 (6 months ago)
First seen 2017-05-21 13:07:58 (8 years ago)
Size 753 KB
Publisher Reimage®
Product Reimage Repair
Signed by Reimage Limited

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
2025-11-27 23:00:37 (6 months ago)
File hash
72cb31555da5996b6dc008f2f6bcbbff
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as PUP.Reimage.

Timeline

First seen 2017-05-21 13:07:58 (8 years ago); latest analysis 2025-11-27 23:00:37 (6 months ago).

Publisher context

Company metadata: Reimage®. Product metadata: Reimage Repair.

Digital signature

Signed by Reimage Limited. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

File context

ReimageRepair (2016_03_12 17_38_49 UTC).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 2025-11-27 23:00:37 (6 months ago).

If ReimageRepair (2016_03_12 17_38_49 UTC).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: 72cb31555da5996b6dc008f2f6bcbbff
Size: 753 KB
First Published: 2017-05-21 13:07:58 (8 years ago)
Latest Published: 2025-11-27 23:00:37 (6 months ago)
Status: PUP.Reimage (on last analysis)
Analysis Date: 2025-11-27 23:00:37 (6 months ago)

Detection screenshot

ReimageRepair (2016_03_12 17_38_49 UTC).exe 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 ReimageRepair (2016_03_12 17_38_49 UTC).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:

%profile%\downloads
%mydoc%\programs\programs\compressed
%profile%\onedrive\bolig2015\anbud
%profile%\onedrive\bolig 2016\anbud
%profile%\onedrive\bolig 2016\bolig 2016\anbud
%profile%\ersian gulf\my documents\downloads
%programfiles%\reimage\reimage repair
%sysdrive%\downloads
%profile%\downloads\folder
%profile%\downloads\programs

ThreatInfo has observed ReimageRepair (2016_03_12 17_38_49 UTC).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:

57 observed names
ReimageRepair (2).exe ReimageRepair (1).exe ReimageRepair.exe $RISV4Y3.exe ReimageRepair(1).exe Windows 10 Naprawa.exe ReimageRepair (3).exe ReimageRepair (4).exe ReimageRepair(4).exe ReimageRepair(2).exe ReimageRepair(3).exe ReimageRepair_3.exe ReimageRepair_2.exe $RHFYMLE.exe ReimageRepair (11).exe ReimageRepair (9).exe ReimageRepair (6).exe ReimageRepair (5).exe ReimageRepair (12).exe ReimageRepair (10).exe ReimageRepair (8).exe ReimageRepair (7).exe $RVKB7P4.exe rvpmueatmuoywqszqaqwtuhkproenmik.back ReimageRepair (2016_01_18 14_16_02 UTC).exe ReimageRepair(1) (2016_01_18 14_16_02 UTC).exe ReimageRepair.exe.vir $RIC81Q1.exe A0160083.exe xp repair.exe ReimageRepair[2].exe A0397190.exe A0396552.exe A0397191.exe ReimageRepair(6).exe ReimageRepair(8).exe ReimageRepair(9).exe ReimageRepair(7).exe ReimageRepair(5).exe A0477281.exe A0477280.exe $R343XXD.exe ReimageRepair (17).exe ReimageRepair (13).exe ReimageRepair (14).exe ReimageRepair (2016_02_01 13_54_11 UTC).exe A0033280.exe A0017550.exe ReimageRepair (20).exe ReimageRepair (18).exe ReimageRepair (19).exe ReimageRepair (15).exe ReimageRepair (16).exe ReimageRepair (2016_04_11 18_18_49 UTC).exe $RESNSBU.exe $RI268IK.exe ReimageRepair (2016_03_12 17_38_49 UTC).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.

Geographic signal

Observed country distribution

ThreatInfo has seen ReimageRepair (2016_03_12 17_38_49 UTC).exe across 80 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Brazil
Share 6.7%
Low High activity

The strongest geographic signal for this file is Brazil with 6.7% 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 44.5%
Windows 7 38.1%
Windows 8.1 11.0%
Windows XP 2.9%
Windows Vista 1.8%
Windows 8 1.7%

The most common operating system signal for ReimageRepair (2016_03_12 17_38_49 UTC).exe is Windows 10 with 44.5% 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

ReimageRepair (2016_03_12 17_38_49 UTC).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 0x000038af
Image base 0x00400000

PE Sections:

Sections 6
Raw data 73216

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

.text 29696 bytes · 40.6% of section data
MD5 419d4e1be1ac35a5db9c47f553b27cea
.rdata 11264 bytes · 15.4% of section data
MD5 cca1ca3fbf99570f6de9b43ce767f368
.data 512 bytes · 0.7% of section data
MD5 77f0839f8ebea31040e462523e1c770e
.ndata 0 bytes · 0.0% of section data
Uncommon name
MD5 00000000000000000000000000000000
.rsrc 27648 bytes · 37.8% of section data
MD5 cf8466597fb9275b9aec02bf2e38ee9c
.reloc 4096 bytes · 5.6% of section data
MD5 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.

Report conclusion

GridinSoft detects this file as PUP.Reimage

This report identifies ReimageRepair (2016_03_12 17_38_49 UTC).exe by MD5 72cb31555da5996b6dc008f2f6bcbbff. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 72cb31555da5996b6dc008f2f6bcbbff.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found.