Threat LensFile scan report

Is CardWarsKingdom.exe safe?

Verdict
Safe

No antivirus engine detected this executable, and its completed sandbox run found no offensive behavior, though unsigned status and unchecked direct-IP traffic warrant source verification.

All 75 antivirus engines reported no detection, including 17 high-trust engines, and one completed sandbox run produced no malicious verdict or offensive technique. The executable is unsigned and contacted one IP whose reputation was not fully checked, so obtain it from an official source and keep endpoint protection enabled.

Run with normal care

Use the file only if it came from the official distribution channel, and keep endpoint protection enabled. Recheck the hash if new network behavior or antivirus detections emerge.

Read the full analysis
Saved file evidenceAntivirus consensus
0of 75 flagged
Flagged 0No detection 75
Digital specimenCardWarsKingdom.exe92bab7933b79c313e5…c268d147a3b579
Size656.0 KB
Code signingUnsigned
SandboxRuntime complete
First seen3d ago
Evidence2 priority signals
0 of 75 antivirus engines flagged the file.

Recommended next actions

01

Before running

Run it only when it came from the developer's official site or another source you independently trust.

02

If you already ran it

Keep normal device protection enabled and stop if the file behaves unexpectedly.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

87%Confidence
Very high
Analyst conclusion

All 75 antivirus engines reported no detection, including 17 high-trust engines, and one completed sandbox run produced no malicious verdict or offensive technique. The executable is unsigned and contacted one IP whose reputation was not fully checked, so obtain it from an official source and keep endpoint protection enabled.

Where this verdict could be wrong3 caveats
  • signing.signed=false and the file was first submitted only 4 days ago, so no authenticated publisher or long-established reputation supports it.
  • The sandbox contacted 162.159.36.2 directly, and contactedHosts=null means no complete host-reputation result is available.
  • The three prior safe files are imphash-only matches with signerMatchesSubject=false, so they may merely share a build framework.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

Use the file only if it came from the official distribution channel, and keep endpoint protection enabled. Recheck the hash if new network behavior or antivirus detections emerge.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    0 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    1 runtime contact was observed without a completed reputation cross-check.

  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 9MITRE ATT&CK techniques
  • 1spawned processes
  • 1network contacts
  • 0filesystem & mutex artifacts
Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & 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.

  1. Recovery step 01

    Run it only when it came from the developer's official site or another source you independently trust.

  2. Recovery step 02

    A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.

  3. 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.

6 evidence-based answers
Is CardWarsKingdom.exe safe?
Evidence-based answer
CardWarsKingdom.exe appears safe. 0 of 75 antivirus engines flagged it. Run it only when it came from the developer's official site or another source you independently trust.
What is CardWarsKingdom.exe?
Evidence-based answer
CardWarsKingdom.exe is a Windows executable program, about 656 KB. Our analysis did not identify a verdict-driving threat signal. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
How many antivirus engines detected CardWarsKingdom.exe?
Evidence-based answer
None — 0 of 75 antivirus engines flagged CardWarsKingdom.exe. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
What is the SHA-256 hash of CardWarsKingdom.exe?
Evidence-based answer
The SHA-256 hash of CardWarsKingdom.exe is 92bab7933b79c313e54273108e77e45288c8cc9e4691c9c9c0c268d147a3b579, and its MD5 is e3048004c458e570e9d6416517e62d10. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
Is it safe to run CardWarsKingdom.exe?
Evidence-based answer
Based on the recorded evidence, CardWarsKingdom.exe has a low observed risk. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it, verify the source and the exact hash before overriding the warning.
How up to date is this analysis of CardWarsKingdom.exe?
Evidence-based answer
This report reflects the scan run on October 7, 2026. Because a file's hash never changes, the identity of CardWarsKingdom.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. 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.