GridinSoft Threat Intelligence

SlayTheSpire2.exe threat report

Detected as Trojan.Heur! File reputation report
MD5 027e9b70eb021ecd9eb47ed9c12ae6c7
Latest seen 2026-05-18 10:01:03 (a week ago)
First seen 2026-05-18 10:01:03 (a week ago)
Size 853 MB

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-05-18 10:01:03 (a week ago)
File hash
027e9b70eb021ecd9eb47ed9c12ae6c7
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-05-18 10:01:03 (a week ago); latest analysis 2026-05-18 10:01:03 (a week ago).

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.

SlayTheSpire2.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Trojan.Heur!, based on the latest analysis from 2026-05-18 10:01:03 (a week ago). ThreatInfo groups this verdict with Trojan reports for broader family-level investigation.

If SlayTheSpire2.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!.

MD5: 027e9b70eb021ecd9eb47ed9c12ae6c7
Size: 853 MB
First Published: 2026-05-18 10:01:03 (a week ago)
Latest Published: 2026-05-18 10:01:03 (a week ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2026-05-18 10:01:03 (a week ago)
SlayTheSpire2.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.

%programfiles%\steam\steamapps\common

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

SlayTheSpire2.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 0x0046cff0
Image base 0x0000000140000000

PE Sections:

Sections 17
Raw data 894748160

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

.text 71014912 bytes · 7.9% of section data
Large raw data
MD5 24e728c2497e50db3bb9f7d2dbc110eb
.rdata 19218944 bytes · 2.1% of section data
Large raw data
MD5 fe649c88cddba8fab59ae76eb3de315f
.buildid 512 bytes · 0.0% of section data
Uncommon name
MD5 bec4eef0f53271bb23091e6fac6fa153
.data 37376 bytes · 0.0% of section data
MD5 3b139f26b2636b3d71ae86123c7d332b
.pdata 1007104 bytes · 0.1% of section data
MD5 c0f69947584329c62ebbc96ad8555f88
.tls 2560 bytes · 0.0% of section data
MD5 ee45d07d0b0658c7d8334de8be27b0e1
pck 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 103424 bytes · 0.0% of section data
MD5 c0918a5508860c31616563af3d60e787
.reloc 345088 bytes · 0.0% of section data
MD5 b158b35fa5166b216c187fc8d6011d0a
/4 5091328 bytes · 0.6% of section data
Large raw data Uncommon name
MD5 07fe77627ff889a1a85f135706069804
/18 512 bytes · 0.0% of section data
Uncommon name
MD5 9d6aaed1a34f4cc33b2d09d56757e25b
/30 20992 bytes · 0.0% of section data
Uncommon name
MD5 31a1d0c8dd6aadbb8443d0bdba45ffb3
/45 301043200 bytes · 33.6% of section data
Large raw data Uncommon name
MD5 125e2798cdb8ee11385ff88167837cfa
/57 37974528 bytes · 4.2% of section data
Large raw data Uncommon name
MD5 30ef89822c1208fce2ec172743685c7b
/69 161246208 bytes · 18.0% of section data
Large raw data Uncommon name
MD5 f071fe0666d0edb00d0a3bb8413f0e86
/80 44391424 bytes · 5.0% of section data
Large raw data Uncommon name
MD5 46e0b99e4868f10c2d59962bf6cb8a21
/94 253249536 bytes · 28.3% of section data
Large raw data Uncommon name
MD5 5726a9d7f38fdf67820322c82ed52d50

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 SlayTheSpire2.exe by MD5 027e9b70eb021ecd9eb47ed9c12ae6c7. 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 027e9b70eb021ecd9eb47ed9c12ae6c7.
  • 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.