GridinSoft Threat Intelligence

dnrepairer.exe file report

Under review File reputation report
MD5 ec6ec990d70c7d53ec494f046865fada
Latest seen 2025-01-29 23:01:04 (a year ago)
First seen 2024-07-06 23:05:00 (2 years ago)
Size 41 MB
Publisher XZ
Product rp

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-07-06 23:05:00 (2 years ago); latest analysis 2025-01-29 23:01:04 (a year ago).

Publisher context

Company metadata: XZ. Product metadata: rp.

Digital signature

Signed by Shanghai Baizhi Network Technology Co., Ltd.. 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.

dnrepairer.exe is a Windows file recorded in the ThreatInfo database. It is associated with rp. The reported company name is XZ. The current detection status is Undefined, based on the latest analysis from 2025-01-29 23:01:04 (a year 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: rp
Company Name: XZ
MD5: ec6ec990d70c7d53ec494f046865fada
Size: 41 MB
First Published: 2024-07-06 23:05:00 (2 years ago)
Latest Published: 2025-01-29 23:01:04 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-01-29 23:01:04 (a year ago)

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

%sysdrive%\ldplayer

ThreatInfo has observed dnrepairer.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 dnrepairer.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.

dnrepairer.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 0x00091a07
Image base 0x00400000

PE Sections:

Sections 5
Raw data 43941376

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

.text 632320 bytes · 1.4% of section data
MD5 59c9bd87e1b752be7cbf2a80113014d5
.rdata 171520 bytes · 0.4% of section data
MD5 6a096edddb76324db992666e184967b7
.data 13312 bytes · 0.0% of section data
MD5 6420646b7678667e9295de1c0515205a
.rsrc 43085312 bytes · 98.1% of section data
Large raw data
MD5 606909c97707e07c8976c0cdeaa9f809
.reloc 38912 bytes · 0.1% of section data
MD5 a9aa99de04f4bcf461b341f2f7e53d98

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