GridinSoft Threat Intelligence

FreeImage.dll file report

Under review File reputation report
MD5 92ca0724dc0147da0e62f9971bd03e98
Latest seen 2025-06-04 23:01:00 (a year ago)
First seen 2025-06-04 23:01:00 (a year ago)
Size 5 MB
Publisher FreeImage
Product FreeImage

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-06-04 23:01:00 (a year ago); latest analysis 2025-06-04 23:01:00 (a year ago).

Publisher context

Company metadata: FreeImage. Product metadata: FreeImage.

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.

FreeImage.dll is a Windows file recorded in the ThreatInfo database. It is associated with FreeImage. The reported company name is FreeImage. The current detection status is Undefined, based on the latest analysis from 2025-06-04 23:01:00 (a year 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: FreeImage
Company Name: FreeImage
MD5: 92ca0724dc0147da0e62f9971bd03e98
Size: 5 MB
First Published: 2025-06-04 23:01:00 (a year ago)
Latest Published: 2025-06-04 23:01:00 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-06-04 23:01:00 (a year ago)
%appdata%

ThreatInfo has observed FreeImage.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 FreeImage.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.

FreeImage.dll is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x00266347
Image base 0x10000000

PE Sections:

Sections 8
Raw data 5977600

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

.text 2743808 bytes · 45.9% of section data
MD5 1cf828d51f4ded6d7cc23a41b0470550
.rdata 1511424 bytes · 25.3% of section data
MD5 789c70ad5c9dcf1ad2aab5f299431a60
.data 1623040 bytes · 27.2% of section data
MD5 64a0e8fa59e9e9773b29f2f5b3c9472a
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 7b772dc3dd4cc3204b8877e1a91b94b1
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
_RDATA 2048 bytes · 0.0% of section data
Uncommon name
MD5 664cc61e4aeeae68b7fa655087e8e5e6
.rsrc 1536 bytes · 0.0% of section data
MD5 ba0fb86000070e3704c14e42b931711d
.reloc 94720 bytes · 1.6% of section data
MD5 b6be93164d1838a66460e42fecc1292a

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 92ca0724dc0147da0e62f9971bd03e98.
  • 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.