GridinSoft Threat Intelligence

NLog.dll file report

Under review File reputation report
MD5 de6ab61d8711ff840bdd16ee4d4a42fb
Latest seen 2024-11-12 23:01:58 (2 years ago)
First seen 2023-08-03 23:22:09 (2 years ago)
Size 826 KB
Publisher NLog
Product NLog v4.6.8
Signed by SweetLabs Inc

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-08-03 23:22:09 (2 years ago); latest analysis 2024-11-12 23:01:58 (2 years ago).

Publisher context

Company metadata: NLog. Product metadata: NLog v4.6.8.

Digital signature

Signed by SweetLabs 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.

NLog.dll is a Windows file recorded in the ThreatInfo database. It is associated with NLog v4.6.8. The reported company name is NLog. The current detection status is Undefined, based on the latest analysis from 2024-11-12 23:01:58 (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: NLog v4.6.8
Company Name: NLog
MD5: de6ab61d8711ff840bdd16ee4d4a42fb
Size: 826 KB
First Published: 2023-08-03 23:22:09 (2 years ago)
Latest Published: 2024-11-12 23:01:58 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-11-12 23:01:58 (2 years ago)
Signed By: SweetLabs Inc
Status: Valid

The signature on NLog.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%\host app service

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

NLog.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 0x000cdb92
Image base 0x10000000

PE Sections:

Sections 3
Raw data 837632

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

.text 835072 bytes · 99.7% of section data
MD5 8992c2c049e10b14b53afd1eb7a5ba87
.rsrc 2048 bytes · 0.2% of section data
MD5 7523476fb9ac1e868199f684e4cbe94d
.reloc 512 bytes · 0.1% of section data
MD5 d299a2b5c6ae9d25710f0aed137ebfda

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