Intelligence Brief: SCKit Malware Exploits ScreenConnect Sessions to Target US Managed Service Providers

Sovereign Geopolitical Intelligence &
Situational Awareness Terminal
[SYSTEM STATUS: OPERATIONAL]
[INGESTION RATE: — briefs/day]
[THREAT LEVEL: ELEVATED]

◈ Source Credibility Index

Single-source assessment (1 source)(swapupdate.in)3/5 — Generally ReliableNATO C/3 — Fairly Reliable / Possibly True

1. BLUF (Bottom Line Up Front)

Available reporting supports an ongoing ScreenConnect-related intrusion in which attackers used SCKit capabilities to abuse authenticated support sessions and seek access to managed service provider (MSP) technicians’ workstations. The best-supported explanation is that attackers gained access through malicious third-party extensions or another unconfirmed route, then used trusted ScreenConnect functions and session theft to attempt wider access; successful propagation to technician workstations has not been established. Reporting published on November 15 adds ConnectWise’s response and Huntress’s finding of a separate RMM+ authentication flaw, but does not identify patient zero. This assessment is likely, with moderate confidence, because the toolkit and attack methods are described in detail while the initial access route and extent of compromise remain unconfirmed.

2. Key Judgments — ScreenConnect MSP Intrusions

  1. Blackpoint Cyber’s Adversary Pursuit Group (APG) said the recovered SCKit toolkit can exploit CVE-2026-84869 and hijack authenticated operator sessions. APG’s testing found that a fully patched ScreenConnect client blocks the known exploit payload; the reporting does not establish that attackers used an unpatched client for initial access.
  2. Malicious third-party extensions are a plausible initial access route, not a confirmed one. ConnectWise said its initial assessment suggested abuse of independent extensions, while Blackpoint’s Nevan Beal said there was insufficient evidence to confirm that route.
  3. The most consequential described mechanism is RelayTrap, which attempts to send malware from a managed endpoint toward a technician connecting to investigate it. Available reporting says there is no evidence that SCKit successfully propagated to a technician workstation.
  4. Huntress separately identified a blank-default access key flaw in RMM+ versions 1.0.31 and 1.0.32. It reported commands across several ScreenConnect instances within minutes, with no corresponding login activity in the logs it reviewed; this finding does not by itself establish that RMM+ was the initial access route in the SCKit activity.

3. Analysis of Competing Hypotheses (ACH)

Hypothesis Supporting Evidence Contradicting Evidence Evidence Gaps Probability
H-A: Attackers entered through a malicious extension or another compromised access path, then used SCKit to abuse ScreenConnect sessions and attempt lateral movement. Blackpoint describes SCKit’s session-hijacking and RelayTrap capabilities. ConnectWise said activity may involve abuse of independent extensions. Blackpoint reported unauthorized Access clients and use of existing agents to run commands. Blackpoint said it could not confirm malicious extensions as initial access. ConnectWise said the presence of extensions alone does not establish compromise. Successful propagation to technician workstations is not evidenced. Forensic evidence identifying patient zero, the access path, affected partners, and any successful technician workstation compromise. 58%
H-B: Attackers used CVE-2026-84869 against an unpatched ScreenConnect client as the initial entry route. The recovered toolkit includes functionality associated with the vulnerability, which permits unauthorized file transfer and execution through an active remote session. APG said the vulnerability is patched and testing confirmed the patch blocks the exploit. Blackpoint said there is no evidence an unpatched client was the initial entry point. Patch status at affected environments and forensic evidence of any successful exploit at initial access. 17%
H-C: The reported commands and compromise risk primarily reflect the RMM+ blank-key flaw, with the SCKit campaign’s broader propagation remaining unconfirmed or separate. Huntress found versions 1.0.31 and 1.0.32 could accept a blank access key when none was configured. It reported commands on several instances without corresponding login activity. Blackpoint describes a distinct SCKit toolkit, unauthorized Access clients, and session-theft capabilities. Reporting does not establish that RMM+ accounts for all observed activity or that it delivered SCKit. Instance-level logs linking RMM+ commands to SCKit, affected organizations, and the relationship between the extension flaw and the campaign. 18%
H-D (Maskirovka / Strategic Deception): The apparent signal is a deliberate disinformation, fabrication, or denial-and-deception operation designed to shape perception or mask a different course of action. Attribution and initial access remain unresolved, and vendor and security-company statements may reflect different access to evidence. Those conditions leave room for incomplete or strategically framed accounts. Blackpoint, ConnectWise, and Huntress describe distinct technical findings and uncertainty rather than making a single uniform claim. The reporting includes concrete test results and explicit limits on what is known; it offers no direct evidence of deliberate fabrication. Independent forensic validation, technical artifacts from affected environments, and later findings that confirm or materially contradict the published accounts. 4%

ACH Assessment: H-A is currently best supported because the reporting describes SCKit’s capabilities and ConnectWise identified extension abuse as a possible access route, while neither source confirms initial access. The separate RMM+ finding makes H-C a credible alternative explanation for some commands, but no reported evidence links it directly to SCKit. H-B is weakened by the patch test and the absence of evidence that an unpatched client was the entry point. The sources do not report a direct contradiction over whether SCKit can perform the described actions; the main uncertainty is whether, where, and how those capabilities were used successfully. This is partial reporting, not proof that all extensions or environments were compromised.

4. Key Assumption Check (KAC)

  • Critical Assumptions: First, that Blackpoint’s recovered toolkit is representative of activity on affected partner systems; if it is not, the described attack chain may overstate the campaign’s operational reach. Second, that reported ScreenConnect commands and SCKit activity are related; if they are separate incidents, the apparent campaign may combine distinct access paths. Third, that patch status can be established on affected clients; if relevant systems were patched before activity, CVE-2026-84869 becomes less plausible as an entry mechanism. Fourth, that session theft or RelayTrap succeeded in at least some environments; if neither did, risk to other customer environments is lower than the toolkit’s capability implies.
  • Information Gaps: Available reporting does not identify patient zero, the affected partners or customer endpoints, the number of compromised systems, or whether any technician workstation was successfully infected. These gaps require partner-level forensic timelines, endpoint and ScreenConnect audit logs, extension configuration and version records, and review of technician workstation browser data and processes. It also does not report whether ConnectWise’s investigation or Huntress’s findings have since established a link between RMM+ and SCKit; technical indicators and incident timelines from affected instances would help resolve that relationship.
  • Bias & Deception Risks: The account is mediated through The Hacker News and depends heavily on vendor and security-company assessments. Blackpoint’s researchers reported toolkit capabilities and limits; ConnectWise described an initial assessment and precautionary response; Huntress reported its own RMM+ finding. These are useful but interested-party claims, and they may reflect different incident visibility. The principal risk is framing: describing a capability can be mistaken for proof of successful exploitation. The reporting gives no history sufficient to assess a “cry wolf” pattern. Independent logs and forensic artifacts would reduce these risks.

5. Implications and Strategic Risks — ScreenConnect and MSP Networks

The described attack path turns access to one managed endpoint into a possible route to technician workstations and other customer environments. If session theft succeeds, routine support connections and shared administrative access can extend the impact beyond the initially affected system. Conversely, the absence of reported successful technician compromise limits what can be concluded about actual reach. The United States is an inferred location in the event summary, not a location established by the article.

Cyber / Information Space — ScreenConnect Sessions

APG said SCKit can use authenticated sessions and legitimate Run Command functionality to deploy software under the NT AUTHORITY\SYSTEM context. That approach can reduce the value of patching alone: patching blocks the known CVE exploit, but does not protect a valid, compromised operator session. RelayTrap also creates a risk that an investigation connection could become an opportunity to target the connecting technician.

Economic / Social — MSP Customer Environments

An MSP technician may administer endpoints for multiple customers, so a compromised workstation or stolen session could expose systems beyond the initial customer environment. The article does not report confirmed downstream outages, data theft, financial losses, or affected customer counts. If investigators find cross-customer access, customers may need to assess administrative activity and the trust they place in shared support infrastructure.

Political / Geopolitical — US Cybersecurity Response

CISA added CVE-2026-84869 to its Known Exploited Vulnerabilities catalog on September 11, 2026, and required federal agencies to apply fixes by September 14. That prior exploitation context makes patch status relevant, but the article does not attribute the current activity to a state or identify a political motive. ConnectWise’s precautionary disabling of five third-party extensions is a vendor action; Blackpoint said it found no technical link between those extensions and SCKit.

Security — ConnectWise Partner Operations

ConnectWise said it was investigating reports of malicious activity affecting a limited number of partners and advised on-premises partners to disable identified extensions. The company also said the presence of those extensions alone does not establish compromise. As partners review systems, distinguishing ordinary administrative commands from unauthorized activity will depend on the quality and retention of session, extension, and endpoint records.

6. Recommendations and Outlook

  • Immediate Actions (0–30 days): Monitor ConnectWise, Blackpoint, and Huntress updates for confirmed initial access, affected versions, and links between RMM+ and SCKit. Review ScreenConnect client patch status and extension inventories, including RMM+ versions 1.0.31 and 1.0.32 and whether an access key was configured. Check for unauthorized Access clients, Run Command activity, suspicious administrative commands, and the reported artifacts sc.msi, sckit-run.bat, sckit-decoder.ps1, SilentForceInstall-WithUninstall.ps1, and connections to ns.mo7sen[.]dev. Review technician workstation browser data and process memory for evidence of session theft, preserving logs and forensic evidence before changing systems.
  • Medium-Term Posture (1–12 months): Track whether partners add additional authentication or session validation for high-impact and bulk administrative actions, as Blackpoint recommended. Assess whether MSPs separate technician workstations from routine endpoint access and maintain records that connect extension activity, operator sessions, and endpoint commands. Monitor for evidence that the same access path is used across more than one partner or customer environment.
  • Scenario Outlook: Best: Investigation finds no successful technician workstation propagation; triggers include patched clients, no suspicious sessions, and no unauthorized Access clients. Worst: Forensics confirm stolen operator sessions and access across multiple customer environments; triggers include anomalous authenticated sessions, related commands across instances, or confirmed RelayTrap execution. Most likely: Partners identify a limited number of affected environments, while initial access and the RMM+ relationship remain unresolved; triggers include continued precautionary extension actions and further forensic updates without evidence of broad propagation.

Overall confidence: Moderate (66%; likely that the reporting accurately describes SCKit’s capabilities and a real ScreenConnect-related campaign, but not that its full attack chain succeeded).

7. Key Individuals and Entities

Name Role / Affiliation Relevance to Assessment
Sam Decker APG researcher, Blackpoint Cyber Named by APG as a researcher who reported testing that the CVE-2026-84869 patch blocks the exploit payload.
Nevan Beal Principal MDR analyst at Blackpoint Cyber; APG researcher Said initial access may involve malicious extensions but that evidence was insufficient to confirm it; also described limits on determining patient zero and timing.
Blackpoint Cyber Adversary Pursuit Group Blackpoint Cyber research group Reported SCKit capabilities, the CVE patch test, and the absence of evidence for successful technician workstation propagation.
ConnectWise ScreenConnect vendor Reported an investigation, disabled five third-party extensions where it could, and advised on-premises partners to disable them.
Huntress Cybersecurity company Reported an authentication flaw in RMM+ versions 1.0.31 and 1.0.32 and commands on several instances.
Unidentified threat actor(s) Actor or actors behind the reported activity; attribution not established The reporting describes SCKit capabilities and activity but does not identify the operator or establish responsibility.
ConnectWise ScreenConnect Remote access software used by partners and MSP technicians The software, its extensions, and its authenticated support sessions are central to the reported attack path.



Explore more: Cybersecurity Briefs · Daily Summary · Support us

WorldWideWatchers · Intelligence Assessment
Source Verification & Governance Report

2026-11-16 11:26:06 UTC
a7356723

Source Reliability
3
Generally Reliable
Source Credibility Index

NATO C · Fairly Reliable
1 source(s) · 1 domain(s)

Information Credibility
PASS
100% faithful
AI faithfulness check

NATO 3 · Possibly True
Corroboration: 53% (MODERATE) · Conflicts: 0 · HIGH

Governance Decision
Cleared
✓ YES Publication
✓ YES Dissemination
✓ Cleared Analyst review

Corroborating Sources
Source SCI Role
swapupdate 3 SOURCE_DOCUMENT
Generated by WorldWideWatchers Intelligence Pipeline · 2026-11-16 11:26:06 UTC · Machine-generated assessment — subject to analyst review before operational use.