File scan report

Verdict Suspicious

Analyzed , 5 days ago

Is setup.exe safe? Treat it as suspicious.

Unsigned Inno Setup installer that engines label as a cracked or repacked software package; 3 of the 71 antivirus engines that checked it flag it, and a sandbox run returned…

Read the whole reasonShow less

Why Suspicious? 3 antivirus engines flag it and a sandbox test run rated it as risky.

Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.

Don't install it until you know where it came from

Do not run this cracked installer; get the software from its official source. If it was already run, keep protection enabled and perform a full system scan.

What to do now4 steps

Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.

What to do

  1. Don't install it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.

If you already installed it

  1. Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.

Not sure what to do?

Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.

Paste this report's link in your topic so helpers can see what was found.

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

3 of 71 flagged

  • Flagged 3
  • No detection 68
  • No result 4
Filesetup.exe6.2 MBSHA-256 15c1b532a554…3a0c43
  • Code signing Unsigned
  • Test run Completed
  • First seen 11mo ago
A sandbox test run rated its behaviour as malicious.

Chapter 02

Why we think so

5 points against it and 4 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

This installer looks like a repacked or cracked software package. 3 of the 71 antivirus engines that checked it flag it with crack and riskware labels, including one major antivirus engine. Our sandbox runs flagged it as malicious, but recorded only installer-style activity with no named injection target. Cracked installers are a common route for bundled unwanted or harmful software.

Where this verdict could be wrong2 caveats
  • A sandbox run returned malicious and no run contradicted it, so hidden payload behaviour cannot be fully excluded even though no high-risk technique or injection target was recorded.
  • The file is widely submitted (over 600 sources over nearly a year) with only 3 detections. That fits a common repacked game or software installer rather than a stealer or trojan.

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

6 sources checked · all complete. See every source

Chapter 03

What it did in our test

It ran in 6 isolated tests; 1 test environment rated what it did as risky.

Test run summary

Capture complete
  • 6isolated sandbox runs
  • 16sandbox rule tags
  • 8spawned processes
  • 1network contact
  • 25filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Checked whether it was running on a test computer.

  • Note: Read the user name of the test computer.

  • Note: Talked to servers over the internet during the test run.

  • Note: Read basic details of the test computer, such as its Windows version.

  • Note: Looked through folders on the test computer (most installers do this).

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 6: FileSeen in the test run

      setup.exe

      15c1b532a55475cc93e05c75b9cc4362ea0b230a57f9019b8da52960903a0c43

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 6: ProcessSeen in the test run

      setup.exe

      "C:\Users\<USER>\Desktop\setup.exe"

      Test run
    2. Evidence 3 of 6: ProcessSeen in the test run

      setup.tmp

      "C:\Users\<USER>\AppData\Local\Temp\is-NOV5Q.tmp\setup.tmp" /SL5="$1C0074,5651573,140800,C:\Users\<USER>\Desktop\setup.exe"

      Test run
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 6: Written fileSeen in the test run

      setup.tmp

      C:\Users\<USER>\AppData\Local\Temp\is-NOV5Q.tmp\setup.tmp

      Test run
    2. Evidence 5 of 6: Written fileSeen in the test run

      _setup64.tmp

      C:\Users\<USER>\AppData\Local\Temp\is-UG6HL.tmp\_isetup\_setup64.tmp

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    1
    1. Evidence 6 of 6: Contacted hostWorked out from other results

      aka.ms

      Older reputation report (safe), not counted as current evidence.

      Contacted-host cross-check

6 facts from the test run. See the full activity list.

Chapter 04

Technical details

3 of the 71 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 3 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPA, CAPE SandboxCompleteRisk signal: 6 runs: 1 malicious, 5 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete5 contacted hosts checked Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 3

  • GData (major engine)Generic.Trojan.PSEB.QWW5J3
  • MalwarebytesRiskWare.Crack
  • WebrootWin.Riskware.Repack

File fingerprint

Last analyzed
Oct 21, 2026, 8:45 AM UTC
SHA-256
15c1b532a55475cc93e05c75b9cc4362ea0b230a57f9019b8da52960903a0c43
SHA-1
a001b3fc0c6e60c6f35753c6960d460141591e1b
MD5
5e784411ed9fa0d1b2a6728e1bff569a

About this file

setup.exe says it is Kingdom Come: Deliverance II Setup (Kingdom Come: Deliverance II), 6.2 MB.

Claims to be
Kingdom Come: Deliverance II Setup (Kingdom Come: Deliverance II)From the file's own version information, written by whoever built it.
Type and size
Win32 EXE · 6.2 MB
Signer
UnsignedNo code signature.
First seen
Nov 14, 2025On VirusTotal.
Submitted by
643 distinct sources
Packer
None detected
Entropy
5.55 of 8

First scanned

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is setup.exe safe, or is it malware?
setup.exe is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 3 of the 71 antivirus engines that checked it flag it. Don't install it unless you're sure where it came from. If you need the software, download a fresh installer from the developer's own website.
What is setup.exe?
setup.exe is a software installer, about 6.2 MB. Its version information says it is “Kingdom Come: Deliverance II Setup” (Kingdom Come: Deliverance II). Version information is written by whoever built the file, so it is a claim, not proof of who made it. VirusTotal first saw it on Nov 14, 2025.
How many antivirus engines detected setup.exe?
3 of the 71 antivirus engines that checked it flag setup.exe, including Malwarebytes and G DATA. We weigh which engines flagged it and what else the scan found, not just the count.
I already downloaded and installed setup.exe — what should I do?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of setup.exe?
The SHA-256 fingerprint of setup.exe is 15c1b532a55475cc93e05c75b9cc4362ea0b230a57f9019b8da52960903a0c43, and its MD5 is 5e784411ed9fa0d1b2a6728e1bff569a. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of setup.exe?
This report reflects the scan on Oct 21, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Other files people checked with the same name. A matching name does not make two files the same: only the SHA-256 fingerprint identifies a file.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.