Is game.CT safe?
No detections appeared across 74 engines, while extensive historical prevalence and absent curated threat-intelligence matches strongly support a benign XML data file.
None of 74 antivirus engines detected this 1,103-byte XML file, including 17 high-trust engines. It has also accumulated 7,625 submissions from 3,629 sources without a curated malware or YARA match, although no completed runtime observation is available.
a7cb166e2ab42c92cd…85232ca5660bfcRecommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened 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.
None of 74 antivirus engines detected this 1,103-byte XML file, including 17 high-trust engines. It has also accumulated 7,625 submissions from 3,629 sources without a curated malware or YARA match, although no completed runtime observation is available.
Static scanning produced zero malicious or suspicious results across 74 engines, with all 17 reporting high-trust engines remaining silent. The file is an established 1,103-byte XML document submitted 7,625 times by 3,629 sources, which weighs strongly against a newly distributed threat. Curated intelligence checks found no MalwareBazaar, CIRCL, or YARAify match. Code signing is not meaningful for this file type, so its absence does not count against it. No sandbox execution or complete contacted-host reputation check is available, limiting conclusions about how another program might interpret its contents.
What We Detected
None of 74 antivirus engines flagged the file as malicious or suspicious. The silent set includes 17 high-trust engines, such as Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast. Curated intelligence checks also returned no MalwareBazaar, CIRCL, or YARAify match.
Threat Behavior
The sample is a small 1,103-byte XML data file rather than an executable, and code signing is not applicable. It has been submitted 7,625 times from 3,629 sources over 389 days. No completed runtime observation is available, and contacted-host reputation was not fully checked, so no claims are made about runtime or network behavior.
What To Do Now
Normal handling is appropriate if the file came from an expected source and is opened only with trusted software. Keep endpoint protection enabled, and avoid importing it into an untrusted or outdated application if its origin is uncertain.
Where this verdict could be wrong2 caveats
- behaviour=null, so no completed runtime execution was available to verify what an application may do when importing this XML file.
- contactedHosts=null, so no complete reputation assessment exists for the domains or hosts mentioned only in community annotations.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/74 engines reported malicious or suspicious findings.
- 17 high-trust engines reported no detection.
- 7,625 submissions from 3,629 sources indicate substantial historical prevalence.
- No MalwareBazaar, CIRCL, or YARAify threat match.
- XML format makes absent code signing neutral.
- No completed runtime observation is available.
- No complete contacted-host reputation result is available.
The file can be handled normally when obtained from an expected source and imported with trusted, updated software. Keep endpoint protection enabled and verify the source if the file arrived unexpectedly.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 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
- 0 / 74engines flagged
- 3,629sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 3,629 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- game.CT
- Format
- XML
- Code signing
- Not applicable to this file type
- Size
- 1.1 KB
- Last analyzed
- Sep 26, 2026, 2:48 AM UTC
a7cb166e2ab42c92cd92b35785ba08c600b8d552349f14bb8a85232ca5660bfcSafety & 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
Open it only when its sender or download source is one 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 game.CT safe?
What is game.CT?
How many antivirus engines detected game.CT?
What is the SHA-256 hash of game.CT?
Is it safe to open game.CT?
How up to date is this analysis of game.CT?
Community
Member reviews and reports for this exact file hash.