GridinSoft Threat Intelligence

MFT.dll file report

Under review File reputation report
MD5 18e23aee770cf14d9973c08eb54c5d6e
Latest seen 2021-08-12 20:51:23 (4 years ago)
First seen 2017-11-03 18:07:53 (8 years ago)
Size 181 KB
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:53 (8 years ago); latest analysis 2021-08-12 20:51:23 (4 years ago).

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.

MFT.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-08-12 20:51:23 (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.

MD5: 18e23aee770cf14d9973c08eb54c5d6e
Size: 181 KB
First Published: 2017-11-03 18:07:53 (8 years ago)
Latest Published: 2021-08-12 20:51:23 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-08-12 20:51:23 (4 years ago)
Signed By: MacPaw INC
Status: Valid

The signature on MFT.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 MFT.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 55.9%
Windows 10 41.2%
Windows 8.1 2.9%

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

MFT.dll 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 0x000038c8
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 170496

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

.text 128512 bytes · 75.4% of section data
MD5 43bfe755d8df81ef16c9bf312351afd8
.rdata 27648 bytes · 16.2% of section data
MD5 ad768b47cec362e989c18f6f313a343d
.data 5120 bytes · 3.0% of section data
MD5 6bbf3f675c2fb846bed90d90d313703b
.pdata 7168 bytes · 4.2% of section data
MD5 15c56b1bbd176670945cb8d8d3013f46
.rsrc 512 bytes · 0.3% of section data
MD5 d9b1a56638a7cb021710f1053064a086
.reloc 1536 bytes · 0.9% of section data
MD5 13ea94253dc6682c1c5af6792e34249c

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 18e23aee770cf14d9973c08eb54c5d6e.
  • 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.