Is Grim Dawn.exe safe?
Only MaxSecure flagged this unsigned executable among 74 engines, while tier-one engines remained silent; a T1055 runtime mapping warrants ordinary caution.
Only 1 of 74 engines flagged the file, and that detection came from MaxSecure with a generic label; all 17 reporting tier-one engines found nothing. One sandbox recorded a possible T1055 process-injection technique, but issued no malicious conclusion, and curated external intelligence supplied no corroborating hit.
10d24c020fe770be84…0eeec17a705bbcRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Only 1 of 74 engines flagged the file, and that detection came from MaxSecure with a generic label; all 17 reporting tier-one engines found nothing. One sandbox recorded a possible T1055 process-injection technique, but issued no malicious conclusion, and curated external intelligence supplied no corroborating hit.
The detection pattern is dominated by a single generic MaxSecure result among 74 engines, with no tier-one detections or family consensus. All 17 reporting tier-one engines were clean, making the isolated low-trust alert likely to be a false positive. Runtime evidence mapped activity to T1055, so the file is not entirely free of concern, although the completed sandbox did not issue a malicious conclusion. Static analysis found neither likely packing nor high-entropy code, and curated external intelligence returned no matching rules or known-malware record. The executable is unsigned, and no complete contacted-host reputation result is available, which limits confidence.
What We Detected
Only 1 of 74 antivirus engines flagged the executable. The sole alert was MaxSecure's generic Trojan.Malware.300983.susgen label; tier-one engines produced zero detections, with all 17 reporting tier-one engines returning no alert. Curated external checks also returned no MalwareBazaar, CIRCL, or YARAify hit.
Threat Behavior
One completed sandbox mapped activity to MITRE T1055, which can indicate process injection, but the evidence does not establish the exact method or malicious intent. That sandbox did not issue a malicious conclusion, and no dropped files, persistence indicators, or network contacts were recorded. Because contactedHosts is null, no complete host-reputation result is available. Static PE analysis found no packer, likely packing, or high-entropy code.
What To Do Now
Obtain the executable from the official game storefront or publisher channel and compare its hash or installation integrity before running it. Keep endpoint protection enabled; if the file came from a crack, mod bundle, or unofficial download, discard it and reinstall from a trusted source.
Where this verdict could be wrong4 caveats
- T1055 appears in behaviour.offensiveTechniques, indicating possible process injection; the saved mapping does not establish the specific method or malicious intent.
- signing.signed=false means there is no verified publisher identity for this executable.
- A communityComments annotation reports a suspicious DynDNS-related rule match, but externalIntel.yaraify.ruleCount=0 and no network contacts were recorded to corroborate it.
- contactedHosts=null, so no completed host-reputation cross-check is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1/74 engines flagged the sample
- engines.tier1Malicious=0 and 17 tier-one engines reported clean
- The sole detection came from low-trust MaxSecure and used a generic label
- behaviour.hasMaliciousSandboxVerdict=false
- No MalwareBazaar, CIRCL, or YARAify hit was returned
- Unsigned Win32 executable with no authenticated publisher
- Runtime evidence maps possible process injection to MITRE T1055
- Community annotation reports a suspicious DynDNS-related signature
- No completed contacted-host reputation cross-check is available
Use only a copy obtained through the official publisher or game storefront, and verify installation integrity where supported. Keep endpoint protection enabled and avoid unofficial repacks or modified executables.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 4MITRE ATT&CK techniques
- 1spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 1 / 74engines flagged
- 21sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 74 antivirus engines flagged the file, including MaxSecure.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 24 times from 21 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Grim Dawn.exe — 10d24c020fe770be8450120a57811c04e5ea4135e41c131a4a0eeec17a705bbc
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\user\Desktop\Grim Dawn.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Users\user\Desktop\Grim Dawn.exe"
1 of 74 engines flagged this file
View all 74 engine results
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.
Fingerprint and provenance
- File name
- Grim Dawn.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 3.5 MB
- Last analyzed
- Sep 28, 2026, 6:18 PM UTC
10d24c020fe770be8450120a57811c04e5ea4135e41c131a4a0eeec17a705bbcSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Grim Dawn.exe safe?
What is Grim Dawn.exe?
How many antivirus engines detected Grim Dawn.exe?
What is the SHA-256 hash of Grim Dawn.exe?
Is it safe to run Grim Dawn.exe?
How up to date is this analysis of Grim Dawn.exe?
Community
Member reviews and reports for this exact file hash.