Skip to content
trendoviz

SCKit abuses ScreenConnect to reach technician workstations

Microsoft observed threat actors abusing ScreenConnect to install unauthorized remote-access clients and deploy the SCKit worm on endpoints managed by service providers. The toolkit persists on affected devices and is designed to target technician workstations through support sessions.

55 out of 100Emerging7D: Insufficient history ProvisionalPublished

Overview

Microsoft Threat Intelligence confirmed a campaign reported by ConnectWise on November 11, 2026, involving unauthorized access to cloud-hosted ScreenConnect instances belonging to managed service providers. Microsoft also observed attackers abusing the remote-support platform to install unauthorized remote-access clients and deploy SCKit on customer-managed endpoints [1].

The documented chain begins with commands issued through ScreenConnect. These commands silently install an additional client connected to threat-actor-controlled infrastructure. A batch launcher then retrieves a PowerShell decoder that decrypts and extracts SCKit using device-specific key material [1].

Why it matters

The campaign changes what a compromised support instance can represent. ScreenConnect commands can install clients connected to attacker infrastructure, and the resulting access allows attackers to administer affected endpoints, execute commands, and deploy further tools independently of the legitimate support instance [1].

Support sessions also become a propagation path. Microsoft says SCKit targets IT support technician workstations using a hijacked authenticated ScreenConnect session, then uses the victim's management console to distribute payloads to other managed devices [1]. A compromise at a service provider can therefore extend beyond the provider's own environment.

Response also has to cover more than a visible remote-access client. Removing an unauthorized client alone does not remove the toolkit's persistence or invalidate exposed web sessions, and SCKit maintains persistence through scheduled tasks and registry Run entries [1].

Opportunities

The disclosed behavior suggests several defensive capabilities that could be built or expanded:

  • Endpoint detection. Microsoft publishes indicators of compromise and Defender XDR hunting queries for this activity [1]. Security teams could package similar detections into managed monitoring workflows for service-provider customer environments.
  • Session and console telemetry. Because the attack chain includes commands issued through the management instance and the use of a hijacked authenticated session, tooling that correlates unusual command patterns, client installations, and session behavior could identify misuse during propagation [1].
  • Remote-management response automation. The documented requirements include removing unauthorized clients, addressing persistence, and invalidating exposed sessions. An incident-response workflow could enumerate these steps across managed fleets [1].
  • Support-chain security reviews. Because SCKit targets technician workstations through a support connection, a product that checks whether endpoint clients, extensions, and support workstations meet a hardened baseline could become part of a provider's assurance offering [1].

These are hypotheses about product opportunities. The evidence does not establish that such products exist, how many would use them, or whether the proposed detections work outside the environments Microsoft studied.

Risks

Operational exposure. ScreenConnect is embedded in support workflows, so organizations may delay changes because remote access is needed for service delivery. A media report states that ConnectWise warned attacks continue against unpatched systems [2]. The evidence does not quantify how many organizations remain exposed or whether patching alone closes the full chain.

Architectural dependence. ScreenConnect operates through a management instance, relay service, technician workstation, and endpoint clients, often alongside RMM software [1]. Security investment tied to one platform's structure can make it harder to operate across heterogeneous remote-management environments.

Response reliability. Removing an unauthorized client alone does not remove persistence or invalidate exposed sessions [1]. Organizations that respond only to the visible client may incorrectly conclude that the environment is clean. The initial-access route for the reported campaign also remains under investigation [1].

Third-party exposure. The campaign targeted cloud-hosted instances belonging to MSPs [1]. The evidence does not document contractual allocation of responsibility, notification duties, liability, or the legal status of affected deployments.

Cost risk cannot be quantified from the available material: no figures for remediation costs, staffing demands, or business losses are provided.

Context

ScreenConnect is a remote-support and access platform used by managed service providers to administer customer devices. Its architecture has three principal components: a management instance that hosts the web console, technician workstations used by support staff, and customer endpoints running guest or access clients [1].

The campaign also involves a separate server-side weakness. ConnectWise's advisory describes an authentication flaw in versions 1.0.31 and 1.0.32 of the RMM+ extension family. When no access key was configured, the extension accepted an empty key, allowing an unauthorized caller to submit commands for delivery to managed endpoints without a normal ScreenConnect user sign-in. ConnectWise is investigating extension abuse as an initial-access route, while the entry method for the reported campaign remains under investigation [1].

Microsoft describes a distinct client-side path. SCKit includes RelayTrap, a malicious replacement for the ScreenConnect client on an affected customer endpoint, designed to deliver a payload to a technician's workstation when support staff connect [1].

Known, claimed, inferred

What the primary source establishes: Microsoft Threat Intelligence confirmed the campaign ConnectWise reported on November 11, 2026, and observed abuse of ScreenConnect to install unauthorized remote-access clients and deploy SCKit on customer-managed endpoints [1]. The chain uses ScreenConnect commands to install a client connected to attacker-controlled infrastructure, followed by a batch launcher that retrieves a PowerShell decoder to decrypt and extract SCKit using device-specific key material [1].

The toolkit persists through scheduled tasks and registry Run entries. Its RelayTrap component is a malicious replacement for the ScreenConnect client on an affected endpoint, intended to deliver a payload to a connecting technician. Microsoft says the worm targets technician workstations through hijacked authenticated sessions and uses the management console to distribute payloads to other managed devices [1].

Two paths should be kept separate. The RMM+ authentication flaw is a server-side issue involving command submission without a normal console sign-in in specific configurations. RelayTrap is a client-side path that moves from a customer endpoint to a technician when support staff connect. ConnectWise states that the fix for CVE-2026-84869 blocks the toolkit's attempted endpoint-to-technician spread; the relationship between the RMM+ flaw and the reported campaign remains unresolved [1].

A reasonable inference is that a remote-support compromise can function as a distribution channel rather than only as a point of entry, because server-side command capability, endpoint persistence, and technician-targeted propagation appear together in the documented behavior [1]. No AI-specific role in the campaign is established by the evidence; nothing attributes SCKit's operation or ScreenConnect's features to AI.

Limitations & uncertainties

The available material does not quantify the number of compromised systems, the scale of the campaign, or the number of affected service providers or customers. It also does not cover incidents after the initial November 11, 2026 report, and it provides no figures for remediation costs, staffing demands, or business losses [1].

No evidence evaluates the effectiveness of patching CVE-2026-84869 or other mitigation steps, and no third-party test report or independent evaluation covers detection coverage for the described indicators of compromise [1].

Several details remain incomplete: the precise mechanics of how RelayTrap replaces the legitimate ScreenConnect client are only partly described, the specific RMM+ configuration conditions and exploited extensions are not fully enumerated, and the entry method for the reported campaign has not been established [1].

Evidence & sources

The key statements of this analysis, labeled by type, with the sources they rely on. Trendoviz does not run product tests.

  • Primary-source or vendor statementMicrosoft observed threat actors abusing ScreenConnect to install unauthorized remote-access clients and deploy the SCKit worm on customer-managed endpoints.[1]
  • Primary-source or vendor statementThe deployment chain starts with ScreenConnect commands that silently install an additional client connected to threat-actor-controlled infrastructure, followed by a batch launcher that retrieves a PowerShell decoder to decrypt and extract SCKit using device-specific key material.[1]
  • Primary-source or vendor statementSCKit maintains persistence through scheduled tasks and registry Run entries.[1]
  • Primary-source or vendor statementMicrosoft says the worm targets IT support technician workstations through hijacked authenticated ScreenConnect sessions and uses the management console to distribute payloads to other managed devices.[1]
  • Primary-source or vendor statementConnectWise's advisory describes an authentication flaw in RMM+ versions 1.0.31 and 1.0.32 that allowed command submission without a normal ScreenConnect sign-in when no access key was configured; the campaign's entry method remains under investigation.[1]
  • Primary-source or vendor statementConnectWise states that the fix for CVE-2026-84869 blocks the toolkit's attempted endpoint-to-technician spread.[1]
  • Primary-source or vendor statementRemoving an unauthorized client alone does not remove the toolkit's persistence or invalidate exposed web sessions.[1]
  • Verified factA media report states that ConnectWise warned attacks continue targeting unpatched systems.[2]

Sources

  1. 1
  2. 2

Updates & corrections

  1. First published · published automatically after passing every check

Found an error? Report it.