GridinSoft Threat Intelligence

cld.node file report

Under review File reputation report
MD5 8f382f24f14c3839dc43e062f97f2e48
Latest seen 2022-07-26 23:25:06 (3 years ago)
First seen 2022-07-26 23:25:06 (3 years ago)
Size 2 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:25:06 (3 years ago); latest analysis 2022-07-26 23:25:06 (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.

cld.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:25:06 (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: 8f382f24f14c3839dc43e062f97f2e48
Size: 2 MB
First Published: 2022-07-26 23:25:06 (3 years ago)
Latest Published: 2022-07-26 23:25:06 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-07-26 23:25:06 (3 years ago)
Signed By: Discord Inc.
Status: Valid

The signature on cld.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_spellcheck-1\discord_spellcheck\node_modules\cld\build

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

cld.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 0x00003035
Image base 0x10000000

PE Sections:

Sections 9
Raw data 2665984

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

.text 492032 bytes · 18.5% of section data
MD5 7b91dc1803f581a43b376d630ec51c1f
.rdata 2129920 bytes · 79.9% of section data
MD5 04d85cf097f6fb1789ae1afea848f530
.data 5120 bytes · 0.2% of section data
MD5 20c630294b0e194685cb922817c780aa
.idata 3584 bytes · 0.1% of section data
MD5 ceaaca47de0232d12c6efa0e17eda37d
.didat 2560 bytes · 0.1% of section data
Uncommon name
MD5 69cc5771cda64c49be84f57774758da5
.tls 1024 bytes · 0.0% of section data
MD5 c573bd7cea296a9c5d230ca6b5aee1a6
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 efc8a07651da175bcb6c9c5755ba7db8
.rsrc 1536 bytes · 0.1% of section data
MD5 ce71617f84e7b24b940816d5176e472a
.reloc 29696 bytes · 1.1% of section data
MD5 ffc3bf498263959bbaebc89e262ea4a3

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 8f382f24f14c3839dc43e062f97f2e48.
  • 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.