GridinSoft Threat Intelligence

libiconv-2.dll file report

Under review File reputation report
MD5 aff7967660fd5cb27bdb0713abd45d08
Latest seen 2021-06-13 20:59:15 (4 years ago)
First seen 2017-10-28 05:10:29 (8 years ago)
Size 896 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-10-28 05:10:29 (8 years ago); latest analysis 2021-06-13 20:59:15 (4 years ago).

Publisher context

Company metadata: Free Software Foundation. Product metadata: libiconv: character set conversion library.

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.

libiconv-2.dll is a Windows file recorded in the ThreatInfo database. It is associated with libiconv: character set conversion library. The reported company name is Free Software Foundation. The current detection status is Undefined, based on the latest analysis from 2021-06-13 20:59:15 (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: libiconv: character set conversion library
Company Name: Free Software Foundation
MD5: aff7967660fd5cb27bdb0713abd45d08
Size: 896 KB
First Published: 2017-10-28 05:10:29 (8 years ago)
Latest Published: 2021-06-13 20:59:15 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-06-13 20:59:15 (4 years ago)
%programfiles%\falcon\mingw\bin
%programfiles%\falcon\mingw

ThreatInfo has observed libiconv-2.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 93.8%
Windows 7 6.3%

The most common operating system signal for libiconv-2.dll is Windows 10 with 93.8% 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.

libiconv-2.dll is identified as pe for 32-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 32-bit
Subsystem Windows CUI
Entry point 0x00001060
Image base 0x66000000

PE Sections:

Sections 8
Raw data 916480

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

.text 72704 bytes · 7.9% of section data
MD5 738d171a45faa20a7b731ac98cf3b015
.data 512 bytes · 0.1% of section data
MD5 b2abfea84dd5a6ec252e6068b19cd068
.rdata 836096 bytes · 91.2% of section data
MD5 e8ffd564830309043f96e7cb8d052d2f
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 512 bytes · 0.1% of section data
MD5 82be77a11fefdd1578d2c6a4a46894e4
.idata 1024 bytes · 0.1% of section data
MD5 84c4ae16a27285836e366438ddaa0f4d
.rsrc 2048 bytes · 0.2% of section data
MD5 2262f1398068affe1b1dd8b48e031233
.reloc 3584 bytes · 0.4% of section data
MD5 e08b34d98e5e35b97ef4ade59848b2ad

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 aff7967660fd5cb27bdb0713abd45d08.
  • 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.