GridinSoft Threat Intelligence

SearchHelper.dll file report

Under review File reputation report
MD5 e4b78dec596b7676de7f6f1c9fc359cb
Latest seen 2023-07-28 23:52:33 (2 years ago)
First seen 2023-07-28 23:52:33 (2 years ago)
Size 233 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 2023-07-28 23:52:33 (2 years ago); latest analysis 2023-07-28 23:52:33 (2 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.

SearchHelper.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 2023-07-28 23:52:33 (2 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: e4b78dec596b7676de7f6f1c9fc359cb
Size: 233 KB
First Published: 2023-07-28 23:52:33 (2 years ago)
Latest Published: 2023-07-28 23:52:33 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-07-28 23:52:33 (2 years ago)
Signed By: MacPaw, Inc.
Status: Valid

The signature on SearchHelper.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 SearchHelper.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 100.0%

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

SearchHelper.dll is identified as pe for 32-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 32-bit
Subsystem Windows CUI
Entry point 0x00037d16
Image base 0x00400000

.NET Info:

MVID: 71be14eb-4f0c-403d-86e3-e1963ca75723
Typelib ID: 94844a3f-2bb7-4f8d-b875-abe1f745ae1d

PE Sections:

Sections 3
Raw data 222720

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

.text 220672 bytes · 99.1% of section data
MD5 dfac7b9ac42eecd8a769cb36a13f8cc9
.reloc 512 bytes · 0.2% of section data
MD5 fcb1a050c233311006e8c9dc3c465133
.rsrc 1536 bytes · 0.7% of section data
MD5 d1f546f46ced09c16f45e687c434d653

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