Is ScreenConnect.ClientSetup.exe safe?
Signed ConnectWise remote-admin installer flagged by three tier-1 engines with no prior signer history.
Three tier-1 engines label the file as remote-admin software and the sample is brand new with no signer history. Sandbox execution produced no malicious verdict and no complete contacted-host reputation result was available were contacted.
96f9de130643657d05…a2f2dcf9a28d30Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
Three tier-1 engines label the file as remote-admin software and the sample is brand new with no signer history. Sandbox execution produced no malicious verdict and no complete contacted-host reputation result was available were contacted.
The file carries a verified ConnectWise signature yet lacks any historical samples from that signer. Three tier-1 engines converge on a remote-admin family label, meeting the hacktoolConfirmed threshold. However, the single sandbox run returned no malicious verdict, contacted-no complete contacted-host reputation result was available, and the direct-IP heuristic notes that legitimate installers can exhibit the same traffic pattern. The combination of strong tier-1 consensus on a dual-use tool with zero prior reputation places the sample in mixed-signal territory.
What We Detected
11 of 75 engines flagged the sample; three tier-1 engines (DrWeb, ESET-NOD32, Kaspersky) agreed on a remote-admin family. The binary is signed by ConnectWise and verified, but the signer has no recorded history in our database. Sandbox execution wrote several MSI-related files and contacted five external IPs, none of which appear in our malicious-host cache.
Threat Behavior
The observed MITRE technique T1562.001 (impair defenses) is consistent with remote-administration tooling that must disable security prompts. No persistence mechanisms, registry modifications, or dropped malicious children were recorded. The direct-IP heuristic fired, but the rule itself notes that legitimate installers can produce the same traffic.
What To Do Now
If this installer was obtained directly from the vendor’s official site, treat it as expected remote-admin software. Otherwise, verify the download source and keep endpoint protection enabled. Re-scan after any vendor update to confirm the signature remains valid.
Where this verdict could be wrong1 caveat
- signerStats.found=false — no historical samples for ConnectWise signer to confirm clean track record.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- verified ConnectWise signature
- sandbox returned no malicious verdict
- no malicious dropped children or contacted hosts
- rare_new with zero prior signer history
- tier-1 remote-admin consensus
- direct-IP traffic without domain resolution
Verify the installer came from ConnectWise’s official channel; if the source is trusted, the file is expected remote-admin software; otherwise exercise caution.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete11 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 7 contacted hosts were cross-checked; coverage is incomplete.
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
- 11MITRE ATT&CK techniques
- 3spawned processes
- 7network contacts
- 19filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
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: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
Note: Loads extra code modules while running.
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
ScreenConnect.ClientSetup.exe
96f9de130643657d058edabb0f8765a7b9ad4e753cf9bc4718a2f2dcf9a28d30
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\System32\msiexec.exe /i C:\Users\<USER>\AppData\Local\Temp\ScreenConnect\26.5.3.9691\f497cb742b3fd927\ScreenConnect.ClientSetup.msi SC_EXE_PATH=C:\Users\<USER>\Downloads\ScreenConnect.ClientSetup.exe
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\ScreenConnect.ClientSetup.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ScreenConnect.ClientSetup.msi
C:\Users\<USER>\AppData\Local\Temp\ScreenConnect\26.5.3.9691\f497cb742b3fd927\ScreenConnect.ClientSetup.msi
04Isolated runtime analysis - Written fileObserved
ScreenConnect.InstallerActions.dll
C:\Users\<USER>\AppData\Local\Temp\MSIC583.tmp-\ScreenConnect.InstallerActions.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
8.8.8.8
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
34.193.20.205
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.
- 8.8.8.8
- 34.193.20.205
- 3.167.69.110
- 92.223.96.6
- 23.11.32.159
- 162.159.36.2
- http://crt.rootg2.amazontrust.com/rootg2.cer
- C:\Users\<USER>\AppData\Local\Temp\ScreenConnect\26.5.3.9691\f497cb742b3fd927\ScreenConnect.ClientSetup.msi
- C:\Users\<USER>\AppData\Local\Temp\MSIC583.tmp-\ScreenConnect.InstallerActions.dll
- C:\Users\<USER>\AppData\Local\Temp\MSIC583.tmp-\Microsoft.Deployment.WindowsInstaller.dll
- C:\Users\<USER>\AppData\Local\Temp\MSIC583.tmp-\Microsoft.Deployment.WindowsInstaller.Package.dll
- C:\Users\<USER>\AppData\Local\Temp\MSIC583.tmp-\ScreenConnect.Core.dll
- C:\Users\<USER>\AppData\Local\Temp\MSIC583.tmp
- C:\Users\<USER>\AppData\Local\Temp\MSIC9CA.tmp
- C:\Users\<USER>\AppData\Local\Temp\MSICEAD.tmp
- \Sessions\1\BaseNamedObjects\Microsoft.Windows.Health.TestInProduction.RegistryStore.AggregateResults
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 9a390e26cca8c5be4572…df69e7Never 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
- 11 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
11 of 75 antivirus engines flagged the file, including AhnLab-V3 and DrWeb.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The file has a valid code signature from ConnectWise.
ProvenanceObservedSourceCode-signing metadataObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: ScreenConnect.ClientSetup.exe — 96f9de130643657d058edabb0f8765a7b9ad4e753cf9bc4718a2f2dcf9a28d30
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\System32\msiexec.exe /i C:\Users\<USER>\AppData\Local\Temp\ScreenConnect\26.5.3.9691\f497cb742b3fd927\ScreenConnect.ClientSetup.msi SC_EXE_PATH=C:\Users\<USER>\Downloads\ScreenConnect.ClientSetup.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\ScreenConnect.ClientSetup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ScreenConnect.ClientSetup.msi — C:\Users\<USER>\AppData\Local\Temp\ScreenConnect\26.5.3.9691\f497cb742b3fd927\ScreenConnect.ClientSetup.msi
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ScreenConnect.InstallerActions.dll — C:\Users\<USER>\AppData\Local\Temp\MSIC583.tmp-\ScreenConnect.InstallerActions.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 8.8.8.8 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 34.193.20.205 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: hacktool
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.
Evidence34.193.20.205 · 3.167.69.110 · 92.223.96.6
11 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
Barely seen in the wild and first surfaced recently. 11 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- ScreenConnect.ClientSetup.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: ConnectWise
- Size
- 12.2 MB
- Last analyzed
- Aug 29, 2026, 2:33 AM UTC
96f9de130643657d058edabb0f8765a7b9ad4e753cf9bc4718a2f2dcf9a28d30Safety & 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 run 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 developer's official site or an official app store.
- 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 ScreenConnect.ClientSetup.exe safe, or is it malware?
What is ScreenConnect.ClientSetup.exe?
How many antivirus engines detected ScreenConnect.ClientSetup.exe?
I already downloaded and ran ScreenConnect.ClientSetup.exe — what should I do?
How do I remove ScreenConnect.ClientSetup.exe?
What kind of malware is ScreenConnect.ClientSetup.exe?
Is ScreenConnect.ClientSetup.exe digitally signed?
What is the SHA-256 hash of ScreenConnect.ClientSetup.exe?
How up to date is this analysis of ScreenConnect.ClientSetup.exe?
Community
Member reviews and reports for this exact file hash.