GridinSoft Threat Intelligence

log4net.dll file report

Under review File reputation report
MD5 2c0e3d187bdeb05ceac44fa5bc5c9f8c
Latest seen 2021-03-27 21:43:48 (5 years ago)
First seen 2021-03-27 21:43:48 (5 years ago)
Size 270 KB
Product log4net

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-03-27 21:43:48 (5 years ago); latest analysis 2021-03-27 21:43:48 (5 years ago).

Publisher context

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

Digital signature

Signed by Solarwinds Worldwide, LLC. 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 2021-03-27 21:43:48 (5 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: 2c0e3d187bdeb05ceac44fa5bc5c9f8c
Size: 270 KB
First Published: 2021-03-27 21:43:48 (5 years ago)
Latest Published: 2021-03-27 21:43:48 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-27 21:43:48 (5 years ago)
Signed By: Solarwinds Worldwide, LLC
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.

%localappdata%

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 7 100.0%

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

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 0x00040aae
Image base 0x00400000

.NET Info:

MVID: 09b08c78-8842-4fb5-9c1c-d468a267c0c8

PE Sections:

Sections 3
Raw data 266240

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

.text 258048 bytes · 96.9% of section data
MD5 5d9a4f6760e531539f4da5d503a1d0a5
.rsrc 4096 bytes · 1.5% of section data
MD5 54d3d1103e1806da2e5438684733a6bd
.reloc 4096 bytes · 1.5% of section data
MD5 7fe7198e3aa596a1c264c94ddcfb44bf

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 2c0e3d187bdeb05ceac44fa5bc5c9f8c.
  • 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.