GridinSoft Threat Intelligence

libxml2.dll file report

Clean record File reputation report
MD5 dbf4e71c21cfe60056d40cf518311321
Latest seen 2022-05-05 23:05:48 (4 years ago)
First seen 2022-05-05 23:05:48 (4 years ago)
Size 1015 KB
Publisher Apple Inc.
Product libxml2.dll
Signed by Apple Inc.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-05-05 23:05:48 (4 years ago); latest analysis 2022-05-05 23:05:48 (4 years ago).

Publisher context

Company metadata: Apple Inc.. Product metadata: libxml2.dll.

Digital signature

Signed by Apple Inc.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

libxml2.dll is a Windows file recorded in the ThreatInfo database. It is associated with libxml2.dll. The reported company name is Apple Inc.. The current detection status is Clean, based on the latest analysis from 2022-05-05 23:05:48 (4 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: libxml2.dll
Company Name: Apple Inc.
MD5: dbf4e71c21cfe60056d40cf518311321
Size: 1015 KB
First Published: 2022-05-05 23:05:48 (4 years ago)
Latest Published: 2022-05-05 23:05:48 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-05-05 23:05:48 (4 years ago)
Signed By: Apple Inc.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%appdata%\tenorshare

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

libxml2.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 0x000c0f97
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1025024

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

.text 788480 bytes · 76.9% of section data
MD5 a9bdb9f04cb5df3f0ada8c017f84323c
.rdata 196096 bytes · 19.1% of section data
MD5 2721aaf37ba642ce3bd2cb694b0e3298
.data 2048 bytes · 0.2% of section data
MD5 1d21105f2cd278d7cdddda123129ec4e
.rsrc 1024 bytes · 0.1% of section data
MD5 58cf01a0c467a5a2069e9b798174874b
.reloc 37376 bytes · 3.6% of section data
MD5 83c353866061fc41848d854557a727b9

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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