File scan report
Verdict Suspicious
Is Setup safe? Treat it as suspicious.
Three engines flagged the file with generic trojan/heur labels but no major consensus.
Why Suspicious? 3 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as suspicious pending further analysis or more evidence; avoid running until additional verification confirms legitimacy.
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.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
3 of 69 flagged
- Flagged 3
- No detection 66
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 4mo ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Unsigned status and medium prevalence keep the sample in mixed-signals territory.
The file is unsigned, carries an installer hint, and has medium prevalence with no prior similar-hash verdicts. These factors together produce a borderline mixed-signals profile rather than a clean safe or decisive malicious call.
What We Detected
Sandbox execution revealed MITRE T1055 process injection, T1548 privilege escalation, and T1562.001 defense evasion plus direct contact to 16 external IPs and zero domains.
Threat Behavior
High-entropy sections and direct-IP a control server are consistent with attempts to evade reputation-based blocking.
What To Do Now
Do not execute on production systems. Submit the sample to additional sandboxes or wait for more evidence before trusting it as a legitimate MT5 installer.
Where this verdict could be wrong1 caveat
- Only 3 low-to-mid tier detections with no major consensus leaves room for a rule-based false positive on a new installer.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No major malicious consensus
- No malicious files it created
- Medium prevalence
- Unsigned executable
- Direct-IP a control server to 16 hosts
- High-entropy code sections
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- 24sandbox rule tags
- 2spawned processes
- 21network contacts
- 20filesystem & 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: 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: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
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.
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
6487b6eebf382a3dcf11636c37f23c4fc70af8edc006ccce49e15277e9bdc897
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
mt5setup.exe
"C:\Users\<USER>\Desktop\mt5setup.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
mt5setup.exe
"C:\Users\user\Desktop\mt5setup.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
checkwritepermissions.exe
C:\Program Files\checkwritepermissions.exe
Test run - Evidence 5 of 7: Written fileSeen in the test run
dnsperf.dat
C:\Users\<USER>\AppData\Roaming\MetaQuotes\dnsperf.dat
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
203.29.60.245
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
45.94.185.87
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 24 mapped techniques, every process, file, registry and network entry and 1 dropped file.
Show the technical evidenceChapter 04
Technical details
3 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 3
- BkavW32.Malware.A04F49E2
- GridinsoftTrojan.Heur!.02212123
- MalwarebytesMalware.Heuristic.2108
File fingerprint
- Last analyzed
- Jul 12, 2026, 10:05 AM UTC
- SHA-256
6487b6eebf382a3dcf11636c37f23c4fc70af8edc006ccce49e15277e9bdc897- SHA-1
86b2cbd1616deac523644857ca992b283a4f3f0e- MD5
038a343791555f281e8e6f5e5075978b
About this file
Setup is a Win32 EXE file of 23.3 MB.
- Type and size
- Win32 EXE · 23.3 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jun 18, 2026On VirusTotal.
- Submitted by
- 2 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Includes every engine result (74), 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 safe, or is it malware?
What is Setup?
How many antivirus engines detected Setup?
I already downloaded and installed Setup — what should I do?
What is the SHA-256 hash of Setup?
How up to date is this analysis of Setup?
Community
Member reviews and reports for this exact file hash.