GridinSoft Threat Intelligence

CleanMyPCShell.dll file report

Under review File reputation report
MD5 b61be8f50721d76fdd45b4dae9178578
Latest seen 2021-01-05 17:06:34 (5 years ago)
First seen 2018-11-06 10:18:14 (7 years ago)
Size 1009 KB
Publisher MacPaw Inc.
Product CleanMyPC
Signed by MacPaw INC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-11-06 10:18:14 (7 years ago); latest analysis 2021-01-05 17:06:34 (5 years ago).

Publisher context

Company metadata: MacPaw Inc.. Product metadata: CleanMyPC.

Digital signature

Signed by MacPaw INC. 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.

CleanMyPCShell.dll is a Windows file recorded in the ThreatInfo database. It is associated with CleanMyPC. The reported company name is MacPaw Inc.. The current detection status is Undefined, based on the latest analysis from 2021-01-05 17:06:34 (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: CleanMyPC
Company Name: MacPaw Inc.
MD5: b61be8f50721d76fdd45b4dae9178578
Size: 1009 KB
First Published: 2018-11-06 10:18:14 (7 years ago)
Latest Published: 2021-01-05 17:06:34 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-05 17:06:34 (5 years ago)
Signed By: MacPaw INC
Status: Valid

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

%programfiles%

ThreatInfo has observed CleanMyPCShell.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 67.4%
Windows 7 27.9%
Windows 8.1 4.7%

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

CleanMyPCShell.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point
Image base

.NET Info:

MVID: 772ff8be-37db-4a94-987d-aac0af2ccfcd
Typelib ID: ff2991dc-25ce-4f4a-a1a1-ff570d931c3c

PE Sections:

Sections 2
Raw data 1019392

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

.text 972800 bytes · 95.4% of section data
MD5 64449b4154b70b80461a6e7b45920f97
.rsrc 46592 bytes · 4.6% of section data
MD5 f065be6b8f31ea41aaa214914e416de1

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