GridinSoft Threat Intelligence

RecycleCleaner.dll file report

Under review File reputation report
MD5 1d956c3ee72419237181e3a5aacec409
Latest seen 2021-01-11 12:26:06 (5 years ago)
First seen 2020-01-04 19:38:22 (6 years ago)
Size 126 KB
Product RecycleCleaner

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-01-04 19:38:22 (6 years ago); latest analysis 2021-01-11 12:26:06 (5 years ago).

Publisher context

Product metadata: RecycleCleaner.

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.

RecycleCleaner.dll is a Windows file recorded in the ThreatInfo database. It is associated with RecycleCleaner. The current detection status is Undefined, based on the latest analysis from 2021-01-11 12:26:06 (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: RecycleCleaner
MD5: 1d956c3ee72419237181e3a5aacec409
Size: 126 KB
First Published: 2020-01-04 19:38:22 (6 years ago)
Latest Published: 2021-01-11 12:26:06 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-11 12:26:06 (5 years ago)
Signed By: Sorentio Systems Ltd
Status: Valid

The signature on RecycleCleaner.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 RecycleCleaner.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 45.0%
Windows XP 40.0%
Windows 7 15.0%

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

RecycleCleaner.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 0x0000fc32
Image base 0x10000000

PE Sections:

Sections 5
Raw data 103424

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

.text 65024 bytes · 62.9% of section data
MD5 0892971928b9b29e34546be74d7e5818
.rdata 20992 bytes · 20.3% of section data
MD5 b6253bfb690e5fc72fb42d1084dca6b8
.data 4608 bytes · 4.5% of section data
MD5 e63032d686bcec18c5ab0a22edeb5a3f
.rsrc 6144 bytes · 5.9% of section data
MD5 316226f5f9a58b1aa43fcdb536e345fc
.reloc 6656 bytes · 6.4% of section data
MD5 9d1c7d981fde89066db2dcea25a549f7

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 1d956c3ee72419237181e3a5aacec409.
  • 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.