cleanmypcservice.exe file report

MD5 ed518d22b06b5ab4816e5c2fa6474e21
Latest seen 2021-08-12 20:43:37 (4 years ago)
First seen 2017-11-03 18:07:58 (8 years ago)
Size 466 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 2017-11-03 18:07:58 (8 years ago); latest analysis 2021-08-12 20:43:37 (4 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.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

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 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: 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)
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.

%programfiles%\cleanmypc
%programfiles%
%programfiles%
%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.

CleanMyPCService.exe
cleanmypcservice.exe

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

46.7%
10.0%
6.7%
6.7%
6.7%
6.7%
3.3%
3.3%
3.3%
3.3%
3.3%

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.

Windows 10 50.0%
Windows 7 46.7%
Windows 8.1 3.3%

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.

cleanmypcservice.exe is identified as pe for 64 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 64
Image Base:
Entry Address:

.NET Info:

MVID: 57062feb-de06-4d09-b7d3-55364bba0983
Typelib ID: ee9c9431-c6a8-4e08-b042-0d420117e910

PE Sections:

Name Size of data MD5
.text 90112 2ee8e5bd3940491160f4d98ee416b201
.reloc 512 1d1bc87e2906095ca3d7b20d2419296d
.rsrc 372224 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.

More information: