GridinSoft Threat Intelligence

discord_hook.node file report

Under review File reputation report
MD5 88b0b0eb3807c1a83e24ee383bd2c38d
Latest seen 2022-07-26 23:36:13 (3 years ago)
First seen 2022-07-26 23:36:13 (3 years ago)
Size 1 MB
Signed by Discord Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-07-26 23:36:13 (3 years ago); latest analysis 2022-07-26 23:36:13 (3 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.

discord_hook.node is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2022-07-26 23:36:13 (3 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: 88b0b0eb3807c1a83e24ee383bd2c38d
Size: 1 MB
First Published: 2022-07-26 23:36:13 (3 years ago)
Latest Published: 2022-07-26 23:36:13 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-07-26 23:36:13 (3 years ago)
Signed By: Discord Inc.
Status: Valid

The signature on discord_hook.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%\arrowfmv\discord\app-1.0.9005\modules\discord_hook-1

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

discord_hook.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 0x000808cb
Image base 0x10000000

PE Sections:

Sections 7
Raw data 1076736

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

.text 894464 bytes · 83.1% of section data
MD5 cab772b2779857a2a01425865c8c54fe
.rdata 125952 bytes · 11.7% of section data
MD5 404ae7fce73b1052d1a63132772356d4
.data 18432 bytes · 1.7% of section data
MD5 9181fc71d946ba771b25ae80584e0c43
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 ce94b9363b52a0d50357f105fec3a8da
.tls 512 bytes · 0.0% of section data
MD5 8e3343efa9afc26ac6caf49228cbe049
.voltbl 512 bytes · 0.0% of section data
Uncommon name
MD5 a4dce0c92d81a3b19adeb71d1b4de702
.reloc 36352 bytes · 3.4% of section data
MD5 015f6751b6f1aa46d9c324f33bd1ad86

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 88b0b0eb3807c1a83e24ee383bd2c38d.
  • 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.