Is Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe safe?
Two tier-1 engines detect generic trojan activity, but weak family agreement and absent runtime evidence prevent a confirmed XWorm attribution.
Five of 75 engines flagged this newly observed, unsigned executable, including Kaspersky and Microsoft. Those two high-trust detections warrant caution, although most engines remained silent and only Zillya identified XWorm, leaving the exact malware family unresolved.
88bb9857462187e794…536f7f7c422f65Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
Five of 75 engines flagged this newly observed, unsigned executable, including Kaspersky and Microsoft. Those two high-trust detections warrant caution, although most engines remained silent and only Zillya identified XWorm, leaving the exact malware family unresolved.
Kaspersky and Microsoft independently flagged the sample, producing two tier-1 malicious votes among 75 engines. Their labels are generic or machine-learning based, while the XWorm identification comes from Zillya alone, so no tier-1 family consensus exists. The executable is unsigned and has only one recorded submission, leaving no established publisher or distribution history. Fourteen tier-1 engines reported no detection, which is meaningful counter-evidence but does not neutralize two independent high-trust alerts. No completed sandbox observation or comprehensive contacted-host reputation check is available, so execution and network behavior remain unverified.
What We Detected
Five of 75 antivirus engines flagged the executable. Kaspersky reported HEUR:Trojan.Win32.Generic and Microsoft reported Trojan:Win32/Wacatac.B!ml, while Zillya named Backdoor.XWorm.Win32.3294. Because the high-trust engines do not agree on a family, the XWorm attribution remains unconfirmed.
Threat Behavior
No completed sandbox observation is available, so there is no verified runtime evidence of persistence, credential theft, command-and-control traffic, or other backdoor activity. A complete reputation check of contacted hosts is also unavailable. Static PE analysis did not identify packed or high-entropy executable code, but that does not override the antivirus detections.
What To Do Now
Do not run the executable on a production or personal system. Keep endpoint protection enabled, quarantine the file, and obtain the software from the official game platform or publisher before comparing hashes or signatures.
Where this verdict could be wrong4 caveats
- 14 tier-1 engines reported no detection, including BitDefender, ESET-NOD32, Fortinet, and Avast.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false, although absent matches do not prove benignity.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false provide no static indication of packed executable code.
- The XWorm name appears only in Zillya's detection; engines.tier1FamilyConsensus.strong=false.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 14 tier-1 engines reported no detection.
- No strong tier-1 family consensus was present.
- YARAify, MalwareBazaar, and CIRCL returned no matching intelligence.
- Static PE analysis found neither likely packing nor high-entropy code.
- Two independent tier-1 engines flagged the executable.
- The executable is unsigned despite code signing being applicable.
- The file was first observed today and has only one recorded submission.
- Zillya identified Backdoor.XWorm.Win32.3294.
- No completed runtime observation is available.
- No comprehensive contacted-host reputation result is available.
Quarantine the file and avoid executing it unless its hash can be verified against an official publisher or platform release. Keep antivirus and endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete5 of 75 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 5 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
5 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
5 of 75 engines flagged this file
View all 75 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
Barely seen in the wild and first surfaced recently. 5 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 62.0 MB
- Last analyzed
- Sep 12, 2026, 2:16 PM UTC
88bb9857462187e794de2769a88c0374510870d1bdff3497e5536f7f7c422f65Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe safe, or is it malware?
What is Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe?
How many antivirus engines detected Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe?
What should I do if I already ran Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe?
How do I remove Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe?
What kind of malware is Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe?
What is the SHA-256 hash of Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe?
How up to date is this analysis of Chrono_Cross_Radical_Dreamers_Edition_HUN_Steam.exe?
Community
Member reviews and reports for this exact file hash.