GridinSoft Threat Intelligence

notifierlib.dll file report

Under review File reputation report
MD5 4d548b23de08a311a4a52ac27758fa23
Latest seen 2021-06-13 20:23:39 (4 years ago)
First seen 2020-06-15 06:26:11 (5 years ago)
Size 398 KB
Publisher Systweak Software
Product notifierlib

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-06-15 06:26:11 (5 years ago); latest analysis 2021-06-13 20:23:39 (4 years ago).

Publisher context

Company metadata: Systweak Software. Product metadata: notifierlib.

Digital signature

Signed by SYSTWEAK SOFTWARE PVT. LTD.. 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.

notifierlib.dll is a Windows file recorded in the ThreatInfo database. It is associated with notifierlib. The reported company name is Systweak Software. The current detection status is Undefined, based on the latest analysis from 2021-06-13 20:23:39 (4 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: notifierlib
Company Name: Systweak Software
MD5: 4d548b23de08a311a4a52ac27758fa23
Size: 398 KB
First Published: 2020-06-15 06:26:11 (5 years ago)
Latest Published: 2021-06-13 20:23:39 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-06-13 20:23:39 (4 years ago)
Signed By: SYSTWEAK SOFTWARE PVT. LTD.
Status: Valid

The signature on notifierlib.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%

ThreatInfo has observed notifierlib.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 85.7%
Windows 7 14.3%

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

notifierlib.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 0x0006324e
Image base 0x10000000

.NET Info:

MVID: e24c75d6-d676-4344-a464-c4cd3587ab86

PE Sections:

Sections 3
Raw data 399872

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

.text 398336 bytes · 99.6% of section data
MD5 5e28acecdb97c3a991a10ef091649abc
.rsrc 1024 bytes · 0.3% of section data
MD5 966e7f3077003f6ed32271ca1bea53fc
.reloc 512 bytes · 0.1% of section data
MD5 6259daa91bd725977b295b737e1af49b

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 4d548b23de08a311a4a52ac27758fa23.
  • 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.