File scan report
Verdict Malicious
Is setup. exe safe? No, we rate this exact file malicious.
The executable is identified as a crack or hacking tool by Microsoft, Sangfor, and Alibaba, with 13 of the 71 antivirus engines that checked it flagging it overall.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Keep it only if you installed it on purpose for security testing. Otherwise delete it and run a full antivirus scan.
What to do now4 steps
This is a hacking tool. It is risky to keep and run, but finding it is not by itself a sign that the device is infected.
What to do
Don't install it unless you got it on purpose for security testing on systems you own. Delete it, then empty the Recycle Bin.
If you didn't put it on the device yourself, delete it and run a full antivirus scan: something else may have brought it.
Tools like this often come with cracked or pirated software. If it came that way, treat the whole download as unsafe and scan everything it installed.
If you already installed it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
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
13 of 71 flagged
- Flagged 13
- No detection 58
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
7 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Thirteen of the 71 antivirus engines that checked it flagged the sample, including five major detections and a confirmed hacking tool designation. Microsoft, Sangfor, and Alibaba independently use crack or hacking tool labels, which is stronger than an isolated generic heuristic. One sandbox recorded five offensive MITRE techniques, including process injection and impairing defenses, although it did not issue a formal malware verdict. Four researcher YARA rules also matched, including shellcode and suspicious TLS-section rules. The executable is unsigned, and the available host-reputation check covered only aka.ms rather than all observed IP contacts. Broad prevalence and several non-detecting engines are counter-signals, but they do not outweigh the confirmed hacking tool labeling and corroborating behavior.
What We Detected
13 of the 71 antivirus engines that checked it flagged this unsigned Win32 executable. Microsoft reported HackTool:Win32/Crack!MTB, Sangfor reported Hacktool.Win32.Crack.V8bi, and Alibaba also identified a crack tool. Five major antivirus engines detected it, although they did not establish a strong consensus on one conventional malware family.
Threat Behavior
Four researcher YARA rules matched, including shellcode, HUNTING_SUSP_TLS_SECTION, and pe_detect_tls_callbacks. No malicious child was confirmed, but all 10 inspected children lack final verdicts. The host-reputation lookup covered aka.ms only and did not cover every observed IP, so no complete network-reputation conclusion is available.
What To Do Now
Do not execute or install this file. Keep antivirus and security software enabled, quarantine or delete the sample, and obtain the intended software from its official publisher. If it already ran, perform a full system scan and review the device for credential access, defense changes, and unexpected processes.
Where this verdict could be wrong5 caveats
- 12 major antivirus engines did not flag the file, including BitDefender, ESET-NOD32, Fortinet, Avast, and Avira.
- No sandbox returned a malicious verdict, although one sandbox recorded five offensive techniques.
- droppedChildren inspected 10 children and found no confirmed malicious child, but all 10 child verdicts remain unknown.
- A count of 1214 distinct submitters and a count of 1410 submissions indicate the sample is well established rather than newly observed.
- contactedHosts found aka.ms safe, but it inspected only 1 host and did not cover the other observed IP contacts.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 12 major antivirus engines did not flag the sample
- No formal malicious sandbox verdict was recorded
- No inspected child was confirmed malicious
- The sample has 1,214 unique submitters and 1,410 submissions
- No brand mismatch was detected
- 13/71 antivirus detections
- Five major antivirus engines flagged the sample
- Confirmed crack or hacking tool labeling
- Unsigned Win32 executable with no signer history
- Five offensive MITRE techniques observed
- Four YARA rules matched
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 35sandbox rule tags
- 8spawned processes
- 7network contacts
- 40filesystem & 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.
Moderate concern: Hid files or windows on the test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
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 recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change 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.
Threat context
How hacking tools are used
Hacking tools are programs that can switch off security software, test passwords or attack other computers. Security professionals use them on purpose; criminals also bundle them with malware.
Bottom line:Keep it only if you installed it on purpose, and check how it got onto the device if you didn't.
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 7: FileSeen in the test run
setup.exe
c4d4e4552be6befc6372440ce115ca9580a205091f8dfbc0669c06cf44c0bc30
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
setup.exe
"C:\Users\<USER>\Desktop\setup.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
setup.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-R6B25.tmp\setup.tmp" /SL5="$4006A,5482592,140800,C:\Users\<USER>\Desktop\setup.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-R6B25.tmp\setup.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-FGPF3.tmp\_isetup\_setup64.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
96.7.170.175
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
23.198.74.242
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 35 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
13 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 13
- GData (major engine)Generic.Trojan.PSEB.7GDA12
- Ikarus (major engine)PUA.Generic
- Microsoft (major engine)HackTool:Win32/Crack!MTB
- Sophos (major engine)Generic Reputation PUA (PUA)
- TrendMicro-HouseCall (major engine)PUA.Win32.Gen.TL0101H726ZX
- AlibabaHackTool:Win32/Crack.ff29a8db
- DeepInstinctMALICIOUS
- MalwarebytesRiskWare.Crack
File fingerprint
- Last analyzed
- Sep 9, 2026, 12:06 AM UTC
- SHA-256
c4d4e4552be6befc6372440ce115ca9580a205091f8dfbc0669c06cf44c0bc30- SHA-1
75135bb085f47d60f9db3faa258ce96dfdcf76d2- MD5
a00ac7b5804c18b194685ea737c0d7af
About this file
setup.exe is a Win32 EXE file of 6.1 MB.
- Type and size
- Win32 EXE · 6.1 MB
- Signer
- UnsignedNo code signature.
- First seen
- Feb 3, 2025On VirusTotal.
- Submitted by
- 1,214 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Includes every engine result (75), 5 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is setup.exe malware?
What is setup.exe?
How many antivirus engines detected setup.exe?
I already downloaded and installed setup.exe — what should I do?
How do I remove setup.exe?
What kind of program is 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.