GridinSoft Threat Intelligence
CleanMyPCService.exe file report
Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2017-11-03 18:07:58 (8 years ago); latest analysis 2021-08-12 20:43:37 (4 years ago).
Company metadata: MacPaw Inc.. Product metadata: CleanMyPC.
Signed by MacPaw INC. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
CleanMyPCService.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-08-12 20:43:37 (4 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
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.
File Details
| Product Name: | CleanMyPC |
| Company Name: | MacPaw Inc. |
| MD5: | ed518d22b06b5ab4816e5c2fa6474e21 |
| Size: | 466 KB |
| First Published: | 2017-11-03 18:07:58 (8 years ago) |
| Latest Published: | 2021-08-12 20:43:37 (4 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-08-12 20:43:37 (4 years ago) |
Overview
| Signed By: | MacPaw INC |
| Status: | Valid |
The signature on CleanMyPCService.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.
Common Places:
| %programfiles%\cleanmypc |
| %programfiles% |
ThreatInfo has observed CleanMyPCService.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.
Geographic signal
Observed country distribution
ThreatInfo has seen CleanMyPCService.exe across 11 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 46.7% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for CleanMyPCService.exe 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.
Analysis
CleanMyPCService.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.
.NET Info:
| MVID: | 57062feb-de06-4d09-b7d3-55364bba0983 |
| Typelib ID: | ee9c9431-c6a8-4e08-b042-0d420117e910 |
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
2ee8e5bd3940491160f4d98ee416b201
1d1bc87e2906095ca3d7b20d2419296d
6b86de5f5bac2e350f769397e14a0f0d
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.