GridinSoft Threat Intelligence

FatalFrameII.exe threat report

Detected as Trojan.Heur! File reputation report
MD5 c2e7d59a1e939abb2246251d330d0ad1
Latest seen 2026-03-12 23:02:06 (2 months ago)
First seen 2026-03-12 23:02:06 (2 months ago)
Size 49 MB
Product Fatal Frame II

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
2026-03-12 23:02:06 (2 months ago)
File hash
c2e7d59a1e939abb2246251d330d0ad1
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 2026-03-12 23:02:06 (2 months ago); latest analysis 2026-03-12 23:02:06 (2 months ago).

Publisher context

Company metadata: KOEI TECMO GAMES CO., LTD.. Product metadata: Fatal Frame II.

Digital signature

Signed by 株式会社コーエーテクモゲームス. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.

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.

FatalFrameII.exe is a Windows file recorded in the ThreatInfo database. It is associated with Fatal Frame II. The reported company name is KOEI TECMO GAMES CO., LTD.. The current detection status is Trojan.Heur!, based on the latest analysis from 2026-03-12 23:02:06 (2 months ago). ThreatInfo groups this verdict with Trojan reports for broader family-level investigation.

If FatalFrameII.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: Fatal Frame II
Company Name: KOEI TECMO GAMES CO., LTD.
MD5: c2e7d59a1e939abb2246251d330d0ad1
Size: 49 MB
First Published: 2026-03-12 23:02:06 (2 months ago)
Latest Published: 2026-03-12 23:02:06 (2 months ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2026-03-12 23:02:06 (2 months ago)
FatalFrameII.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: 株式会社コーエーテクモゲームス
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on FatalFrameII.exe is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.

%sysdrive%\games

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

FatalFrameII.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 0x01dc29f0
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 51914312

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

.text 32983040 bytes · 63.5% of section data
Large raw data
MD5 6d9419a1c19eacb6e69f202398b38a4f
.rdata 13177856 bytes · 25.4% of section data
Large raw data
MD5 76f4699b7844ee28834316a424611333
.data 1209856 bytes · 2.3% of section data
MD5 0711c587bc92ea0d2356e2bf6b65dd2e
.pdata 1216512 bytes · 2.3% of section data
MD5 3b5ef7429f9c4e63bc17bb7195502938
_RDATA 40448 bytes · 0.1% of section data
Uncommon name
MD5 cb664bb030292f0b5224c6824733e502
.gehcont 512 bytes · 0.0% of section data
Uncommon name
MD5 2387c2d071f465f8d93a6f2641369708
.rsrc 2542592 bytes · 4.9% of section data
MD5 8f3aa4e241e6c72a974b3675ccf9decf
.reloc 509952 bytes · 1.0% of section data
MD5 3b189705a7ffc0c9a6187a6a7b37100c
.bind 233544 bytes · 0.4% of section data
Uncommon name
MD5 33efe4369192139ecb34e3037fd6c2c0

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 FatalFrameII.exe by MD5 c2e7d59a1e939abb2246251d330d0ad1. 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 c2e7d59a1e939abb2246251d330d0ad1.
  • 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.