File scan report
Verdict Suspicious
Is Screen Connect. Client Setup. msi safe? Treat it as suspicious.
A genuine ConnectWise ScreenConnect client installer that grants someone remote control of this PC.
Why Suspicious? 12 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now5 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
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.
It is only 3 days old. If you're unsure, scan it again in a few days; antivirus engines often catch up on new files.
If you already installed it
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.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
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
12 of 63 flagged
- Flagged 12
- No detection 51
- No result 12
- Code signing ConnectWise, LLC
- Test run Completed
- First seen 3d ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This is a validly signed ScreenConnect client installer. When run, it installs a background service and connects to a specific remote session server, giving whoever controls that server access to the computer. Twelve of the 63 antivirus engines that checked it flag it, including DrWeb, Kaspersky and Trellix, because this tool is widely abused by tech-support scammers and intruders.
The file carries a verified signature from ConnectWise, LLC, so it is the real remote-support product, not a tampered copy. In the sandbox runs it installed the ScreenConnect client service and connected as a guest-access client to a cloud relay server, which is exactly what grants remote control. Twelve of the 63 antivirus engines that checked it flagged it, three of them major, mostly with remote-administration or riskware labels rather than a malware family. The file is and seen from a single source, and earlier ScreenConnect installers from this signer were rated the same way. Whether it is safe depends entirely on who sent it.
What We Detected
12 of the 63 antivirus engines that checked it flagged this Windows Installer package, including DrWeb, Kaspersky and Trellix, with labels such as remote-admin, riskware and hacking tool tied to ConnectWise ScreenConnect. The package is validly signed by ConnectWise, LLC. Our static analysis matched an indicator rule for this remote-management tool.
Threat Behavior
In the sandbox runs the installer ran silently, created the ScreenConnect client service, and started client processes that connected to a ScreenConnect cloud relay server for a guest session. No process injection or malicious network host was found. However, the purpose of this software is to let a remote operator see and control the computer.
What To Do Now
Only install this if your own IT department or a support provider you contacted yourself asked you to. If someone sent it by unsolicited call, email or pop-up, do not run it. If it is already installed, uninstall the ScreenConnect Client, disconnect from the internet and run a full scan with your security software kept enabled.
Where this verdict could be wrong2 caveats
- The installer carries a verified ConnectWise signature, and no malicious host, file it created or sandbox verdict was found. If an IT provider you trust sent it, it is likely ordinary remote-support software.
- Most detections label the product category (remote administration) rather than a malware family.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Valid code signature from ConnectWise, LLC
- No malicious hosts among the contacted servers
- No malicious sandbox verdict and no observed injection into other processes
- Three major antivirus engines and nine others flag it as remote-access tooling
- Installs a background service that gives a remote operator control of the computer
- Connects to a cloud relay session that tech-support scammers commonly use
- Rare and recently observed, from a single submitter
7 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 3 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 21sandbox rule tags
- 4spawned processes
- 9network contacts
- 26filesystem & 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.
Note: Read the user name of the test computer.
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
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 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.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
ScreenConnect.ClientSetup.msi
6c0756f4702c7e9257c832e05ebb6945f5c377c535c1a89bc8a06e7b90eada60
Uploaded file
- 2
Processes
What ran
- 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 - Evidence 3 of 7: ProcessSeen in the test run
ScreenConnect.ClientService.exe
"C:\Program Files (x86)\ScreenConnect Client (0fad7daefc5c4850)\ScreenConnect.ClientService.exe" "?e=Access&y=Guest&h=instance-ouoxhg-relay.screenconnect.com&p=443&s=e8942f90-cce2-4e74-913a-da4e32c13864&k=BgIAAACkAABSU0ExAAgAAAEAAQCxL0i1W9Z8xPu0o16i%2bkbg%2fd9x7p7s1T880WULrTS74HTBAu%2fEePtURrLy33ioFCVbMDmZPwaWOyoOHEcnD%2f3IaOLey144upgjyP9b9hPBoAojkrBwialiRmgpQWLPVBOua9T8vJUdI0LXvdvsgzdyVLAJ3Ud4bYkQ73Vhtwa5AaclOqxo%2fwkJT0l1NgulLrIMglG4qaZ6Sifq0g%2b4wjX1WhGmC%2fosywPVxNkQq430aw5vcML9sNUt43bHy6HPk5uvl8E9BnCJ3DcHIUHxqzqxSLm2o3RNy55m0otsUfHA0OvAtHoNoJph%2fiEefnd64cZpFr3VYcLh6l46qcnycvuV"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
3g3jc1kd.tmp
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\3g3jc1kd.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
3g3jc1kd.newcfg
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\3g3jc1kd.newcfg
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
instance-ouoxhg-relay.screenconnect.com
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
check.screenconnect.com
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 3 sandboxes and its runtime behaviour was observed.
Techniques observed in the sandbox
21MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1033· Reads user info
- T1047
- T1055· Process injection
- T1059· Runs commands
- T1071· Application protocol
- T1074
- T1082· System recon
- T1105· Network file transfer
- T1106
- T1112
- T1129· Loads modules
- T1497· Sandbox evasion
- T1518· Checks your AV
- T1539
- T1547· Auto-start
- T1547.001· Auto-start
- T1562· Disables security
- T1562.001· Disables security
- T1573
- T1574· Execution hijack
Observed activity
Processes started
4Programs the file ran, with their command lines.
msiexec.exe"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\ScreenConnect.ClientSetup.msi" /qb ACCEPTEULA=1 LicenseAccepted=1ScreenConnect.ClientService.exe"C:\Program Files (x86)\ScreenConnect Client (0fad7daefc5c4850)\ScreenConnect.ClientService.exe" "?e=Access&y=Guest&h=instance-ouoxhg-relay.screenconnect.com&p=443&s=e8942f90-cce2-4e74-913a-da4e32c13864&k=BgIAAACkAABSU0ExAAgAAAEAAQCxL0i1W9Z8xPu0o16i%2bkbg%2fd9x7p7s1T880WULrTS74HTBAu%2fEePtURrLy33ioFCVbMDmZPwaWOyoOHEcnD%2f3IaOLey144upgjyP9b9hPBoAojkrBwialiRmgpQWLPVBOua9T8vJUdI0LXvdvsgzdyVLAJ3Ud4bYkQ73Vhtwa5AaclOqxo%2fwkJT0l1NgulLrIMglG4qaZ6Sifq0g%2b4wjX1WhGmC%2fosywPVxNkQq430aw5vcML9sNUt43bHy6HPk5uvl8E9BnCJ3DcHIUHxqzqxSLm2o3RNy55m0otsUfHA0OvAtHoNoJph%2fiEefnd64cZpFr3VYcLh6l46qcnycvuV"ScreenConnect.WindowsClient.exe"C:\Program Files (x86)\ScreenConnect Client (0fad7daefc5c4850)\ScreenConnect.WindowsClient.exe" "RunRole" "a0bd7aaa-f634-4d13-869e-dd194bdb7611" "User"ScreenConnect.WindowsClient.exe"C:\Program Files (x86)\ScreenConnect Client (0fad7daefc5c4850)\ScreenConnect.WindowsClient.exe" "RunRole" "c614647d-52c4-4ee7-9a4d-58fbcacb134a" "System"
Network contacts
99 hosts, listed as 4 domains, 5 addresses, 1 link. Links show the host and path only.
- Domain
instance-ouoxhg-relay.screenconnect.com - Domain
check.screenconnect.com - Domain
crt.rootg2.amazontrust.com - Domain
server-ovh5008527-relay.screenconnect.com - IP address
15.235.11.101 - IP address
100.60.246.137
Show all 10 entries for network contacts
- IP address
3.167.69.74 - IP address
23.3.75.152 - IP address
23.11.33.159 - URL
http://crt.rootg2.amazontrust.com/rootg2.cer
Files
24Files the file created, changed or deleted.
- Written
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\3g3jc1kd.tmp - Written
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\3g3jc1kd.newcfg - Written
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\user.config - Written
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\tuvoni0t.tmp - Written
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\tuvoni0t.newcfg - Written
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\hq3ywxt2.tmp
Show all 24 entries for files
- Written
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\hq3ywxt2.newcfg - Written
C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\ScreenConnect.WindowsClient.exe.log - Written
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\MSIC18C.tmp-\ScreenConnect.InstallerActions.dll - Written
C:\Users\<USER>\AppData\Local\Temp\MSIC18C.tmp-\Microsoft.Deployment.WindowsInstaller.dll - Written
C:\Users\<USER>\AppData\Local\Temp\MSIC18C.tmp-\Microsoft.Deployment.WindowsInstaller.Package.dll - Written
C:\Users\<USER>\AppData\Local\Temp\MSIC18C.tmp-\ScreenConnect.Core.dll - Written
C:\Users\<USER>\AppData\Local\Temp\MSIC18C.tmp-\ScreenConnect.Windows.dll - Written
C:\Users\<USER>\AppData\Local\Temp\MSIC18C.tmp-\ScreenConnect.WindowsInstaller.dll - Deleted
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\3g3jc1kd.newcfg - Deleted
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\3g3jc1kd.tmp - Deleted
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\tuvoni0t.newcfg - Deleted
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\tuvoni0t.tmp - Deleted
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\hq3ywxt2.newcfg - Deleted
C:\Windows\System32\config\systemprofile\AppData\Local\ScreenConnect Client (0fad7daefc5c4850)\hq3ywxt2.tmp - Deleted
C:\Users\<USER>\AppData\Local\Temp\MSIC18C.tmp - Deleted
C:\Users\<USER>\AppData\Local\Temp\MSICFE5.tmp - Deleted
C:\Users\<USER>\AppData\Local\Temp\MSID6CB.tmp
Registry and auto-start
15Settings the file changed, including ways to start again after a restart.
- Set
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\ProxyBypass - Set
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\IntranetName - Set
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\UNCAsIntranet - Set
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\AutoDetect - Set
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ScreenConnect Client (0fad7daefc5c4850)\ImagePath - Set
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\EventLog\Application\ScreenConnect\EventMessageFile
Show all 15 entries for registry and auto-start
- Set
HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Cached\{8D80504A-0826-40C5-97E1-EBC68F953792} {886D8EEB-8CF2-4446-8D02-CDBA1DBDCF99} 0xFFFF - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\InProgress\(Default) - Set
HKEY_CLASSES_ROOT\sc-0fad7daefc5c4850\shell\open\command\(Default) - Set
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SafeBoot\Network\ScreenConnect Client (0fad7daefc5c4850)\(Default) - Set
HKEY_CLASSES_ROOT\CLSID\{6FF59A85-BC37-4CD4-C057-FF94D35AA6C9}\InprocServer32\(Default) - Set
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Authentication Packages - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{6FF59A85-BC37-4CD4-C057-FF94D35AA6C9}\(Default) - Set
HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\ScreenConnect Client (0fad7daefc5c4850)\Start - Set
HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\ScreenConnect Client (0fad7daefc5c4850)\ImagePath
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
Global\_MSIExecuteGlobal\netfxeventlog.1.0
Sandbox background — not the file
6The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
lsass.exeC:\Windows\system32\lsass.exe - VM host
8.8.8.8
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache. 1 has no saved verdict and was not checked; that is missing coverage, not a finding.
- ed4c87e89be4e43a36d8…0d51b6Not checkedno saved verdict
Chapter 04
Technical details
12 of the 63 antivirus engines that checked it flag it; signed by ConnectWise, LLC.
No risky structure found
We opened the uploaded Windows installer in an isolated sandbox and read its structure without running it.
7 links found. Only domains are shown; paths and query strings are never published.
Checked on Oct 22, 2026 while the file was uploaded. MalwareTips deleted its copy afterwards; VirusTotal keeps the uploaded file.
Sources checked
Every check behind this verdict
7 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 12
- DrWeb (major engine)BackDoor.RA.364
- Kaspersky (major engine)not-a-virus:HEUR:RemoteAdmin.Win32.ConnectWise.gen
- TrellixENS (major engine)ConnectWise
- GoogleDetected
- huorongHackTool/ConnectWiseControl.j
- NANO-AntivirusRiskware.Win32.RemoteAdmin.ljylbz
- RisingHacktool.ConnectWise!8.13A88 (CLOUD)
- SkyhighConnectWise
File fingerprint
- Last analyzed
- Oct 22, 2026, 6:11 PM UTC
- SHA-256
6c0756f4702c7e9257c832e05ebb6945f5c377c535c1a89bc8a06e7b90eada60- SHA-1
451d40153fa80bcd1f11942b696cab12f5ef4c01- MD5
bbeefbf6f88618f44dae1d12c55d4e03
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
- Oct 22, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Antivirus consensus
12 of 63 engines flagged this file
12 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
The 12 detections come from 11 independent scan engines: several vendors license the same engine, so their results are one vote.
- Tier-118 engines3flagged
- Tier-233 engines7flagged
- Low-trust12 engines2flagged
View all 75 engine results
- DrWebMalicious: BackDoor.RA.364
- GoogleMalicious: Detected
- huorongMalicious: HackTool/ConnectWiseControl.j
- KasperskyMalicious: not-a-virus:HEUR:RemoteAdmin.Win32.ConnectWise.gen
- NANO-AntivirusMalicious: Riskware.Win32.RemoteAdmin.ljylbz
- RisingMalicious: Hacktool.ConnectWise!8.13A88 (CLOUD)
- SkyhighMalicious: ConnectWise
- TrellixENSMalicious: ConnectWise
- VaristMalicious: W32/ConnectWise.S.gen!Eldorado
- VBA32Malicious: Riskware.MSIL.ScreenConnect.Heur
- XcitiumMalicious: ApplicUnwnt@#2zaiqebwyafpj
- ZillyaMalicious: Tool.ConnectWise.Win32.234
- AcronisClean
- AhnLab-V3Clean
- AlibabaNo result
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GridinsoftClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- PaloaltoNo result
- PandaClean
- SangforClean
- SentinelOneClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootNo result
- YandexClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)Signed by "ConnectWise, LLC" — short generic company CN. Paired with 12 engine hit(s); possible stolen, fraudulent, or reseller-purchased code-signing certificate.
EvidenceConnectWise, LLC
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 12 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
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?
What is ScreenConnect.ClientSetup.msi?
How many antivirus engines detected ScreenConnect.ClientSetup.msi?
What should I do if I already installed 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.