GridinSoft Threat Intelligence

forhonor.exe threat report

Detected as Trojan.Heur! File reputation report
MD5 57a9282d78c6bcb14426cce8baf15ae4
Latest seen 2024-01-12 23:48:30 (2 years ago)
First seen 2024-01-12 23:48:30 (2 years ago)
Size 102 MB
Publisher Ubisoft
Product ForHonor
Signed by Blue Byte GmbH

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2024-01-12 23:48:30 (2 years ago)
File hash
57a9282d78c6bcb14426cce8baf15ae4
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!, part of the Trojan threat category.

Category context

Malware disguised as legitimate software or delivered through deceptive packaging. Related Trojan reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2024-01-12 23:48:30 (2 years ago); latest analysis 2024-01-12 23:48:30 (2 years ago).

Publisher context

Company metadata: Ubisoft. Product metadata: ForHonor.

Digital signature

Signed by Blue Byte 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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present. Review the Trojan category for related samples and common context.

forhonor.exe is a Windows file recorded in the ThreatInfo database. It is associated with ForHonor. The reported company name is Ubisoft. The current detection status is Trojan.Heur!, based on the latest analysis from 2024-01-12 23:48:30 (2 years ago). ThreatInfo groups this verdict with Trojan reports for broader family-level investigation.

If forhonor.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.

Product Name: ForHonor
Company Name: Ubisoft
MD5: 57a9282d78c6bcb14426cce8baf15ae4
Size: 102 MB
First Published: 2024-01-12 23:48:30 (2 years ago)
Latest Published: 2024-01-12 23:48:30 (2 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2024-01-12 23:48:30 (2 years ago)
forhonor.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Signed By: Blue Byte GmbH
Status: Valid

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

%sysdrive%\steam\steamapps\common

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

forhonor.exe 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 0x03194151
Image base 0x0000000140000000

PE Sections:

Sections 12
Raw data 107622912

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

.text 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 6057984 bytes · 5.6% of section data
Large raw data
MD5 bb3ed4f319bbdaf851060ef6f75a0714
.sbss 3804672 bytes · 3.5% of section data
Uncommon name
MD5 47665e77b29ac918d6e8916fd6482b41
.pdata 1804288 bytes · 1.7% of section data
MD5 c59ff781274a58e3a10a47479c564f95
.xtext 9728 bytes · 0.0% of section data
Uncommon name
MD5 888710ec486485b702e806cc8ae15984
.rsrc 2560 bytes · 0.0% of section data
MD5 d2ea48a839549d5b7f1fe834f5b697d3
.srdata 35840 bytes · 0.0% of section data
Uncommon name
MD5 91a8003cbdcffc7b1c755cf91e677c06
.data1 1024 bytes · 0.0% of section data
Uncommon name
MD5 96c2d6b8ae8df211c70268db886ca765
.bss 512 bytes · 0.0% of section data
MD5 0b7ee8cb1189c138fe3bd1ca8ff594f1
.arch 4096 bytes · 0.0% of section data
Uncommon name
MD5 620f0b67a91f7f74151bc5be745b7110
.tls 95666176 bytes · 88.9% of section data
Large raw data
MD5 105bda7773ce7ed66f7d0c75234eeaa6
.code 236032 bytes · 0.2% of section data
Uncommon name
MD5 6da601c2ca127149e122b873ec54eaf5

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

GridinSoft detects this file as Trojan.Heur!

This report identifies forhonor.exe by MD5 57a9282d78c6bcb14426cce8baf15ae4. It is part of the Trojan report group. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 57a9282d78c6bcb14426cce8baf15ae4.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found. Use the Trojan category to compare similar reports.