Microsoft Threat Intelligence reports that the SCKit toolkit exploits ConnectWise ScreenConnect to install unauthorized remote-access implants and then hijack active technician sessions. The attack chain leverages ScreenConnect's legitimate extension framework and session-handling features to gain persistent footholds and pivot across managed environments.


Attack chain and SCKit capabilities
SCKit is a post-exploitation toolkit designed to weaponize ConnectWise ScreenConnect, a widely used remote monitoring and management platform. Operators first gain access to a ScreenConnect server — often through exposed web interfaces or compromised credentials — and then deploy SCKit as a malicious extension. The toolkit registers itself inside ScreenConnect's extension directory, giving it the same privileges as legitimate add-ons and allowing it to survive service restarts and system reboots without additional persistence mechanisms.
Once installed, SCKit enumerates active sessions and injects code into the technician console. This injection lets attackers observe or take over live support sessions, capture keystrokes, and execute commands on the endpoint without the technician's knowledge. The toolkit also creates hidden access tokens that persist across reboots, providing long-term remote access even if the initial entry point is closed or credentials are rotated.
Microsoft observed SCKit being used to pivot from a single compromised ScreenConnect server into multiple customer environments managed by the same MSP. Because technicians often connect to dozens of client machines from one console, hijacking that console multiplies the blast radius dramatically. The activity aligns with financially motivated intrusion sets that monetize access through ransomware deployment or data theft across the managed service provider ecosystem.
Detection signals in Microsoft Defender XDR
Defender for Endpoint surfaces several behavioral indicators tied to SCKit. Process creation events show the ScreenConnect service spawning unexpected child processes such as PowerShell or cmd.exe with encoded commands. File system telemetry captures new DLLs or scripts dropped into the ScreenConnect extension folder, often with randomized names but consistent directory paths that stand out against baseline extension inventories.
Network logs reveal outbound connections from the ScreenConnect server to uncommon destinations on non-standard ports, typically used for command-and-control callbacks. Defender for Identity correlates these signals with authentication anomalies, such as service accounts performing interactive logons or token manipulation via MakeToken-style techniques that indicate credential theft and lateral movement preparation.
Microsoft provides ready-to-run advanced hunting queries that join DeviceProcessEvents, DeviceFileEvents, and DeviceNetworkEvents around the ScreenConnect service account. The queries filter for extension-folder writes, suspicious command lines, and lateral movement patterns like SMB session enumeration from the server host, giving security teams immediate detection coverage without custom rule development.
Recommended mitigations for MSPs and IT teams
Restrict ScreenConnect web portals to trusted IP ranges or VPN access only; do not expose the management interface directly to the internet. Enforce multi-factor authentication for all administrator and technician accounts, and rotate service-account credentials regularly using a privileged access management solution to limit the window of opportunity for credential reuse.
Audit the ScreenConnect extension directory on a schedule. Remove any extensions not explicitly approved by change control, and verify digital signatures on legitimate add-ons. Enable tamper protection on the ScreenConnect service so that unauthorized file writes trigger alerts and prevent silent modification of the extension catalog.
Segment technician workstations from managed client networks using firewall rules or Zero Trust network access. Limit the number of concurrent sessions per technician and enforce session recording with immutable storage. Apply the principle of least privilege to the ScreenConnect service account, denying interactive logon rights and restricting lateral SMB access to contain potential compromise.
What to do next
Run the Defender XDR hunting queries today to baseline your ScreenConnect servers. Patch or isolate any instance running an unapproved extension, and enforce MFA plus network segmentation before the next maintenance window.
Source: SCKit abuses ScreenConnect to deploy remote access and target technician sessions (Azure).



