GridinSoft Threat Intelligence

FAT.dll file report

Under review File reputation report
MD5 2647d3343b667b6f4c2058de684e455f
Latest seen 2021-08-12 20:49:34 (4 years ago)
First seen 2017-11-03 18:07:58 (8 years ago)
Size 71 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:58 (8 years ago); latest analysis 2021-08-12 20:49:34 (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.

FAT.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:49:34 (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: 2647d3343b667b6f4c2058de684e455f
Size: 71 KB
First Published: 2017-11-03 18:07:58 (8 years ago)
Latest Published: 2021-08-12 20:49:34 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-08-12 20:49:34 (4 years ago)
Signed By: MacPaw INC
Status: Valid

The signature on FAT.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 FAT.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 54.5%
Windows 10 42.4%
Windows 8.1 3.0%

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

FAT.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 0x00001780
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 58368

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

.text 34304 bytes · 58.8% of section data
MD5 1c1d2186e8b8988ef8cbd04b04dba96a
.rdata 14848 bytes · 25.4% of section data
MD5 052541041088b120641270927535ab43
.data 5120 bytes · 8.8% of section data
MD5 ccb98f0ce6c11b1939ac76809a75fc8a
.pdata 2560 bytes · 4.4% of section data
MD5 8fcc2a8437ae2e741ee4d58fad963c02
.rsrc 512 bytes · 0.9% of section data
MD5 b8ee9ba7f6e9f572f1101ec66cb50a71
.reloc 1024 bytes · 1.8% of section data
MD5 4993206ca2b4900bf55ff8e5007ea9df

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 2647d3343b667b6f4c2058de684e455f.
  • 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.