GridinSoft Threat Intelligence

libxml2-2.dll file report

Under review File reputation report
MD5 1a22041c44c919be4159ce2b3993e69e
Latest seen 2024-04-29 23:02:13 (2 years ago)
First seen 2017-05-22 11:18:00 (9 years ago)
Size 3 MB
Signed by Digiarty, Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:18:00 (9 years ago); latest analysis 2024-04-29 23:02:13 (2 years ago).

Digital signature

Signed by Digiarty, 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.

libxml2-2.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2024-04-29 23:02:13 (2 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: 1a22041c44c919be4159ce2b3993e69e
Size: 3 MB
First Published: 2017-05-22 11:18:00 (9 years ago)
Latest Published: 2024-04-29 23:02:13 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-04-29 23:02:13 (2 years ago)
Signed By: Digiarty, Inc.
Status: Valid

The signature on libxml2-2.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%\winx_dvd_copy_pro
%programfiles%

ThreatInfo has observed libxml2-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 7 67.6%
Windows 10 32.4%

The most common operating system signal for libxml2-2.dll is Windows 7 with 67.6% 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-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 0x000010c0
Image base 0x70f40000

PE Sections:

Sections 20
Raw data 3763712

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

.text 806912 bytes · 21.4% of section data
MD5 f4d26d79fdffd8b44fdfe0b96bd6aff4
.data 3072 bytes · 0.1% of section data
MD5 20afb66390580a21a5ecf1a87f7c4e1e
.rdata 153088 bytes · 4.1% of section data
MD5 087265c2b3ca781cb20b1eae379f9005
/4 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 50688 bytes · 1.3% of section data
MD5 64d75dda0ecf2517fa3dced9d06ef829
.idata 3072 bytes · 0.1% of section data
MD5 cdf4d059a37d885c98e48768ac05c6c5
.CRT 512 bytes · 0.0% of section data
MD5 2f9d2a68f7faca901c1432db60965bf9
.tls 512 bytes · 0.0% of section data
MD5 4ebd8cfc3b2fb8f3d4061a0249496ddb
.reloc 34304 bytes · 0.9% of section data
MD5 3b841b4612d1e90b3a91ba7321ae4b34
/14 1536 bytes · 0.0% of section data
Uncommon name
MD5 3fbd5ab8fba0f8ac24e059e3b112263f
/29 53760 bytes · 1.4% of section data
Uncommon name
MD5 11193fba72dfe569b8a2629f497cf030
/45 77824 bytes · 2.1% of section data
Uncommon name
MD5 ca076b1ad2483b357d48018473c30fbf
/61 1387008 bytes · 36.9% of section data
Uncommon name
MD5 3f62f5878aba0d4efca1bce93518b11a
/73 34816 bytes · 0.9% of section data
Uncommon name
MD5 064bfc17d262abfde32044dd4b870f4a
/87 192512 bytes · 5.1% of section data
Uncommon name
MD5 95747e354b73aa14ab2a1f63127ec1fe
/99 125440 bytes · 3.3% of section data
Uncommon name
MD5 d55cc7b2e2672f2c0da6b5bac5dcc997
/112 13312 bytes · 0.4% of section data
Uncommon name
MD5 bf21e3ccddbdbf0c8d455d6541e9fcfc
/123 773120 bytes · 20.5% of section data
Uncommon name
MD5 8d262699c8bb652b17a08ef1f3f0a181
/134 51712 bytes · 1.4% of section data
Uncommon name
MD5 53d846c61581d303b6c73ff067d24e6a

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 1a22041c44c919be4159ce2b3993e69e.
  • 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.