GridinSoft Threat Intelligence

notificationstate.node file report

Under review File reputation report
MD5 ae40e3fce8d217b2cf7dc2c55e94994c
Latest seen 2024-01-01 23:42:12 (2 years ago)
First seen 2024-01-01 23:42:12 (2 years ago)
Size 100 KB
Signed by Discord Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-01-01 23:42:12 (2 years ago); latest analysis 2024-01-01 23:42:12 (2 years ago).

Digital signature

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

notificationstate.node is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2024-01-01 23:42:12 (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: ae40e3fce8d217b2cf7dc2c55e94994c
Size: 100 KB
First Published: 2024-01-01 23:42:12 (2 years ago)
Latest Published: 2024-01-01 23:42:12 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-01 23:42:12 (2 years ago)
Signed By: Discord Inc.
Status: Valid

The signature on notificationstate.node 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.

%commonappdata%\hi\discord\app-1.0.9027\modules\discord_utils-1\discord_utils\node_modules\macos-notification-state\build

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

notificationstate.node 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 0x00001441
Image base 0x10000000

PE Sections:

Sections 5
Raw data 82432

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

.text 50176 bytes · 60.9% of section data
MD5 299ef4c84e6c88d9b7197b9fb6c5e82c
.rdata 25088 bytes · 30.4% of section data
MD5 198933c8dcbbd21460ef11783b3ea989
.data 2560 bytes · 3.1% of section data
MD5 86b5be2944c5c59aff9c9de041c959d3
.rsrc 512 bytes · 0.6% of section data
MD5 d800476d74df07915cdcf1a87a5052a7
.reloc 4096 bytes · 5.0% of section data
MD5 8d2260cca971aebb5764ee7a2d0cf6d1

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