File scan report
Verdict Malicious
Is setup. exe safe? No, we rate this exact file malicious.
Unsigned installer flagged by four major antivirus engines as crack/hacking tool with offensive MITRE techniques.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Treat as malicious; delete the file and do not run it.
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
12 of 69 flagged
- Flagged 12
- No detection 57
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 2y ago
Chapter 02
Why we think so
4 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
12 of the 69 antivirus engines that checked it flag the file, four of them major, with consistent crack/hacking tool labels. The binary is unsigned, exhibits privilege-escalation and defense-evasion techniques, and matches prior malicious import-table fingerprint.
Four tier-4 engines (GData, Microsoft, Sophos, TrendMicro-HouseCall) label the sample as crack or hacking tool, satisfying the hacktoolConfirmed rule. The file is unsigned despite being an installer, and its sandbox run shows T1134, and techniques. Samples built with the same import table previously received malicious verdicts under the same reason code. While the file is widely seen and long established and drops no malicious files it created, the engine consensus and offensive techniques outweigh those mitigating factors.
What We Detected
12 of the 69 antivirus engines that checked it report the file malicious; four major antivirus engines converge on crack/hacking tool families. The binary is unsigned and contains three MITRE techniques reserved for offensive tooling.
Threat Behavior
Sandbox execution shows direct-IP contact, long sleeps, debug detection, and hosts-file modification. Two contacted hosts (bit.ly, fitgirl-repacks.site) are already flagged suspicious in our cache.
What To Do Now
Do not execute the file. Keep security software enabled and remove the sample from disk. If the file was downloaded from an untrusted source, scan the entire system with current signatures.
Where this verdict could be wrong2 caveats
- The file is widely seen and long established with 2183 submitters indicates wide distribution rather than targeted malware campaign
- droppedChildren.hasMaliciousChild=false and droppedChildren.rollup.malicious=0 across 10 children
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- widely seen and long established prevalence
- no malicious files it created
- unsigned executable
- major hacking tool detections
- offensive MITRE techniques
- suspicious contacted hosts
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- 29sandbox rule tags
- 13spawned 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: Used an unusual way to talk to a server.
Moderate concern: Downloaded a file during the test run.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Sandbox labels we could not confirm (common in safe files too)
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
a3ba1dde7cb3246935a7f5a22fc172ea69a383a35c1e0517db050477e1d33708
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-DPTLI.tmp\setup.tmp" /SL5="$20180,5178042,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-DPTLI.tmp\setup.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-D8UME.tmp\_isetup\_setup64.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
74.125.69.94
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
23.62.209.152
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 29 mapped techniques, every process, file, registry and network entry, 10 dropped files and contacted-host reputation.
Show the technical evidenceChapter 04
Technical details
12 of the 69 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 12
- GData (major engine)Generic.Trojan.PSEB.B43E37
- Microsoft (major engine)HackTool:Win32/Crack!MTB
- Sophos (major engine)Generic Reputation PUA (PUA)
- TrellixENS (major engine)Artemis!02E9F9C05125
- TrendMicro-HouseCall (major engine)PUA.Win32.Gen.TL0101FA26ZZ
- CAT-QuickHealHacktool.Crack
- MalwarebytesRiskWare.Crack
- Paloaltogeneric.ml
File fingerprint
- Last analyzed
- Sep 4, 2026, 2:39 PM UTC
- SHA-256
a3ba1dde7cb3246935a7f5a22fc172ea69a383a35c1e0517db050477e1d33708- SHA-1
32ee22ed8e8efac6f60a53c7a249dc4371ea1c31- MD5
02e9f9c05125aa63280148f6bb875a7e
About this file
setup.exe is a Win32 EXE file of 5.8 MB.
- Type and size
- Win32 EXE · 5.8 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 21, 2024On VirusTotal.
- Submitted by
- 2,183 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Includes every engine result (74), 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.