GridinSoft Threat Intelligence

log4net.dll file report

Under review File reputation report
MD5 f1f8fe284935fc99264df2e440068750
Latest seen 2024-10-07 23:01:04 (2 years ago)
First seen 2020-12-05 19:39:14 (5 years ago)
Size 318 KB
Product log4net

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-12-05 19:39:14 (5 years ago); latest analysis 2024-10-07 23:01:04 (2 years ago).

Publisher context

Company metadata: The Apache Software Foundation. Product metadata: log4net.

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.

log4net.dll is a Windows file recorded in the ThreatInfo database. It is associated with log4net. The reported company name is The Apache Software Foundation. The current detection status is Undefined, based on the latest analysis from 2024-10-07 23:01:04 (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.

Product Name: log4net
Company Name: The Apache Software Foundation
MD5: f1f8fe284935fc99264df2e440068750
Size: 318 KB
First Published: 2020-12-05 19:39:14 (5 years ago)
Latest Published: 2024-10-07 23:01:04 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-10-07 23:01:04 (2 years ago)
Signed By: LAVASOFT SOFTWARE CANADA INC
Status: Valid

The signature on log4net.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 log4net.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 78.0%
Windows 7 16.7%
Windows 8.1 2.8%
Windows 8 2.4%

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

log4net.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 0x0004a43e
Image base 0x00400000

.NET Info:

MVID: 8b6bfa3e-ebb0-4148-91f9-c410ce536c9a

PE Sections:

Sections 3
Raw data 307200

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

.text 299008 bytes · 97.3% of section data
MD5 7f1f8523910d60ede5943b44bc855651
.rsrc 4096 bytes · 1.3% of section data
MD5 c4818b9f4f1c9d409790b32404619345
.reloc 4096 bytes · 1.3% of section data
MD5 9868e786922c2f8003292deea9541919

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