Is setup.exe safe?
Single low-trust engine flags Remcos while 74 others stay silent on a signed installer with medium prevalence.
One low-trust engine (VBA32) reports Backdoor.Win32.Remcos; all 17 tier-1 engines are clean. The file is signed by FastCopy Lab with no prior history, shows only generic YARA matches, and has no sandbox malicious verdict.
723d3e50f391dbfc04…61e662401965cfRecommended 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.
One low-trust engine (VBA32) reports Backdoor.Win32.Remcos; all 17 tier-1 engines are clean. The file is signed by FastCopy Lab with no prior history, shows only generic YARA matches, and has no sandbox malicious verdict.
The detection pattern matches the classic low-trust-only false-positive shape: 1/75 engines, tier1Malicious=0, onlyLowTrustFlagging=true. The single detection is a generic Remcos label from VBA32. Signing is verified but the publisher has no historical samples in our data. YARAify hits are generic debugger and IPv6 rules, not Remcos-specific. Sandbox execution produced no malicious verdict and the file shows medium prevalence over 92 days.
What We Detected
75 engines scanned the 5.2 MB signed Win32 EXE. Only VBA32 (low-trust tier) flagged it as Backdoor.Win32.Remcos; the remaining 74 engines, including all 17 tier-1 engines, returned clean. The certificate belongs to FastCopy Lab and is verified, yet the signer has no prior samples recorded.
Threat Behavior
One sandbox run observed T1547.001 (registry run key) and direct-IP contact to 162.159.36.2, but no malicious sandbox verdict was issued. YARAify matched five generic rules focused on debugger checks and IPv6 patterns, none specific to Remcos. No dropped children or persistence indicators beyond the single registry key were recorded.
What To Do Now
The file can be executed with standard precautions. Keep endpoint protection enabled; the single low-trust detection does not override the clean tier-1 consensus and medium-prevalence history.
Where this verdict could be wrong1 caveat
- YARAify returned 13 rules but none are Remcos-specific; generic debugger checks can match legitimate software.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 74/75 engines clean
- All tier-1 engines clean
- Verified digital signature
- Medium prevalence over 92 days
- No malicious sandbox verdict
- Single low-trust engine detection
- Signer has no historical samples
The sample shows the classic low-trust-only false-positive pattern; it can be treated as safe while keeping normal endpoint protection active.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete6 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
- 20MITRE ATT&CK techniques
- 3spawned processes
- 1network contacts
- 7filesystem & 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
723d3e50f391dbfc041efec9de7cadee9cc1d63feba5c1ebf461e662401965cf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\FastCopy5.11.3_installer.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\FastCopy5.11.3_installer.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Connect
\Device\ConDrv\Connect
04Isolated runtime analysis - Written fileObserved
Microsoft Compatibility Appraiser
C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- \Device\ConDrv\Connect
- C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
- C:\ProgramData\Microsoft
- C:\ProgramData\Microsoft\Crypto
- C:\ProgramData\Microsoft\Crypto\RSA
- \Sessions\1\BaseNamedObjects\DBWinMutex
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 6rule hits recorded
- 1 / 75engines flagged
- 799sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The file has a valid code signature from FastCopy Lab.
ProvenanceObservedSourceCode-signing metadataObserved at - 02
5 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceObservedSourceSignature and behavior rulesObserved at - 03
1 of 75 antivirus engines flagged the file, including VBA32.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: setup.exe — 723d3e50f391dbfc041efec9de7cadee9cc1d63feba5c1ebf461e662401965cf
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\FastCopy5.11.3_installer.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\FastCopy5.11.3_installer.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Connect — \Device\ConDrv\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Microsoft Compatibility Appraiser — C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
- Check_OutputDebugStringA_iat
- DebuggerCheck__API
- Detect_all_IPv6_variants
- golang_bin_JCorn_CSC846
- MD5_Constants
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.
Evidence162.159.36.2
1 of 75 engines flagged this file
View all 75 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
- Signature valid: FastCopy Lab
- Size
- 4.9 MB
- Last analyzed
- Aug 18, 2026, 1:40 AM UTC
723d3e50f391dbfc041efec9de7cadee9cc1d63feba5c1ebf461e662401965cfSafety & 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?
Is setup.exe digitally signed?
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.