GridinSoft Threat Intelligence

EmptyFolderCleaner.dll file report

Under review File reputation report
MD5 0ebb789e56483e84927c3a536adbfd3e
Latest seen 2021-01-11 12:15:23 (5 years ago)
First seen 2020-01-04 19:37:03 (6 years ago)
Size 124 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-01-04 19:37:03 (6 years ago); latest analysis 2021-01-11 12:15:23 (5 years ago).

Publisher context

Product metadata: EmptyFolderCleaner.

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.

EmptyFolderCleaner.dll is a Windows file recorded in the ThreatInfo database. It is associated with EmptyFolderCleaner. The current detection status is Undefined, based on the latest analysis from 2021-01-11 12:15:23 (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: EmptyFolderCleaner
MD5: 0ebb789e56483e84927c3a536adbfd3e
Size: 124 KB
First Published: 2020-01-04 19:37:03 (6 years ago)
Latest Published: 2021-01-11 12:15:23 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-11 12:15:23 (5 years ago)
Signed By: Sorentio Systems Ltd
Status: Valid

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

EmptyFolderCleaner.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 0x0000f4ab
Image base 0x10000000

PE Sections:

Sections 5
Raw data 101376

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

.text 63488 bytes · 62.6% of section data
MD5 2d5013c3a6a0b17218dc86a6986103fc
.rdata 20480 bytes · 20.2% of section data
MD5 37694afa0de9c6436bc80c9b40e73905
.data 4608 bytes · 4.5% of section data
MD5 aa80f3d4c68dd08625f83969ff756b09
.rsrc 6144 bytes · 6.1% of section data
MD5 944eb19c381f20d4e316af638cdc6ef9
.reloc 6656 bytes · 6.6% of section data
MD5 4175fee3c056c5fe2dba54499bbb0d83

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 0ebb789e56483e84927c3a536adbfd3e.
  • 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.