GridinSoft Threat Intelligence

RCE.exe file report

Under review File reputation report
MD5 1970586b89169853e069c28ec2b1569e
Latest seen 2021-12-12 21:25:14 (4 years ago)
First seen 2021-12-12 21:25:14 (4 years ago)
Size 743 KB
Publisher 2.0
Signed by Qiwang Computer

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-12-12 21:25:14 (4 years ago); latest analysis 2021-12-12 21:25:14 (4 years ago).

Publisher context

Company metadata: 2.0. Product metadata: Registry Clean up Expert.

Digital signature

Signed by Qiwang Computer. 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.

RCE.exe is a Windows file recorded in the ThreatInfo database. It is associated with Registry Clean up Expert. The reported company name is 2.0. The current detection status is Undefined, based on the latest analysis from 2021-12-12 21:25:14 (4 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.

Product Name: Registry Clean up Expert
Company Name: 2.0
MD5: 1970586b89169853e069c28ec2b1569e
Size: 743 KB
First Published: 2021-12-12 21:25:14 (4 years ago)
Latest Published: 2021-12-12 21:25:14 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-12-12 21:25:14 (4 years ago)
Signed By: Qiwang Computer
Status: Valid

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

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

RCE.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 0x0002956a
Image base 0x00400000

PE Sections:

Sections 5
Raw data 754688

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

.text 254464 bytes · 33.7% of section data
MD5 03292a552785b550e34c6ff4b198d578
.rdata 63488 bytes · 8.4% of section data
MD5 b24ca7cb350753a953aa9e95dfed35a2
.data 11264 bytes · 1.5% of section data
MD5 f1469ae0711ed140c9105545dc70c4a0
.rsrc 387072 bytes · 51.3% of section data
MD5 1f93dfb54b8bbc967cd712ef6061317a
.reloc 38400 bytes · 5.1% of section data
MD5 8a62b1b52562769ca00fc15c3c88bff7

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 1970586b89169853e069c28ec2b1569e.
  • 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.