File scan report

Verdict Suspicious

Analyzed , 9 days ago

Is ScreenConnect.ClientSetup.msi safe? Treat it as suspicious.

Two major antivirus engines and multiple smaller detections label the MSI as a ConnectWise remote-administration tool.

Read the whole reasonShow less

Why Suspicious? 10 antivirus engines flag it; nothing else confirms it.

Limited evidence · One sign points to a problem; nothing else confirms it.

Don't install it until you know where it came from

If it came from a link, an attachment or a stranger, delete it.

What to do now4 steps

Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.

What to do

  1. Don't install it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.

If you already installed it

  1. Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.

Not sure what to do?

Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.

Paste this report's link in your topic so helpers can see what was found.

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

10 of 62 flagged

  • Flagged 10
  • No detection 52
  • No result 13
FileScreenConnect.ClientSetup.msi10.2 MBSHA-256 72265f631791…65c84e
  • Code signing ConnectWise, LLC
  • Test run Completed
  • First seen 1mo ago
10 of the 62 antivirus engines that checked it flag it, including Kaspersky and Dr.Web.

Chapter 02

Why we think so

3 points against it and 2 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The file is legitimately signed by ConnectWise, yet it exhibits offensive MITRE techniques and a prior similar sample was rated suspicious.

Where this verdict could be wrong1 caveat
  • contactedHosts.maliciousHosts.length=0 and droppedChildren.hasMaliciousChild=false — no confirmed malicious infrastructure or child payloads observed.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

6 sources checked · 5 complete · 1 partial. See every source

Chapter 03

What it did in our test

It ran in our isolated test environment; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 28sandbox rule tags
  • 7spawned processes
  • 5network contacts
  • 27filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Downloaded a file during the test run.

  • Moderate concern: Checked whether it was running on a test computer.

  • Moderate concern: Hid files or windows on the test computer.

  • Note: Read the user name of the test computer.

  • Note: Deleted files or logs during the test run (installers often clean up after themselves).

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: A sandbox rule tagged this run as spreading through USB drives; nothing confirms it.

  • Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.

  • Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      ScreenConnect.ClientSetup.msi

      72265f63179181b63a71516d4eb68bd2a463b9dd75741307ba637ca26865c84e

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      msiexec.exe

      "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\ScreenConnect.ClientSetup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1

      Test run
    2. Evidence 3 of 7: ProcessSeen in the test run

      ScreenConnect.ClientService.exe

      "C:\Program Files (x86)\ScreenConnect Client (22cbab73b9a716a9)\ScreenConnect.ClientService.exe" "?e=Access&y=Guest&h=instance-e4nogh-relay.screenconnect.com&p=443&s=29f38bb1-620f-4a83-b051-b4b03c2700c7&k=BgIAAACkAABSU0ExAAgAAAEAAQDJb4UxGns%2bDdWnv50eJpt9%2fhLA9Ly5I%2bD%2fRBJ5sdUbbgEzsWxp4HCNcwq4eQxBAlj4r%2bHupxSkD2%2blWaV6i8AxUeQwImQlZLdg4F6vsEKofeFKM6UqsN8O%2fmZZKld015wvsgv0LVhniSVplMOdib2SEnt8JwWQ8Gc1teS8gMPFX9Zn%2b8NE%2bePw9nmVFQFP5JDHwwtfVs%2fsKRzFktsLBzy7noyXVCTtsORIPxbzyKqnmDyuFFiK1xskSvqWE0t8rLEP5gYmEqNrQEiaEyFz7mSOfNGaW4mI6WlsI6UB%2byRfmX82TqzkEERwTA%2fONz968lBCBY2ANC0EIHYgkWCJP%2fDO"

      Test run
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      hm3hlfjo.tmp

      C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.tmp

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      hm3hlfjo.newcfg

      C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.newcfg

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      15.204.186.18

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      34.193.20.205

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 04

Technical details

10 of the 62 antivirus engines that checked it flag it; signed by ConnectWise, LLC.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 10 of 62 engines flagged it · 13 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial1 of 6 contacted hosts were cross-checked; coverage is incomplete Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 10

  • DrWeb (major engine)BackDoor.RA.364
  • Kaspersky (major engine)not-a-virus:HEUR:RemoteAdmin.Win32.ConnectWise.gen
  • TrellixENS (major engine)Artemis!E1F2D75DD493
  • GoogleDetected
  • huorongHackTool/ConnectWiseControl.j
  • RisingHacktool.ConnectWise!8.13A88 (CLOUD)
  • VaristW32/ConnectWise.S.gen!Eldorado
  • VBA32Riskware.MSIL.ScreenConnect.Heur
2 more in the full engine list

File fingerprint

Last analyzed
Oct 17, 2026, 1:23 PM UTC
SHA-256
72265f63179181b63a71516d4eb68bd2a463b9dd75741307ba637ca26865c84e
SHA-1
ac03ee169fbbdc3bfaea7056a13769c17d338255
MD5
51f6afece02b5a8bb5904c005ef92782

About this file

ScreenConnect.ClientSetup.msi is a Windows Installer file of 10.2 MB.

Type and size
Windows Installer · 10.2 MB
Signer
ConnectWise, LLCValid code signature.
First seen
Aug 28, 2026On VirusTotal.
Submitted by
2 distinct sourcesRarely seen: few people have submitted this exact file.

First scanned Updated

Chapter 05

Questions & answers

Short answers to the 7 questions people ask most about this file.

Is ScreenConnect.ClientSetup.msi safe, or is it malware?
ScreenConnect.ClientSetup.msi is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. 10 of the 62 antivirus engines that checked it flag it. Don't install it unless you're sure where it came from. If you need the software, download a fresh installer from the developer's own website.
What is ScreenConnect.ClientSetup.msi?
ScreenConnect.ClientSetup.msi is a Windows installer (MSI), about 10.2 MB. VirusTotal first saw it on Aug 28, 2026.
How many antivirus engines detected ScreenConnect.ClientSetup.msi?
10 of the 62 antivirus engines that checked it flag ScreenConnect.ClientSetup.msi, including Kaspersky and Dr.Web. We weigh which engines flagged it and what else the scan found, not just the count.
What should I do if I already installed ScreenConnect.ClientSetup.msi?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
Is ScreenConnect.ClientSetup.msi digitally signed?
Yes. ScreenConnect.ClientSetup.msi has a valid digital signature from ConnectWise, LLC, which shows the file hasn't been changed since that publisher signed it. Malware is sometimes signed with stolen certificates, so a signature alone isn't proof of safety.
What is the SHA-256 hash of ScreenConnect.ClientSetup.msi?
The SHA-256 fingerprint of ScreenConnect.ClientSetup.msi is 72265f63179181b63a71516d4eb68bd2a463b9dd75741307ba637ca26865c84e, and its MD5 is 51f6afece02b5a8bb5904c005ef92782. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of ScreenConnect.ClientSetup.msi?
This report reflects the scan on Oct 17, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Other files people checked with the same name or signer, and recent reports with the same rating. A matching name does not make two files the same: only the SHA-256 fingerprint identifies a file.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.