Is Setup safe?
Suspicious file assessment
1 high-confidence signature or behavior rule matched this file.
6487b6eebf382a3dcf…e15277e9bdc897Recommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial16 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 24MITRE ATT&CK techniques
- 9spawned processes
- 40network contacts
- 20filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
Setup
6487b6eebf382a3dcf11636c37f23c4fc70af8edc006ccce49e15277e9bdc897
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\mt5setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
checkwritepermissions.exe
C:\Program Files\checkwritepermissions.exe
04Isolated runtime analysis - Written fileObserved
dnsperf.dat
C:\Users\<USER>\AppData\Roaming\MetaQuotes\dnsperf.dat
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
203.29.60.245
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
45.94.185.87
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 203.29.60.245
- 45.94.185.87
- 36.255.79.249
- 194.164.179.33
- 203.29.60.248
- 104.166.145.86
- 88.212.232.156
- 148.113.1.241
- 156.38.206.18
- 45.94.185.85
- https://36.255.76.152/
- https://36.255.77.152/
- https://45.94.184.87/
- https://203.29.60.248/cdn/files/mt5/cdn.txt
- https://203.29.60.248/
- https://36.255.76.150/cdn/files/mt5/cdn.txt
- C:\Program Files\checkwritepermissions.exe
- C:\Users\<USER>\AppData\Roaming\MetaQuotes\dnsperf.dat
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Users\user\AppData\Roaming\MetaQuotes
- C:\Users\user\AppData\Roaming\MetaQuotes\WebInstall
- C:\Users\<USER>\AppData\Roaming\MetaQuotes\WebInstall
- C:\Program Files\checkwritepermissions.exe
- C:\Users\user\AppData\Local\Temp\0013461513
- C:\Users\user\AppData\Local\Temp\0164771190
- C:\Users\user\AppData\Local\Temp\0361540775
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 9d96c5844aa0ff4150fa…5959abNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 3 / 74engines flagged
- 2sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
3 of 74 antivirus engines flagged the file, including Bkav and Gridinsoft.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 2 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Setup — 6487b6eebf382a3dcf11636c37f23c4fc70af8edc006ccce49e15277e9bdc897
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\mt5setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: checkwritepermissions.exe — C:\Program Files\checkwritepermissions.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: dnsperf.dat — C:\Users\<USER>\AppData\Roaming\MetaQuotes\dnsperf.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 203.29.60.245 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 45.94.185.87 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHostSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence203.29.60.245 · 45.94.185.87 · 36.255.79.249
3 of 74 engines flagged this file
View all 74 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Setup
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 22.2 MB
- Last analyzed
- Jul 12, 2026, 10:05 AM UTC
6487b6eebf382a3dcf11636c37f23c4fc70af8edc006ccce49e15277e9bdc897Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Setup safe, or is it malware?
What is Setup?
How many antivirus engines detected Setup?
I already downloaded and opened Setup — what should I do?
How do I remove Setup?
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.