GridinSoft Threat Intelligence

CleanMyPC.Tools.exe file report

Under review File reputation report
MD5 3934145fcda9abfef5073d52abc039a8
Latest seen 2021-01-05 17:05:06 (5 years ago)
First seen 2018-11-06 10:18:22 (7 years ago)
Size 758 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:22 (7 years ago); latest analysis 2021-01-05 17:05:06 (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.

CleanMyPC.Tools.exe 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:05: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: CleanMyPC
Company Name: MacPaw Inc.
MD5: 3934145fcda9abfef5073d52abc039a8
Size: 758 KB
First Published: 2018-11-06 10:18:22 (7 years ago)
Latest Published: 2021-01-05 17:05:06 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-05 17:05:06 (5 years ago)
Signed By: MacPaw INC
Status: Valid

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

%programfiles%

ThreatInfo has observed CleanMyPC.Tools.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 71.8%
Windows 7 23.1%
Windows 8.1 5.1%

The most common operating system signal for CleanMyPC.Tools.exe is Windows 10 with 71.8% 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.

CleanMyPC.Tools.exe is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point
Image base

.NET Info:

MVID: 6ba26588-df77-45f4-a6d9-0d48d53b11e0

PE Sections:

Sections 3
Raw data 762368

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

.text 389632 bytes · 51.1% of section data
MD5 aabe38541b61749d0b479c9c62245d9a
.reloc 512 bytes · 0.1% of section data
MD5 632b582bf26b805fd5ad08d574964c4a
.rsrc 372224 bytes · 48.8% of section data
MD5 21389883ef7d8dff6c79fc3798fc8ef1

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 3934145fcda9abfef5073d52abc039a8.
  • 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.