File scan report

Verdict Suspicious

Analyzed , 22 hours ago

Is setup.exe safe? Treat it as suspicious.

An unsigned installer that 6 of the 68 antivirus engines that checked it flag, several of them identifying it as a software crack, with one malicious sandbox run contradicted by…

Read the whole reasonShow less

Why Suspicious? 6 antivirus engines flag it and one sandbox test run rated it malicious while another found nothing.

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 installer. Obtain the software from its official publisher and keep your security protection enabled.

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.

Antivirus results

6 of 68 flagged

  • Flagged 6
  • No detection 62
  • No result 7
Filesetup.exe5.0 MBSHA-256 7c1d65ed2ad4…f4aef4
  • Code signing Unsigned
  • Test run Completed
  • First seen 7d ago
A sandbox test run rated its behaviour as malicious.

Chapter 02

Why we think so

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

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Six of the 68 antivirus engines that checked it flagged this unsigned installer, including Sophos and Trellix. Malwarebytes labels it a crack-style riskware tool. The sandbox runs disagreed: one returned malicious and another returned clean, and no hostile action was confirmed. Cracked software installers often carry hidden risks.

Where this verdict could be wrong2 caveats
  • The file was submitted by about 1,175 distinct sources and most major antivirus engines (16) reported nothing, which suggests many people run it without a clear malware detection.
  • No high-risk techniques were corroborated in the sandbox runs, and the observed processes look like an ordinary installer unpacking itself.

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
  • 20sandbox rule tags
  • 5spawned processes
  • 0network contacts
  • 18filesystem & 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: Read basic details of the test computer, such as its Windows version.

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

  • Note: Loaded extra code modules while running.

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.

  • Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.

  • Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.

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 5: FileSeen in the test run

      setup.exe

      7c1d65ed2ad431da2d7dfe9a0fca03e00e57588c903f4b6b8ffb1fdc9af4aef4

      Uploaded file
  2. Processes

    What ran

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

      setup.exe

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

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

      setup.tmp

      "C:\Users\<USER>\AppData\Local\Temp\is-FB5G2.tmp\setup.tmp" /SL5="$5006A,4435580,140800,C:\Users\<USER>\Desktop\setup.exe"

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

    Created or changed

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

      setup.tmp

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

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

      _setup64.tmp

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

      Test run
    3. +1 more recorded observation

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

Chapter 04

Technical details

6 of the 68 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: 6 of 68 engines flagged it · 7 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPA, CAPE SandboxCompleteWorth noting: 6 runs: 1 malicious, 1 clean, 4 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete1 contacted host checked
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 6

  • Sophos (major engine)Generic Reputation PUA (PUA)
  • TrellixENS (major engine)Artemis!BEC1842DED3A
  • BkavW32.Malware.FD36495B
  • MalwarebytesRiskWare.Crack
  • Paloaltogeneric.ml
  • VBA32Trojan.Win32.Generic

File fingerprint

Last analyzed
Oct 25, 2026, 2:11 PM UTC
SHA-256
7c1d65ed2ad431da2d7dfe9a0fca03e00e57588c903f4b6b8ffb1fdc9af4aef4
SHA-1
c77abca67086fc7d6cae3f331ef1c2265905f2f1
MD5
bec1842ded3a188e65e35b99bc3c0804

About this file

setup.exe says it is Call of Duty: Modern Warfare 4 Setup (Call of Duty: Modern Warfare 4), 5.0 MB.

Claims to be
Call of Duty: Modern Warfare 4 Setup (Call of Duty: Modern Warfare 4)From the file's own version information, written by whoever built it.
Type and size
Win32 EXE · 5.0 MB
Signer
UnsignedNo code signature.
First seen
Oct 19, 2026On VirusTotal.
Submitted by
1,175 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. 6 of the 68 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 5.0 MB. Its version information says it is “Call of Duty: Modern Warfare 4 Setup” (Call of Duty: Modern Warfare 4). 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 Oct 19, 2026.
How many antivirus engines detected setup.exe?
6 of the 68 antivirus engines that checked it flag setup.exe, including Malwarebytes and Sophos. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already installed setup.exe?
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 7c1d65ed2ad431da2d7dfe9a0fca03e00e57588c903f4b6b8ffb1fdc9af4aef4, and its MD5 is bec1842ded3a188e65e35b99bc3c0804. 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 25, 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.