File scan report
Verdict Suspicious
Is Grim Dawn.
An unsigned game executable wrapped in Steam DRM, flagged by 3 of the 68 antivirus engines that checked it with generic rule labels only.
Read the whole reasonShow less
Why Suspicious? 3 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
3 of 68 flagged
- Flagged 3
- No detection 65
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Three of the 68 antivirus engines that checked it flagged this file, all with generic machine-learning or header rules; most major engines found nothing. It carries Valve's Steam DRM wrapper, which often trips such heuristics. However, it is unsigned and rarely submitted, so its origin cannot be confirmed.
Microsoft's machine-learning detection, a Zoner header rule and a Bkav generic label are the only detections, and none names a real malware family. Sixteen major antivirus engines, including BitDefender, Kaspersky and ESET, reported nothing. The encrypted high-entropy section belongs to Steam's DRM wrapper, which is a known trigger for these rules rather than malware packing. The sandbox summary recorded no high-risk techniques, no injection targets and no network contacts. Still, the file is unsigned and submitted by only six sources, so no strong benign anchor confirms it is the genuine game binary.
What We Detected
3 of the 68 antivirus engines that checked it flagged this executable, first seen on Jul 23, 2026: Microsoft (a generic machine-learning label), Zoner (a probable header heuristic) and Bkav (a generic label). No named malware family appears, and most major antivirus engines found nothing.
Threat Behavior
The file carries Valve's Steam DRM wrapper, whose encrypted section explains its high entropy. The sandbox summary recorded no high-risk techniques, no process injection targets and no network contacts. The file has no digital signature, and no complete host-reputation result is available.
What To Do Now
Only run game executables obtained through Steam or the official store. If this file came from elsewhere, delete it and reinstall the game from the official source.
Where this verdict could be wrong1 caveat
- The detections are generic machine-learning and header rules that Steam DRM wrappers commonly trigger. Sixteen major antivirus engines found nothing, and no hostile activity in the test run was recorded, so a false positive is quite plausible.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Sixteen major antivirus engines, including BitDefender, Kaspersky and ESET, reported nothing.
- The high-entropy section is explained by Steam's DRM wrapper.
- No high-risk behaviour, injection targets or network contacts were recorded.
- The file has no digital signature to confirm its publisher.
- A major antivirus engine flagged it with a generic machine-learning label.
- It has been submitted by only a handful of sources.
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 4sandbox rule tags
- 1spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 2: FileSeen in the test run
Grim Dawn.exe
19f65c0a916ae70f011ce75d22ad6067fd91333659f7d5043ec68353d77d83e6
Uploaded file
- 1
Processes
What ran
- Evidence 2 of 2: ProcessSeen in the test run
Grim Dawn.exe
"C:\Users\user\Desktop\Grim Dawn.exe"
Test run
2 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
4MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1055· Process injection
- T1071· Application protocol
Observed activity
Processes started
1Programs the file ran, with their command lines.
Grim Dawn.exe"C:\Users\user\Desktop\Grim Dawn.exe"
Chapter 04
Technical details
3 of the 68 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 3
- Microsoft (major engine)Trojan:Win32/Wacatac.B!ml
- BkavW32.Malware.596E6188
- ZonerProbably Heur.ExeHeaderL
File fingerprint
- Last analyzed
- Jul 23, 2026, 11:21 PM UTC
- SHA-256
19f65c0a916ae70f011ce75d22ad6067fd91333659f7d5043ec68353d77d83e6- SHA-1
38628c97a6376ce38a4486efc805ccb4d86ee1b4- MD5
bdb3b7182e8c4bce6c6db9f436397d46
About this file
Grim Dawn.exe is a Win32 EXE file of 4.7 MB.
- Type and size
- Win32 EXE · 4.7 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 23, 2026On VirusTotal.
- Submitted by
- 6 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 6.34 of 8
First scanned Updated
Antivirus consensus
3 of 68 engines flagged this file
6 of the 74 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines1flagged
- Tier-234 engines1flagged
- Low-trust17 engines1flagged
View all 74 engine results
- BkavMalicious: W32.Malware.596E6188
- MicrosoftMalicious: Trojan:Win32/Wacatac.B!ml
- ZonerMalicious: Probably Heur.ExeHeaderL
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleNo result
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Grim Dawn.exe safe, or is it malware?
What is Grim Dawn.exe?
How many antivirus engines detected Grim Dawn.exe?
I already downloaded and ran Grim Dawn.exe — what should I do?
What is the SHA-256 hash of Grim Dawn.exe?
How up to date is this analysis of Grim Dawn.exe?
Community
Member reviews and reports for this exact file hash.