File verdict·Decided by the MT AI Engine
Our call

Safe

Dead Cells game executable; 16 tier-1 engines silent; 615 submissions over 678 days; zero malicious consensus.

Trust score88High trust
MT AI confidence · 92%
deadcells_gl.exe
17.2 MB
06489415f452556dd2d1763c1e4a
Antivirus engines
0 of 74 flagged
Code signing
Unsigned
Age
First seen 2y ago
MT AI Engine · our arbiter

The verdict, reasoned out.

Not a rules engine. The MT AI Engine reads every signal we collected, weighs them against history, and commits to an answer.

92%Confidence
Very high
Reasoning

The file exhibits a classic benign-software profile: zero malicious detections across 69 engines, including 16 high-trust vendors (Avast, BitDefender, Kaspersky, ESET-NOD32, Fortinet, F-Secure, Emsisoft, GData, Avira, AVG, DrWeb). Its prevalence classification (common_old, 615 submissions, 678 days) indicates an established, widely-distributed executable. The MITRE techniques observed (T1027, T1056, T1059, T1071, T1082, T1129, T1496, T1497.001, T1574.002) are ambient and consistent with game runtime, anti-cheat, and DRM systems. The MalwareTips.Synth.DirectIpC2 heuristic fired due to direct-IP contact without DNS, but this is routine for game asset delivery and update infrastructure; the absence of any malicious sandbox verdict or contacted-malicious-hosts hits contradicts a C2 interpretation. The filename matches the known Dead Cells indie game title, and no adversarial flags or brand mismatches are present.

Key signals · 5

Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.

  1. tier1Malicious=0; 16 tier-1 engines (Avast, BitDefender, Kaspersky, ESET-NOD32, Fortinet, F-Secure, Emsisoft, GData, Avira, AVG, DrWeb) all silent

  2. prevalence: common_old, 565 unique submitters, 615 submissions, first seen 2024-08-20 — established benign software

  3. behaviour: 0 offensive MITRE techniques; 9 ambient (T1027, T1056, T1059, T1071, T1082, T1129, T1496, T1497.001, T1574.002) consistent with game runtime

  4. triggeredHeuristics: MalwareTips.Synth.DirectIpC2 fired but is evidence-only; direct-IP contact to CDNs/update servers is benign for games; no malicious sandbox verdict or contacted-hosts hits corroborate C2 interpretation

  5. filename 'deadcells_gl.exe' matches Dead Cells game executable; no adversarial flags; no brand mismatch

Points in its favour
  • 16 tier-1 antivirus engines (Avast, AVG, Avira, BitDefender, DrWeb, Emsisoft, ESET-NOD32, F-Secure, Fortinet, GData, Kaspersky) all report clean
  • Common_old prevalence: 615 submissions, 565 unique sources, 678 days without malicious consensus
  • Zero offensive MITRE techniques; 9 ambient techniques consistent with game runtime and anti-cheat systems
  • No malicious sandbox verdict; no dropped malicious children; no contacted malicious hosts
  • Filename matches known Dead Cells indie game title; no adversarial flags or brand mismatch
What to do

This file is safe. It is the legitimate Dead Cells game executable, confirmed by zero malicious detections across 69 engines and 678 days of benign prevalence. You can download and run it from official sources (Steam, Epic Games Store, GOG, Motion Twin) without concern.

Runtime behaviour

What this file did when executed

This file was detonated in 1 sandbox and its runtime behaviour was observed.

MITRE ATT&CK
9

Adversary techniques mapped to the MITRE ATT&CK framework.

T1027T1056T1059T1071T1082T1129T1496T1497.001T1574.002
Spawned processes
9
$(unnamed)
%SAMPLEPATH%\deadcells_gl.exe
$(unnamed)
%SAMPLEPATH%\06489415f452556dd2fd6e211924934a6d94b440e92afd2add0720d1763c1e4a.exe
$(unnamed)
C:\Windows\System32\UI0Detect.exe
$(unnamed)
C:\Program Files\Google2628_1671701965\bin\updater.exe
$(unnamed)
C:\Program Files\Google2180_1764434623\bin\updater.exe
$(unnamed)
C:\Program Files\Google3888_53288682\bin\updater.exe
$(unnamed)
C:\Program Files\Google3524_1260986720\bin\updater.exe
$(unnamed)
"C:\Users\user\Desktop\deadcells_gl.exe"
+1 more processes captured.
Network activity
16
IP addresses16
  • a83f:8110:bf9a:62ff:c29b:64ff:c39e:66ff
  • 192.168.0.45
  • 23.216.81.152
  • 192.168.0.43
  • 184.27.218.92
  • 192.168.0.1
  • 192.168.0.64
  • 20.99.133.109
  • 23.55.140.42
  • 23.215.176.123
+6 more
Filesystem & mutexes
1
Files written1
  • \Device\ConDrv\\Connect
No researcher-database hits
External threat-intel sources were not collected for this scan.
Signature matches

YARA + heuristic rules that fired

One or more medium-severity heuristic rules matched. Not definitive, but the patterns match known malware behaviour.

1 synthesis
MITRE ATT&CK profile
C2× 1
MalwareTips synthesis rules
Our heuristics on VT data + sandbox behaviour
  • DirectIpC2medium

    Sample contacted 11 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.

    Evidence
    a83f:8110:bf9a:62ff:c29b:64ff:c39e:66ff · 23.216.81.152 · 184.27.218.92
Antivirus engine breakdown

0 detections across 74 engines

0 malicious0 suspicious74 clean
Tier-117 engines
0flag
Top commercial AVs (low FP rate)
Tier-237 engines
0flag
Mainstream engines with mixed FP rates
Low-trust20 engines
0flag
Heuristic / generic-AI engines (high FP rate)
All 74 engines report this file as clean.
Hash 06489415f452… cross-referenced against 74 AV engines via our AV network.
PE forensics

Section entropy & packers

Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.

Unpacked
Section entropy5 sections
.text
6.35
.rdata
5.56
.data
2.23
.rsrc
6.57
.reloc
6.46
0.0Packed threshold 7.28.0
Prevalence

How often this file shows up in the wild

Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.

Common & old
Unique uploaders
565
Hundreds of people have uploaded this — common.
Total submissions
615
Includes repeat uploads by the same source.
First seen by VT
2y ago
Aug 19, 2024
Prevalence quadrant
Rare · New
Targeted malware lives here
Common · New
Just-released software
Rare · Old
Niche or internal tooling
here
Common · Old
Trusted legitimate binaries
File identity

Forensic fingerprint

File biography
First seen (VT)
8/19/2024, 9:56:08 PM
First seen (MalwareBazaar)
Last analysis (VT)
6/23/2026, 1:07:18 AM
Scanned here
6/29/2026, 9:49:33 AM
File name
deadcells_gl.exe
Size
17.24 MB
MIME type
(unknown)
Detected type
Win32 EXE
SHA-256
06489415f452556dd2fd6e211924934a6d94b440e92afd2add0720d1763c1e4a
MD5
bcbfc2b945878d591b8cadd76d0cbafc
SHA-1
5682ca5c8dce80e024896ad0db6e9e2bf3d3054a
PE imphash
6f3a01b9e56529b5162f87102fb6271c
First seen (VT)
8/19/2024, 9:56:08 PM
Last analysis (VT)
6/23/2026, 1:07:18 AM
First scan (MalwareTips)
6/29/2026, 9:49:33 AM
Last scan (MalwareTips)
6/29/2026, 9:49:33 AM
Behavior tags
detect-debug-environmentpeexechecks-user-inputidle
Community classification

Reviews & malware reports(0)

Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.

Loading…
Loading reports…
Files are processed in a streaming pass-through — MalwareTips never stores the binary on its servers. Only the scan result (hash, detections, verdict) is retained so the next person who scans the same file gets an instant answer. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.