LichdomBattlemage.exe threat report

MD5 fb89af9f1e818fde494aec8126abfd12
Latest seen 2022-03-15 23:21:48 (4 years ago)
First seen 2022-03-15 23:21:48 (4 years ago)
Size 32 MB
Publisher Xaviant, LLC

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
2022-03-15 23:21:48 (4 years ago)
File hash
fb89af9f1e818fde494aec8126abfd12
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2022-03-15 23:21:48 (4 years ago); latest analysis 2022-03-15 23:21:48 (4 years ago).

Publisher context

Company metadata: Xaviant, LLC. Product metadata: Lichdom Battlemage.

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.

LichdomBattlemage.exe is a Windows file recorded in the ThreatInfo database. It is associated with Lichdom Battlemage. The reported company name is Xaviant, LLC. The current detection status is Trojan.Heur!, based on the latest analysis from 2022-03-15 23:21:48 (4 years ago).

If LichdomBattlemage.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: Lichdom Battlemage
Company Name: Xaviant, LLC
MD5: fb89af9f1e818fde494aec8126abfd12
Size: 32 MB
First Published: 2022-03-15 23:21:48 (4 years ago)
Latest Published: 2022-03-15 23:21:48 (4 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2022-03-15 23:21:48 (4 years ago)
LichdomBattlemage.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.

%sysdrive%\steamlibrary\steamapps\common\lichdom battlemage

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

100.0%

The strongest geographic signal for this file is Poland with 100.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 LichdomBattlemage.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.

LichdomBattlemage.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: 0x0000000137000000
Entry Address: 0x025ea2f0

PE Sections:

Name Size of data MD5
.text 27424768 c770bccac7f13aeb79c5532661bbe142
PSFD00 8704 4fb7ec28bc021b0d3fa2a4b7e91b0b1e
.rdata 4492288 c32556b040ee4baa2560a3d844b2df24
.data 289280 769375eb2ebd40664139f1daaf567396
.pdata 1426944 d2e5791e1ed0751b1de6c7a91c3a56bb
_RDATA 37376 f4e984ac0630e25a3aa35b86bf86f3e1
.rsrc 304128 039f628f59bdf257451b997a0eae74f0
.bind 463440 2162e668a3d1771d689b58fa328004c7

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: