Is ScreenConnect.ClientSetup.msi safe?
Signed ConnectWise ScreenConnect installer flagged by two tier-1 engines as remote-admin tool with process-injection and defense-evasion behaviour.
Two tier-1 engines and multiple tier-2 detections label the MSI as a ConnectWise remote-administration tool. The file is legitimately signed by ConnectWise, yet it exhibits offensive MITRE techniques and a prior similar sample was rated suspicious.
72265f63179181b63a…637ca26865c84eRecommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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.
Two tier-1 engines and multiple tier-2 detections label the MSI as a ConnectWise remote-administration tool. The file is legitimately signed by ConnectWise, yet it exhibits offensive MITRE techniques and a prior similar sample was rated suspicious.
The sample triggers hacktoolConfirmed because at least one tier-1 engine and several tier-2 engines explicitly label it a ConnectWise hacktool. Offensive techniques T1055, T1485, T1547.001 and T1562.001 observed in the sandbox raise the risk profile. The signer is ConnectWise, but the absence of historical signer statistics and the rare_new prevalence classification prevent a clean verdict. The single prior signer-matched sample also received a suspicious rating, reinforcing the mixed-signal assessment.
What We Detected
10 of 75 engines flagged the MSI. Two tier-1 engines (DrWeb, Kaspersky) and several tier-2 engines returned remote-admin or hacktool labels. The file is signed by ConnectWise and verified.
Threat Behavior
Sandbox execution showed process injection (T1055), data destruction (T1485), persistence via autostart (T1547.001) and defense evasion (T1562.001). Six external IPs were contacted directly; no complete contacted-host reputation result was available were identified in our cache. Eight child files were dropped, none flagged malicious.
What To Do Now
If this installer was obtained from the official ConnectWise site or your IT department, treat it as expected remote-support software. Otherwise, verify the download source and keep endpoint protection enabled.
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.
- Digitally signed and verified by ConnectWise
- No malicious child files or known-malicious hosts contacted
- Two tier-1 detections on remote-admin/hacktool category
- Offensive MITRE techniques observed in sandbox
- Rare and recently submitted file (rare_new)
Verify the installer came from an official ConnectWise channel; if the source is untrusted, quarantine the file and scan the system with up-to-date security software.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete10 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 8 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete3 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
- 28MITRE ATT&CK techniques
- 14spawned processes
- 8network contacts
- 27filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used removable-media replication behaviour that can spread files between devices.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
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.msi
72265f63179181b63a71516d4eb68bd2a463b9dd75741307ba637ca26865c84e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\ScreenConnect.ClientSetup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
hm3hlfjo.tmp
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.tmp
04Isolated runtime analysis - Written fileObserved
hm3hlfjo.newcfg
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.newcfg
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
15.204.186.18
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
8.8.8.8
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.
- 15.204.186.18
- 8.8.8.8
- 34.193.20.205
- 3.167.69.74
- 199.232.210.172
- 23.11.32.159
- 162.159.36.2
- http://crt.rootg2.amazontrust.com/rootg2.cer
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.tmp
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.newcfg
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\user.config
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\3fs51om0.tmp
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\3fs51om0.newcfg
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.newcfg
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.tmp
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\3fs51om0.newcfg
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\3fs51om0.tmp
- C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\ojx0pfil.newcfg
- Global\_MSIExecute
- Global\netfxeventlog.1.0
- \BaseNamedObjects\Local\SM0:5472:304:WilStaging_02
Files this sample writes at runtime
This file drops 8 children at runtime. None are currently flagged malicious in our cache.
- 8cd975f551bb249e5890…7bb24aNever scannednever seen before
- de867af8055f81b7691f…96e16fNever scannednever seen before
- 548c551f6ebc5d829158…c624a1Never scannednever seen before
- 3e54286e348ebd3d70ea…3db29dNever scannednever seen before
- e92d94613443befebb55…2964f7Never scannednever seen before
- d827d3575ca29f8a40ea…4b51bbNever scannednever seen before
- 320b89343e896a8d2ebf…797fbbNever scannednever seen before
- dbf379b93127345a8328…dc764fNever 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.
- 3rule hits recorded
- 10 / 75engines flagged
- 2sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
10 of 75 antivirus engines flagged the file, including DrWeb and Google.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from ConnectWise.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: ScreenConnect.ClientSetup.msi — 72265f63179181b63a71516d4eb68bd2a463b9dd75741307ba637ca26865c84e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\ScreenConnect.ClientSetup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: hm3hlfjo.tmp — C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: hm3hlfjo.newcfg — C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (22cbab73b9a716a9)\hm3hlfjo.newcfg
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 15.204.186.18 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 8.8.8.8 — 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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence15.204.186.18 · 34.193.20.205 · 3.167.69.74
10 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 10 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- ScreenConnect.ClientSetup.msi
- Format
- Windows Installer
- Code signing
- Signature valid: ConnectWise
- Size
- 9.8 MB
- Last analyzed
- Aug 29, 2026, 7:11 PM UTC
72265f63179181b63a71516d4eb68bd2a463b9dd75741307ba637ca26865c84eSafety & 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 install 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. Download a fresh installer 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.msi safe, or is it malware?
What is ScreenConnect.ClientSetup.msi?
How many antivirus engines detected ScreenConnect.ClientSetup.msi?
What should I do if I already installed ScreenConnect.ClientSetup.msi?
How do I remove ScreenConnect.ClientSetup.msi?
What kind of malware is ScreenConnect.ClientSetup.msi?
Is ScreenConnect.ClientSetup.msi digitally signed?
What is the SHA-256 hash of ScreenConnect.ClientSetup.msi?
How up to date is this analysis of ScreenConnect.ClientSetup.msi?
Community
Member reviews and reports for this exact file hash.