GridinSoft Threat Intelligence

liblz4.dll file report

Under review File reputation report
MD5 00303518148ef1806238ab6b73ba7795
Latest seen 2025-07-31 23:01:42 (10 months ago)
First seen 2025-07-31 23:01:42 (10 months ago)
Size 133 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-07-31 23:01:42 (10 months ago); latest analysis 2025-07-31 23:01:42 (10 months ago).

Digital signature

Signed by 7270356 Canada 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.

liblz4.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2025-07-31 23:01:42 (10 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.

MD5: 00303518148ef1806238ab6b73ba7795
Size: 133 KB
First Published: 2025-07-31 23:01:42 (10 months ago)
Latest Published: 2025-07-31 23:01:42 (10 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-07-31 23:01:42 (10 months ago)
Signed By: 7270356 Canada Inc.
Status: Valid

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

%appdata%\lavasoft\web companion

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

liblz4.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 0x661c0000

PE Sections:

Sections 10
Raw data 109056

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

.text 93184 bytes · 85.4% of section data
MD5 9d4385ed2e17507beaa6795929845faa
.data 512 bytes · 0.5% of section data
MD5 d40b0aca480b7c2bf3b2f9a71128b62b
.rdata 1536 bytes · 1.4% of section data
MD5 c64da5412ab570f6e488ff028747790e
.eh_fram 8192 bytes · 7.5% of section data
Uncommon name
MD5 2f10acfb1a0ea7935bc8f18aa86ba38e
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.edata 3072 bytes · 2.8% of section data
MD5 6baa56a8d558df6d34bdd0ddd51a39ab
.idata 1024 bytes · 0.9% of section data
MD5 8436f96634eb3e00344f3b7241434b8d
.CRT 512 bytes · 0.5% of section data
MD5 7c68ced9bba757d7d743c0755fc10ee2
.tls 512 bytes · 0.5% of section data
MD5 05b17baa76a6dc0a02f6903cb8a21fb5
.reloc 512 bytes · 0.5% of section data
MD5 b5af59728d8675fe6446f3d078b1c9d0

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 00303518148ef1806238ab6b73ba7795.
  • 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.