SCKit worm abuses ScreenConnect to install unauthorised remote access and target technicians
- Severity
- High
- Exploited
- Yes
- Sources
- 4
What happened
ConnectWise reported an active campaign from 11 November 2026 in which attackers gained unauthorised access to cloud-hosted ScreenConnect instances used by managed service providers, and Microsoft Threat Intelligence confirmed this activity. The SCKit toolkit installs persistence through scheduled tasks and Run registry entries, deploys RelayTrap to deliver a payload to connecting technicians, and uses hijacked technician sessions to push payloads to other managed devices. Removing the unauthorised client alone does not remove the persistence or invalidate exposed web sessions.
For IT people · Written by AI from 4 sources · Wrong?
What to do
- Investigate ScreenConnect technician workstations and the endpoints they have managed for unauthorised clients.
- Remove scheduled tasks and registry Run entries left by SCKit, not just the unauthorised client.
- Check whether RMM+ 1.0.31 or 1.0.32 is installed and ensure an access key is configured.
- Apply the ConnectWise fix for CVE-2026-84869 and invalidate exposed ScreenConnect web sessions.
Written by AI from the sources, checked against them
Vulnerabilities
Full story timeline · 5 updates
- Fri 11 SeptemberCVE-2026-84869 added to CISA’s exploited listCISA KEV
- Thu 12 NovemberHackers Hijack ConnectWise ScreenConnect to Deploy SCKit Malware Across 288 Devices at 48 OrganizationsCyber Security News
- SCKit Malware Turns ScreenConnect Support Sessions Into Potential MSP Attack PathsThe Hacker News
- Rogue remote-access campaign spread through ScreenConnect add-on, researchers sayCyberScoop
- Fri 13 NovemberSCKit abuses ScreenConnect to deploy remote access and target technician sessionsMicrosoft Security Blog
Who reported · 4 outlets
Who and what is in it
Companies
Products