GridinSoft Threat Intelligence

updater.node file report

Under review File reputation report
MD5 19036ad63d2eeebb28ee285e5156ad89
Latest seen 2024-01-01 23:42:50 (2 years ago)
First seen 2024-01-01 23:42:50 (2 years ago)
Size 3 MB
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:50 (2 years ago); latest analysis 2024-01-01 23:42:50 (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.

updater.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:50 (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: 19036ad63d2eeebb28ee285e5156ad89
Size: 3 MB
First Published: 2024-01-01 23:42:50 (2 years ago)
Latest Published: 2024-01-01 23:42:50 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-01 23:42:50 (2 years ago)
Signed By: Discord Inc.
Status: Valid

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

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

updater.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 0x0021ae00
Image base 0x10000000

PE Sections:

Sections 5
Raw data 3517952

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

.text 2323968 bytes · 66.1% of section data
MD5 6a46b540f4be0004e08102aeb59470d4
.rdata 1069568 bytes · 30.4% of section data
MD5 28ed1efedb84302ec15b8cb7ce877300
.data 14336 bytes · 0.4% of section data
MD5 8cd6b72c96f18aef7516c983744204f9
.didat 512 bytes · 0.0% of section data
Uncommon name
MD5 d3bb746fd5197041fe8c1021613b8339
.reloc 109568 bytes · 3.1% of section data
MD5 02ef1ebbaaf0a998e138920af718f3b1

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 19036ad63d2eeebb28ee285e5156ad89.
  • 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.