File scan report
Verdict Suspicious
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.
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
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
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
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.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
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
- Code signing Unsigned
- Test run Completed
- First seen 7d ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
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.
Six of the 68 antivirus engines that checked it flagged the file. Two of them are major antivirus engines, but both used generic reputation labels and named no malware family. Malwarebytes calls it a crack, which matches the file's overall threat labelling. The installer is unsigned, so no publisher vouches for it. The sandbox runs showed a typical installer unpacking helper libraries, and a malicious verdict from one run was offset by a clean one, with no injection target or hostile network contact found. Although the file has many submitters, that does not establish it as safe given the crack labelling.
What We Detected
6 of the 68 antivirus engines that checked it flagged this unsigned installer, first seen on Oct 19, 2026. Sophos reports a reputation-based potentially unwanted program, Trellix reports a generic detection, and Malwarebytes labels it riskware associated with a software crack. No engine named a malware family, and no reference database lists the file.
Threat Behavior
The sandbox runs show an installer that extracts a temporary setup program and helper libraries. One run returned a malicious verdict and another returned a clean one. No process injection target, persistence or hostile network contact was confirmed.
What To Do Now
Avoid running cracked or unofficial installers. Get the software from its official publisher instead. If you have already run this file, scan your system with up-to-date security software and keep your protection enabled.
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.
- Many distinct sources submitted the file.
- No corroborated high-risk behaviour or malicious network contact was observed.
- No listing in malware reference databases.
- Engines label the file as a software crack or riskware.
- Two major antivirus engines flagged it.
- The installer carries no digital signature.
- One sandbox run returned a malicious verdict.
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.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
setup.exe
7c1d65ed2ad431da2d7dfe9a0fca03e00e57588c903f4b6b8ffb1fdc9af4aef4
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
setup.exe
"C:\Users\<USER>\Desktop\setup.exe"
Test run - 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 - +1 more recorded observation
- 2
Files
Created or changed
- 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 - 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 - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 20 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 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.
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
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is setup.exe safe, or is it malware?
What is setup.exe?
How many antivirus engines detected setup.exe?
What should I do if I already installed setup.exe?
What is the SHA-256 hash of setup.exe?
How up to date is this analysis of setup.exe?
Community
Member reviews and reports for this exact file hash.