GridinSoft Threat Intelligence

RegistryCleaner.dll file report

Under review File reputation report
MD5 22bc451f8f3be4941e8c1e6582eb3a39
Latest seen 2021-01-11 12:33:05 (5 years ago)
First seen 2020-01-04 19:36:33 (6 years ago)
Size 325 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-01-04 19:36:33 (6 years ago); latest analysis 2021-01-11 12:33:05 (5 years ago).

Publisher context

Product metadata: RegistryCleaner.dll.

Digital signature

Signed by Sorentio Systems 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.

RegistryCleaner.dll is a Windows file recorded in the ThreatInfo database. It is associated with RegistryCleaner.dll. The current detection status is Undefined, based on the latest analysis from 2021-01-11 12:33:05 (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.

Product Name: RegistryCleaner.dll
MD5: 22bc451f8f3be4941e8c1e6582eb3a39
Size: 325 KB
First Published: 2020-01-04 19:36:33 (6 years ago)
Latest Published: 2021-01-11 12:33:05 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-11 12:33:05 (5 years ago)
Signed By: Sorentio Systems Ltd
Status: Valid

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

%commondir%

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

Windows 10 50.0%
Windows XP 30.8%
Windows 7 19.2%

The most common operating system signal for RegistryCleaner.dll is Windows 10 with 50.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.

RegistryCleaner.dll 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 0x0002bb90
Image base 0x10000000

PE Sections:

Sections 5
Raw data 314880

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

.text 186368 bytes · 59.2% of section data
MD5 3ec784ba86386710141760f387dfc690
.rdata 96256 bytes · 30.6% of section data
MD5 d41eec500fc0b46e3ae4e4bf169ebd42
.data 4096 bytes · 1.3% of section data
MD5 e7c2507eeee5ac420d364bc91df11dc9
.rsrc 10752 bytes · 3.4% of section data
MD5 8c8e7033f1f2458412c2faa239bbccbb
.reloc 17408 bytes · 5.5% of section data
MD5 74c8f9e2a4d2e406abd6cf86ce0fb6b1

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 22bc451f8f3be4941e8c1e6582eb3a39.
  • 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.