GridinSoft Threat Intelligence

LZ4.dll file report

Under review File reputation report
MD5 f8a7c813085b746bcdda96930be7fad0
Latest seen 2026-01-05 23:01:21 (4 months ago)
First seen 2022-12-21 23:42:47 (3 years ago)
Size 51 KB
Publisher Milosz Krajewski
Product LZ4

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-12-21 23:42:47 (3 years ago); latest analysis 2026-01-05 23:01:21 (4 months ago).

Publisher context

Company metadata: Milosz Krajewski. Product metadata: LZ4.

Digital signature

Signed by Lavasoft Software 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.

LZ4.dll is a Windows file recorded in the ThreatInfo database. It is associated with LZ4. The reported company name is Milosz Krajewski. The current detection status is Undefined, based on the latest analysis from 2026-01-05 23:01:21 (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.

Product Name: LZ4
Company Name: Milosz Krajewski
MD5: f8a7c813085b746bcdda96930be7fad0
Size: 51 KB
First Published: 2022-12-21 23:42:47 (3 years ago)
Latest Published: 2026-01-05 23:01:21 (4 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-01-05 23:01:21 (4 months ago)
Signed By: Lavasoft Software Canada Inc.
Status: Valid

The signature on LZ4.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%\lavasoft\web companion

ThreatInfo has observed LZ4.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 98.3%
Windows 7 1.7%

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

LZ4.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 0x0000b12e
Image base 0x10000000

.NET Info:

MVID: cb7fa203-93b2-4fb4-a8bf-5b0e51ef01c9

PE Sections:

Sections 3
Raw data 38912

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

.text 37376 bytes · 96.1% of section data
MD5 28ddcedfe2096a71411002a1b32cb060
.rsrc 1024 bytes · 2.6% of section data
MD5 ce213b2c470f1352dc2f62578cc8e65d
.reloc 512 bytes · 1.3% of section data
MD5 e27c5a2f6b6df539ec281a34917e160e

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