GridinSoft Threat Intelligence

liblzo2-2.dll file report

Under review File reputation report
MD5 e4fb2a7c1f92d4e61cffe3f2c0ce9f87
Latest seen 2026-01-27 23:00:52 (4 months ago)
First seen 2018-10-30 18:15:16 (7 years ago)
Size 170 KB
Signed by OpenVPN Technologies, Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-10-30 18:15:16 (7 years ago); latest analysis 2026-01-27 23:00:52 (4 months ago).

Digital signature

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

File context

liblzo2-2.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2026-01-27 23:00:52 (4 months 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.

File Details

MD5: e4fb2a7c1f92d4e61cffe3f2c0ce9f87
Size: 170 KB
First Published: 2018-10-30 18:15:16 (7 years ago)
Latest Published: 2026-01-27 23:00:52 (4 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-01-27 23:00:52 (4 months ago)

Overview

Signed By: OpenVPN Technologies, Inc.
Status: Valid

The signature on liblzo2-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.

Common Places:

%programfiles%\totalav
%programfiles%\scanguard
%programfiles%\pcprotect
%programfiles%\totalav\updates\totalav-4.14.31
%programfiles%\totalav\updates\totalav-5.5.83
%sysdrive%\archivos de programa\totalav
%commonappdata%\totalav\updates\5_5_83\prev
%commonappdata%\totalav\updates\5_5_83\extracted
%commonappdata%\totalav\updates\5_17_470\prev

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

Geographic signal

Observed country distribution

ThreatInfo has seen liblzo2-2.dll across 95 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 15.2%
Low High activity

The strongest geographic signal for this file is United States with 15.2% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 82.0%
Windows 7 12.6%
Windows 8.1 3.9%
Windows 8 0.3%
Windows Server 2008 R2 0.3%
Windows Server 2016 0.3%
Windows Server 2012 R2 0.3%
Windows Vista 0.2%
Windows XP 0.1%

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

Analysis

liblzo2-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 0x00001400
Image base 0x6cd80000

PE Sections:

Sections 9
Raw data 163840

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

.text 150528 bytes · 91.9% of section data
MD5 913e6c27326455f7813dcbb9d3dd92ea
.data 512 bytes · 0.3% of section data
MD5 1fcfed838733651b4bbd3c6363ae0bdc
.rdata 5120 bytes · 3.1% of section data
MD5 394b09fa8ac85447f0584b14dfb81f4e
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 4096 bytes · 2.5% of section data
MD5 8cd3b4e4bdb50d44274b62b1e12e65bf
.idata 1536 bytes · 0.9% of section data
MD5 6f2a29af2dacecc8b8b45c0f3a23a5a5
.CRT 512 bytes · 0.3% of section data
MD5 0dd8552ac04d2644c5cd93cf325e417b
.tls 512 bytes · 0.3% of section data
MD5 733a27455b660504a795d59d97948586
.reloc 1024 bytes · 0.6% of section data
MD5 081c0e21dd79c5ebe0531f360d06f0b1

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