GridinSoft Threat Intelligence

smdm.dll file report

Under review File reputation report
MD5 154bca4d796846ba91f83c8f5da0f746
Latest seen 2021-08-12 20:57:37 (4 years ago)
First seen 2017-11-03 18:07:57 (8 years ago)
Size 57 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:57 (8 years ago); latest analysis 2021-08-12 20:57: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.

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.

smdm.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-08-12 20:57: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: 154bca4d796846ba91f83c8f5da0f746
Size: 57 KB
First Published: 2017-11-03 18:07:57 (8 years ago)
Latest Published: 2021-08-12 20:57:37 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-08-12 20:57:37 (4 years ago)
Signed By: MacPaw INC
Status: Valid

The signature on smdm.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%\cleanmypc
%programfiles%

ThreatInfo has observed smdm.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 7 51.6%
Windows 10 45.2%
Windows 8.1 3.2%

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

smdm.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: b2efa573-9894-461f-af7c-c4537890b151
Typelib ID: 68694739-53eb-4baf-8024-36e0d1b90313

PE Sections:

Sections 3
Raw data 44544

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

.text 43008 bytes · 96.6% of section data
MD5 116292bb1d7823aea8d8ef10d57a716e
.reloc 512 bytes · 1.1% of section data
MD5 6b22d18fc923b4d873876b8c95d31d31
.rsrc 1024 bytes · 2.3% of section data
MD5 fd3770fcac81ded7e1de76f595d94723

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 154bca4d796846ba91f83c8f5da0f746.
  • 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.