GridinSoft Threat Intelligence

odin.node file report

Under review File reputation report
MD5 9625a2da97c0b79b893ae419065ae0cd
Latest seen 2025-08-14 23:00:54 (9 months ago)
First seen 2025-08-14 23:00:44 (9 months ago)
Size 729 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-14 23:00:44 (9 months ago); latest analysis 2025-08-14 23:00:54 (9 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-08-14 23:00:54 (9 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: 9625a2da97c0b79b893ae419065ae0cd
Size: 729 KB
First Published: 2025-08-14 23:00:44 (9 months ago)
Latest Published: 2025-08-14 23:00:54 (9 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-08-14 23:00:54 (9 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.0.26\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 0x0006be44
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 734208

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

.text 576512 bytes · 78.5% of section data
MD5 9e1547809acf2ba6d2cbd12c65a7a64c
.rdata 126464 bytes · 17.2% of section data
MD5 9794f8f4323a2397e5c60ece1b84caa0
.data 5632 bytes · 0.8% of section data
MD5 834046532c6f6b7d3f145222874bb9e5
.pdata 22016 bytes · 3.0% of section data
MD5 86207797ee3317bc6bdef05f6331c82b
.fptable 512 bytes · 0.1% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 512 bytes · 0.1% of section data
MD5 d41f41f480202a2c0ac2553a22c89ad7
.reloc 2560 bytes · 0.3% of section data
MD5 3b101e5057710105cef5058ff9beea9c

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 9625a2da97c0b79b893ae419065ae0cd.
  • 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.