<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Screenconnect | FirewallSync</title><link>https://firewallsync.com/tags/screenconnect/</link><description>Practical cybersecurity writing for engineering teams that ship fast.</description><language>en-us</language><image><url>https://firewallsync.com/icon-512.png</url><title>FirewallSync</title><link>https://firewallsync.com/</link></image><lastBuildDate>Sun, 15 Nov 2026 04:55:00 +0000</lastBuildDate><atom:link href="https://firewallsync.com/tags/screenconnect/index.xml" rel="self" type="application/rss+xml"/><item><title>ScreenConnect SCKit Worm via RMM+ Extension: What We Know</title><link>https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/</link><guid>https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/</guid><pubDate>Sun, 15 Nov 2026 04:55:00 +0000</pubDate><dc:creator>John Marshall</dc:creator><category>Security Operations</category><description>Huntress reports rogue ScreenConnect clients and an SCKit toolkit on 288 hosts at 48 organizations on November 11, 2026 and 205 more hosts at 41 organizations on November 13. ConnectWise disabled five third-party extensions, including RMM+, across about 400 partner environments. What is confirmed, what is not, and what to check.</description><enclosure url="https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/cover_hu9712551773197380682.jpg" type="image/jpeg" length="0"/><media:content url="https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/cover_hu9712551773197380682.jpg" medium="image" type="image/jpeg" width="1200" height="630"/><content:encoded><![CDATA[<p><img src="https://firewallsync.com/posts/screenconnect-sckit-worm-rmm-plus-extension-what-we-know/cover_hu9712551773197380682.jpg" alt="Close-up of a wiring frame densely packed with red, yellow, green and white wires on terminal pins" width="1200" height="630"></p><p><strong>What happened:</strong> On November 11, 2026, security firm Huntress saw rogue ScreenConnect clients appear on customer endpoints at 48 organizations within about 90 minutes, followed by a toolkit it calls <strong>SCKit</strong>. A second wave on November 13 hit 205 more hosts across 41 organizations. ConnectWise, which makes ScreenConnect, says it has found no compromise of its own infrastructure and no flaw in ScreenConnect itself, and has disabled five third-party extensions, including one called <strong>RMM+</strong>, across about 400 partner environments. How the attackers first got in is not yet confirmed.</p>
<p>ScreenConnect is remote-support software widely used by managed service providers (MSPs) and IT teams, so a single compromised console can reach every machine it manages. It is the second incident this week involving MSP remote-management software, after the <a href="/posts/n-able-n-central-able2shell-zero-days-offline-what-we-know/">N-able N-central Able2Shell zero-days</a>.</p>
<h2 id="timeline">Timeline</h2>
<p>Times are UTC as given by <a href="https://www.huntress.com/blog/sckit-worm-rogue-screenconnect">Huntress</a> unless noted.</p>
<table>
  <thead>
      <tr>
          <th>Date</th>
          <th>Event</th>
          <th>Source</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Aug-Sep 2026</td>
          <td>Earlier rogue ScreenConnect &ldquo;worm-like&rdquo; activity; Huntress Rapid Response</td>
          <td><a href="https://huntress.com/blog/rogue-screenconnect-installations">Huntress (Sept post)</a></td>
      </tr>
      <tr>
          <td>Sep 8, 2026</td>
          <td>ConnectWise publishes CVE-2026-84869 (CVSS 9.9), fixed in ScreenConnect 26.6.5</td>
          <td>CVE record</td>
      </tr>
      <tr>
          <td>Sep 11, 2026</td>
          <td>CISA adds CVE-2026-84869 to KEV</td>
          <td><a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog">KEV catalog</a></td>
      </tr>
      <tr>
          <td>Nov 11, ~17:47</td>
          <td>Huntress first observes suspicious activity; all 288 hosts hit within about 90 minutes</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>Nov 11, 22:45</td>
          <td>ConnectWise publishes its advisory</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>By Nov 12</td>
          <td>ConnectWise disables five RMM+-family extensions across about 400 partner environments</td>
          <td>Huntress, <a href="https://cyberscoop.com/connectwise-screenconnect-sckit-attack/">CyberScoop</a>, <a href="https://www.theregister.com/security/2026/11/12/hackers-exploiting-screenconnect-plugin-flaw-to-spread-malware-across-hundreds-of-pcs/5309361">The Register</a></td>
      </tr>
      <tr>
          <td>Nov 13, 16:12</td>
          <td>Second wave detected: 205 hosts across 41 organizations</td>
          <td>Huntress (update 5:30pm ET)</td>
      </tr>
  </tbody>
</table>
<h2 id="confirmed-vs-not-confirmed">Confirmed vs not confirmed</h2>
<table>
  <thead>
      <tr>
          <th>Claim</th>
          <th>Status</th>
          <th>Who says so</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>288 hosts across 48 organizations hit on Nov 11</td>
          <td>Reported</td>
          <td>Huntress, from its own customer telemetry</td>
      </tr>
      <tr>
          <td>205 hosts across 41 organizations hit on Nov 13</td>
          <td>Reported</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>No compromise of ConnectWise infrastructure or vulnerability in ScreenConnect itself</td>
          <td>Vendor statement</td>
          <td>ConnectWise, quoted by CyberScoop and The Register</td>
      </tr>
      <tr>
          <td>Five third-party extensions disabled across about 400 environments</td>
          <td>Vendor action</td>
          <td>ConnectWise, via Huntress, CyberScoop, The Register</td>
      </tr>
      <tr>
          <td>The ~400 environments are compromised</td>
          <td><strong>No.</strong> ConnectWise says they were flagged for having the extensions, not for confirmed compromise</td>
          <td>The Register</td>
      </tr>
      <tr>
          <td>RMM+ was the initial access vector</td>
          <td><strong>Not confirmed.</strong> Huntress calls the link suggestive; ConnectWise had &ldquo;not yet identified an initial access vector and full scope&rdquo;</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>Spread from technician workstations to other customers</td>
          <td><strong>Not observed succeeding.</strong> Huntress reconstructed the capability but did not see it work in the logs it checked</td>
          <td>Huntress</td>
      </tr>
      <tr>
          <td>Who did it</td>
          <td><strong>Not attributed</strong></td>
          <td>Huntress, CyberScoop</td>
      </tr>
  </tbody>
</table>
<p>Huntress&rsquo;s counts come from organizations that use Huntress. The total number of affected organizations is not known publicly, and the two waves&rsquo; organization counts should not be added together, since the same organization could appear in both.</p>
<h2 id="how-the-attack-worked-as-far-as-sources-say">How the attack worked, as far as sources say</h2>
<p><strong>Suspected entry point.</strong> Huntress says the activity &ldquo;seems to be related&rdquo; to RMM+ versions 1.0.31 and 1.0.32. The Register, reporting the same finding, says &ldquo;installations without a configured access key will accept a blank one.&rdquo; Per Huntress, RMM+ operates outside ScreenConnect&rsquo;s user accounts, roles and MFA, and it found no matching login activity in incident logs; the commands appeared in logs linked to RMM+. Huntress also says most RMM+ installations it saw were legitimate. The extension&rsquo;s developer has not been named in any of the reports we read.</p>
<p><strong>What was installed.</strong> According to Huntress:</p>
<ul>
<li>A rogue ScreenConnect client, installed silently by a batch-script dropper.</li>
<li>SCKit, about 16 files delivered as an encrypted package with keys tied to the victim machine&rsquo;s UUID.</li>
<li>&ldquo;RelayTrap&rdquo; components that take over the legitimate client&rsquo;s connection slot, plus a <code>TrapWatch</code> scheduled task running as SYSTEM.</li>
<li>Defender exclusions, AppLocker/SRP rules and, in one incident, a service posing as &ldquo;Windows Update Agent&rdquo;.</li>
<li>A <code>netsh portproxy</code> rule, a modified hosts file, and a tool that steals browser session cookies, including ScreenConnect&rsquo;s <code>.aspxauth</code> cookie, which Huntress describes as a way to reach further sessions.</li>
</ul>
<p>Huntress also warns that isolating a host does not remove this persistence, and that infected systems were reinfected soon after isolation ended.</p>
<p><strong>How it relates to CVE-2026-84869.</strong> The September flaw lets files be &ldquo;transferred and executed through an active remote session without authorization or Host confirmation in certain circumstances,&rdquo; per the <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/84xxx/CVE-2026-84869.json">CVE record</a>, and affects &ldquo;All versions prior to 26.6.5&rdquo;. ConnectWise&rsquo;s November guidance tells partners to confirm every technician client runs 26.6.5 or later. Neither ConnectWise nor Huntress says the November campaign exploited this CVE, so treat the upgrade as hardening against the spread path, not as the root cause.</p>
<h2 id="what-to-check-in-your-environment">What to check in your environment</h2>
<p>If you run ScreenConnect, cloud or on-premises:</p>
<ol>
<li><strong>Extensions.</strong> Check for Labtech Plus, RMM Plus, RMM+, RMM Plus Password Link and RMM+ Password Link. ConnectWise disabled them on hosted instances; on-premises partners must disable them themselves.</li>
<li><strong>Client versions.</strong> Confirm technician clients are on 26.6.5 or later.</li>
<li><strong>Do not triage through ScreenConnect.</strong> Huntress advises against connecting to a suspect host through ScreenConnect and recommends WinRM or another out-of-band tool. If a technician already connected to a suspect host, investigate that technician&rsquo;s workstation from a clean device.</li>
<li><strong>Hunt for the artefacts Huntress lists:</strong> an unfamiliar ScreenConnect client alongside the legitimate one, a <code>TrapWatch</code> scheduled task, <code>C:\ProgramData\RelayTrap\</code>, toolkit files in <code>%TEMP%</code>, a <code>RelayTrapLiteAlert</code> Run value, unexpected <code>netsh interface portproxy</code> rules, and hosts-file changes. Huntress publishes hashes and network indicators in its post.</li>
<li><strong>Sessions and credentials.</strong> Terminate active ScreenConnect web sessions, rotate credentials, and revoke browser and identity-provider sessions.</li>
<li><strong>Audit history.</strong> Review Run Command and Toolbox history and instance audit logs for activity with no matching user login.</li>
</ol>
<p>For engineers outside the MSP world, the transferable lesson is about plugins: any extension that runs commands with its own authentication path is a second front door to your remote-access tool. Inventory extensions with the same rigour as user accounts, and require that their access keys are set rather than defaulting to empty. For tracking the ScreenConnect CVEs already in KEV, see <a href="/posts/cisa-kev-json-feed-what-each-field-means-and-how-to-match-it-against-a-scanner-export/">how to match the CISA KEV JSON feed against a scanner export</a>.</p>
<h2 id="sources-and-verification">Sources and verification</h2>
<table>
  <thead>
      <tr>
          <th>Important claim</th>
          <th>Source</th>
          <th>Status</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Counts, timeline, RMM+ versions, toolkit components, recommendations</td>
          <td><a href="https://www.huntress.com/blog/sckit-worm-rogue-screenconnect">Huntress, Nov 11 2026, updated Nov 13</a></td>
          <td>Verified (Huntress telemetry)</td>
      </tr>
      <tr>
          <td>ConnectWise found no infrastructure compromise or ScreenConnect vulnerability</td>
          <td><a href="https://cyberscoop.com/connectwise-screenconnect-sckit-attack/">CyberScoop, Nov 12 2026</a>, <a href="https://www.theregister.com/security/2026/11/12/hackers-exploiting-screenconnect-plugin-flaw-to-spread-malware-across-hundreds-of-pcs/5309361">The Register, Nov 12 2026</a></td>
          <td>Verified (vendor statement)</td>
      </tr>
      <tr>
          <td>~400 environments are an exposure count, not compromise</td>
          <td>The Register</td>
          <td>Qualified (vendor statement as reported)</td>
      </tr>
      <tr>
          <td>CVE-2026-84869 description, CVSS 9.9, fixed in 26.6.5</td>
          <td><a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/84xxx/CVE-2026-84869.json">CVE record</a></td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>CVE-2026-84869 added to KEV on Sep 11, 2026</td>
          <td><a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog">CISA KEV</a> (kev-data JSON)</td>
          <td>Verified</td>
      </tr>
      <tr>
          <td>No attribution</td>
          <td>Huntress, CyberScoop</td>
          <td>Verified</td>
      </tr>
  </tbody>
</table>
]]></content:encoded></item></channel></rss>