Is Setup.exe safe?
Only 1 of 73 engines flagged this older installer, while all 18 tier-1 engines remained silent and runtime analysis found no offensive behavior.
APEX alone flagged the executable, while 72 of 73 engines did not, including all 18 tier-1 engines. One sandbox run found no offensive techniques or malicious runtime verdict, though the unsigned file made four direct-IP contacts whose reputation was not checked completely.
96d9b8d315460f5c61…5a7d8f79f899afRecommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
APEX alone flagged the executable, while 72 of 73 engines did not, including all 18 tier-1 engines. One sandbox run found no offensive techniques or malicious runtime verdict, though the unsigned file made four direct-IP contacts whose reputation was not checked completely.
The detection pattern is characteristic of a low-trust false positive: APEX was the only one of 73 engines to flag the file, and it supplied no named malware family. All 18 tier-1 engines remained silent, including Kaspersky, BitDefender, ESET-NOD32, Avast, and Fortinet. One completed sandbox run recorded 13 installer-common techniques but no offensive techniques, persistence indicators, or malicious sandbox verdict. Six dropped files were inspected without a malicious child finding, although their individual verdicts remain unknown. The main concern is direct communication with four IP addresses; because no complete host-reputation result is available, those contacts cannot be characterized as benign. The lack of a digital signature also limits publisher verification, but these concerns do not outweigh the broad engine agreement and runtime findings.
What We Detected
APEX was the sole detector among 73 antivirus engines and returned only a generic “Malicious” label. All 18 tier-1 engines were silent, including Kaspersky, BitDefender, ESET-NOD32, Avast, and Fortinet, and no engine family consensus exists.
Threat Behavior
One completed sandbox run observed installer-like file creation and 13 ambient techniques, with no offensive techniques, persistence indicators, or malicious sandbox verdict. Six dropped children were inspected without a malicious-child finding, but their individual classifications remain unknown. The sample contacted four IP addresses directly; no complete host-reputation result is available, so those contacts remain an unresolved limitation rather than evidence of clean networking.
What To Do Now
Use the file only if it came from the expected game vendor or another trusted distribution channel. Keep endpoint protection enabled, verify the download source, and avoid running it if its origin cannot be established or if unexpected network activity appears.
Where this verdict could be wrong4 caveats
- The executable is unsigned: signing.applicable=true and signing.signed=false, so publisher identity cannot be verified.
- MalwareTips.Synth.DirectIpC2 fired for four direct-IP contacts, and contactedHosts=null leaves their reputation unresolved.
- similarHashes[0].verdict is suspicious, but matchKind=imphash and signerMatchesSubject=false make this weak similarity evidence.
- All 6 inspected dropped children have unknown verdicts, despite droppedChildren.hasMaliciousChild=false.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of 73 engines detected the file
- All 18 tier-1 engines remained silent
- No offensive techniques or malicious sandbox verdict in one completed run
- No malicious dropped child among 6 inspected
- No YARAify, CIRCL malicious, or MalwareBazaar hit
- Unsigned Win32 executable with no verifiable publisher identity
- Four direct-IP contacts with no complete host-reputation cross-check
- Six dropped children remain individually unclassified
- Generic APEX detection from one low-trust engine
If the installer came from an expected, trusted source, retain normal endpoint-protection monitoring while using it. Otherwise, obtain a fresh copy from the official release channel rather than relying on this unsigned executable.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 73 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial4 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 13MITRE ATT&CK techniques
- 4spawned processes
- 4network contacts
- 30filesystem & mutex artifacts
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.exe
96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af.exe
02Isolated runtime analysis - ProcessObserved
Observed process
%USERPROFILE%\AppData\Local\Temp\is-2B202.tmp\96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af.tmp
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
996E.tmp
C:\Documents and Settings\Administrator\Local Settings\Temp\is-FAMTP.tmp\996E.tmp
04Isolated runtime analysis - Written fileObserved
96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af.tmp
C:\Users\<USER>\AppData\Local\Temp\is-5RFMR.tmp\96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:0:0:e600:0:0:0
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.99.184.37
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.
- a83f:8110:0:0:e600:0:0:0
- 20.99.184.37
- 131.253.33.203
- 23.216.147.64
- C:\Documents and Settings\Administrator\Local Settings\Temp\is-FAMTP.tmp\996E.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-5RFMR.tmp\96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af.tmp
- C:\Program Files (x86)\Wizards of the Coast LLC
- C:\Program Files (x86)\Wizards of the Coast LLC\Magic The Gathering - Duels of the Planeswalkers 2013
- C:\Program Files (x86)\Wizards of the Coast LLC\Magic The Gathering - Duels of the Planeswalkers 2013\Movies
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1008.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1289.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER12D8.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER32D2.tmp.WERInternalMetadata.xml
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- c5177fdc6031728e1014…74ab28Never scannednever seen before
- c151f7d13c49ff483b3b…1c31c2Never scannednever seen before
- 4dc09bac0613590f1fac…7e74a2Never scannednever seen before
- e19781aabe466dd8779c…d63c64Never scannednever seen before
- a4c86fc4836ac728d7bd…95fd81Never scannednever seen before
- 9884e9d1b4f8a873ccbd…360d87Never 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.
- 1rule hit recorded
- 1 / 73engines flagged
- 29sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 73 antivirus engines flagged the file, including APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 30 times from 29 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Setup.exe — 96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — %SAMPLEPATH%\96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — %USERPROFILE%\AppData\Local\Temp\is-2B202.tmp\96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: 996E.tmp — C:\Documents and Settings\Administrator\Local Settings\Temp\is-FAMTP.tmp\996E.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af.tmp — C:\Users\<USER>\AppData\Local\Temp\is-5RFMR.tmp\96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899af.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: a83f:8110:0:0:e600:0:0:0 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 20.99.184.37 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The 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.
Evidencea83f:8110:0:0:e600:0:0:0 · 20.99.184.37 · 131.253.33.203
1 of 73 engines flagged this file
View all 73 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.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 1.1 MB
- Last analyzed
- Sep 15, 2026, 3:55 PM UTC
96d9b8d315460f5c613192d642109fed9287aecab220a1e3615a7d8f79f899afSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Install it only when it came from the developer's official site or an official app store.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Setup.exe safe?
What is Setup.exe?
How many antivirus engines detected Setup.exe?
What is the SHA-256 hash of Setup.exe?
Is it safe to install Setup.exe?
How up to date is this analysis of Setup.exe?
Community
Member reviews and reports for this exact file hash.