GridinSoft Threat Intelligence

odin.node file report

Under review File reputation report
MD5 8fcce550cabe3ed8f25eb35b713e6415
Latest seen 2025-09-02 23:01:57 (8 months ago)
First seen 2025-08-16 23:01:38 (9 months ago)
Size 786 KB
Signed by ESL Gaming GmbH

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-08-16 23:01:38 (9 months ago); latest analysis 2025-09-02 23:01:57 (8 months ago).

Digital signature

Signed by ESL Gaming GmbH. 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.

odin.node is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2025-09-02 23:01:57 (8 months 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: 8fcce550cabe3ed8f25eb35b713e6415
Size: 786 KB
First Published: 2025-08-16 23:01:38 (9 months ago)
Latest Published: 2025-09-02 23:01:57 (8 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-09-02 23:01:57 (8 months ago)
Signed By: ESL Gaming GmbH
Status: Valid

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

%localappdata%\faceit\app-2.1.42\resources\app\build\win32

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

odin.node is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00075dd8
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 792576

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

.text 619520 bytes · 78.2% of section data
MD5 4d1a4f78c3ddd0f4350ff4aea52729b8
.rdata 140288 bytes · 17.7% of section data
MD5 9a942418d832be59aad060d10bfa1086
.data 5632 bytes · 0.7% of section data
MD5 7376d3db0a34c366b9c2b2ae10791c36
.pdata 23552 bytes · 3.0% of section data
MD5 3ce77ae7e0fa6b97f5f8cc9db141d389
.fptable 512 bytes · 0.1% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 512 bytes · 0.1% of section data
MD5 cc1353022ae0aa157590fdd95794c222
.reloc 2560 bytes · 0.3% of section data
MD5 5da0c5f3581b1beaf61638010370c03b

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