GridinSoft Threat Intelligence

FreeImage.dll file report

Under review File reputation report
MD5 9f0e01fe8f36a0b3a39ce573283fbc0f
Latest seen 2022-08-25 23:14:01 (3 years ago)
First seen 2022-08-25 23:14:01 (3 years 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 2022-08-25 23:14:01 (3 years ago); latest analysis 2022-08-25 23:14:01 (3 years 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 2022-08-25 23:14:01 (3 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: FreeImage
Company Name: FreeImage
MD5: 9f0e01fe8f36a0b3a39ce573283fbc0f
Size: 5 MB
First Published: 2022-08-25 23:14:01 (3 years ago)
Latest Published: 2022-08-25 23:14:01 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-25 23:14:01 (3 years ago)
%programfiles%\software\note5\note5_5.1.4.36469\main

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 7 100.0%

The most common operating system signal for FreeImage.dll is Windows 7 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 0x001d23c8
Image base 0x10000000

PE Sections:

Sections 8
Raw data 5400064

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

.text 2220544 bytes · 41.1% of section data
MD5 c1632692080c893aa86acef0e99776c3
.rdata 1462272 bytes · 27.1% of section data
MD5 e999dde478a1d727ee5e5f2274aa2ac2
.data 1630720 bytes · 30.2% of section data
MD5 2d72de2c90e8e9c225a4917231367379
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 3cedca79902856db96543b6b83414da4
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 a713a886e740eebbf93d8e0fe58b9918
.rsrc 1536 bytes · 0.0% of section data
MD5 35c0f64b22975f94031118595e2f68b7
.reloc 83456 bytes · 1.5% of section data
MD5 545a505e277185f7606f9d0b86f40d7a

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 9f0e01fe8f36a0b3a39ce573283fbc0f.
  • 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.