Threat LensFile scan report

Is ScreenConnect.ClientSetup.exe safe?

Verdict
Suspicious

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.

Do not run it until verified

Verify the installer came from ConnectWise’s official channel; if the source is trusted, the file is expected remote-admin software; otherwise exercise caution.

Read the full analysis
Saved file evidenceAntivirus consensus
11of 75 flagged
Flagged 11No detection 64
Digital specimenScreenConnect.ClientSetup.exe96f9de130643657d05…a2f2dcf9a28d30
Size12.2 MB
Code signingConnectWise
SandboxRuntime complete
First seenToday
Evidence3 priority signals
11 of 75 antivirus engines flagged the file, including AhnLab-V3 and DrWeb.

Recommended next actions

01

Before running

Do not run it until the source and publisher can be verified independently.

02

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.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

65%Confidence
High
Analyst conclusion

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.

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.

Recommended action

Verify the installer came from ConnectWise’s official channel; if the source is trusted, the file is expected remote-admin software; otherwise exercise caution.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    11 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    1 of 7 contacted hosts were cross-checked; coverage is incomplete.

  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

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.

Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & 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.

  1. Recovery step 01

    Don't run it unless you're certain it came from a source you trust.

  2. Recovery step 02

    Check where you got it — an unexpected attachment or a random download link is a red flag.

  3. 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.

  4. 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.

9 evidence-based answers
Is ScreenConnect.ClientSetup.exe safe, or is it malware?
Evidence-based answer
ScreenConnect.ClientSetup.exe is suspicious — treat it as unsafe until you're sure. 11 of 75 antivirus engines flag it (family: remoteadmin); that detection signal contributes to the cautious verdict. Don't run it unless you fully trust where it came from. Get a fresh copy from the developer's official site or an official app store.
What is ScreenConnect.ClientSetup.exe?
Evidence-based answer
ScreenConnect.ClientSetup.exe is a Windows executable program, about 12.2 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
How many antivirus engines detected ScreenConnect.ClientSetup.exe?
Evidence-based answer
11 of 75 antivirus engines flagged ScreenConnect.ClientSetup.exe, 11 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence.
I already downloaded and ran ScreenConnect.ClientSetup.exe — what should I do?
Evidence-based answer
Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
How do I remove ScreenConnect.ClientSetup.exe?
Evidence-based answer
To remove ScreenConnect.ClientSetup.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete this file from the device, then empty the Recycle Bin or Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
What kind of malware is ScreenConnect.ClientSetup.exe?
Evidence-based answer
ScreenConnect.ClientSetup.exe is classified as a hacktool — dual-use offensive tooling that is dangerous regardless of intent. Engines attribute it to the remoteadmin family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
Is ScreenConnect.ClientSetup.exe digitally signed?
Evidence-based answer
Yes — ScreenConnect.ClientSetup.exe carries a valid digital signature from ConnectWise, which confirms the file hasn't been tampered with since that publisher signed it. A valid signature is a positive signal, but note that malware is occasionally signed with stolen or abused certificates, so it isn't proof of safety on its own.
What is the SHA-256 hash of ScreenConnect.ClientSetup.exe?
Evidence-based answer
The SHA-256 hash of ScreenConnect.ClientSetup.exe is 96f9de130643657d058edabb0f8765a7b9ad4e753cf9bc4718a2f2dcf9a28d30, and its MD5 is 315119b16e8574c8c2261b8b3938a338. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
How up to date is this analysis of ScreenConnect.ClientSetup.exe?
Evidence-based answer
This report reflects the scan run on August 29, 2026. Because a file's hash never changes, the identity of ScreenConnect.ClientSetup.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.