forhonor.exe threat report

MD5 bd2a1684de641b0472099999f914f295
Latest seen 2024-01-31 23:00:37 (2 years ago)
First seen 2023-02-28 23:37:30 (3 years ago)
Size 104 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-31 23:00:37 (2 years ago)
File hash
bd2a1684de641b0472099999f914f295
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2023-02-28 23:37:30 (3 years ago); latest analysis 2024-01-31 23:00:37 (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.

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-31 23:00:37 (2 years ago).

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: bd2a1684de641b0472099999f914f295
Size: 104 MB
First Published: 2023-02-28 23:37:30 (3 years ago)
Latest Published: 2024-01-31 23:00:37 (2 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2024-01-31 23:00:37 (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%\steamlibrary\steamapps\common
%programfiles%\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.

50.0%
50.0%

The strongest geographic signal for this file is Argentina with 50.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

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 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x03128151

PE Sections:

Name Size of data MD5
.xdata 0 d41d8cd98f00b204e9800998ecf8427e
.code 6032896 44bc31a0f541a93f3bf200bf01d4df62
.reloc 3771904 1ce731c55d83c4dae30b430a0b2ce937
.pdata 1792000 a8f2e12df210ee3361e0f8175f27ac85
.link 9728 6afb8f345e4a9829a730134f5f191494
.rdata 2560 7401af96ad0aeaeb5e546c7e4d5b1431
.arch 35840 91a8003cbdcffc7b1c755cf91e677c06
.xcode 1024 6eec32b2ecc71ab4238feab283c12e1a
.sdata 512 c8da816fae67bf3678347c87fd56cf5a
.xtext 4096 620f0b67a91f7f74151bc5be745b7110
.rsrc 97452032 6466af02e6bdb543667ba6ba4fc9bdce
.idata 236032 e60900b5171c8a0e51bcd82f641c33c0

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.

More information: