GridinSoft Threat Intelligence

DigitalSignatureLib.dll file report

Under review File reputation report
MD5 0fa587b62211d32dda87acdff2d498e9
Latest seen 2023-10-21 23:22:08 (2 years ago)
First seen 2018-04-17 21:03:00 (8 years ago)
Size 39 KB
Signed by SolarWinds, Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-04-17 21:03:00 (8 years ago); latest analysis 2023-10-21 23:22:08 (2 years ago).

Digital signature

Signed by SolarWinds, 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.

DigitalSignatureLib.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2023-10-21 23:22:08 (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.

MD5: 0fa587b62211d32dda87acdff2d498e9
Size: 39 KB
First Published: 2018-04-17 21:03:00 (8 years ago)
Latest Published: 2023-10-21 23:22:08 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-10-21 23:22:08 (2 years ago)
Signed By: SolarWinds, Inc.
Status: Valid

The signature on DigitalSignatureLib.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 DigitalSignatureLib.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 57.1%
Windows 7 21.4%
Windows Server 2016 21.4%

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

DigitalSignatureLib.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x000015cb
Image base 0x10000000

PE Sections:

Sections 5
Raw data 33280

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

.text 18944 bytes · 56.9% of section data
MD5 a3a42ed6ccac90a67d758839479eca37
.rdata 8704 bytes · 26.2% of section data
MD5 fa2104b9cc3814111f3a8219b483be18
.data 3072 bytes · 9.2% of section data
MD5 fdde1291ddec36a9773250d3d4a413dc
.rsrc 512 bytes · 1.5% of section data
MD5 276fe64142f25c6f23aa6ceb66b1c307
.reloc 2048 bytes · 6.2% of section data
MD5 2ea2f37494a64d881e981d704dc367ae

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 0fa587b62211d32dda87acdff2d498e9.
  • 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.