ConnectWise says attacks against its ScreenConnect remote access software are far from over, even as it closed the book on one part of the incident. The company announced on Monday that it has finished investigating unauthorized access directed at partner-run ScreenConnect environments — but warned that a separate stream of intrusions against customer-hosted, on-premises deployments is still being reported.

The distinction matters. Two different problems are running in parallel, and closing one does not close the other.

What's closed, and what's still open

Closed: the partner-environment investigation. For customers whose concern was the partner side of the house, that chapter is done.

Still open: exploitation of on-premises installations. ConnectWise said it continues to see activity against self-hosted environments where previously flagged third-party extensions remain enabled. Tooling circulating under the name SCKit has been linked to attempts against unpatched instances, replacing bespoke per-target reconnaissance with a more repeatable process.

That is the real news hook here. ScreenConnect is remote monitoring and management (RMM) software, and RMM tools sit at a privileged point in managed service provider (MSP) trust chains: a foothold in one can become a pathway into many downstream customer networks. Anything that makes exploitation of the unpatched tail of that install base easier raises the practical exposure for anyone still running older versions.

ConnectWise's core recommendation is specific: ensure the technician client is running version 26.6.5 or later.

What administrators should do now

  • Upgrade the technician client to 26.6.5 or later, and verify the version on every system that connects to your ScreenConnect instance — not just the server itself.
  • Audit third-party extensions and disable anything unnecessary or unrecognized. ConnectWise tied continuing on-premises activity to environments where flagged extensions remain enabled.
  • Treat self-hosted, on-premises installs as internet-facing attack surface. Internet-reachable RMM servers with outdated components are precisely what tooling like SCKit is built to find.

Why this is more than a routine advisory

Vendor patches for RMM products recur regularly enough that they blur together. What separates this story is the combination of an active exploitation campaign, tooling that appears to lower the skill floor for attackers, and a product category whose compromise propagates through MSP relationships rather than stopping at a single endpoint. For IT teams and managed service providers broadly — including those running lean, self-managed deployments — the practical takeaway is that "we host it ourselves" does not mean "we are outside the threat model." It usually means patching and extension hygiene are entirely your own responsibility.

The escalation path is straightforward: unpatched instance, enabled third-party extension, privileged remote access, downstream trust.

Source: The Hacker News. ConnectWise's full advisory should be treated as the authoritative reference for version and extension specifics.


ConnectWise 表示,針對其 ScreenConnect 遠端存取軟件的攻擊遠未結束,儘管公司已就事件其中一部分劃上句號。該公司周一宣布,針對合作夥伴營運的 ScreenConnect 環境的未授權存取調查已經完成——但同時警告,另一條針對客戶自行託管、本地自架(on-premises)部署的入侵仍在不斷通報中。

這區別至關重要。兩類問題正在同步發展,結束其中一項並不等於解決另一項。

已結案的,與仍未了結的

已結案:合作夥伴環境的調查。對擔心合作夥伴一方問題的客戶而言,該章節已告一段落。

仍未了結:本地自架安裝的漏洞利用。ConnectWise 表示,其持續見到針對自行託管環境的攻擊活動,這些環境中先前已被標記的第三方擴充功能仍然啟用。以 SCKit 為名流傳的工具已被關聯到針對未修補實例的攻擊嘗試,以更具可重複性的流程取代了逐一目標的專屬偵察(reconnaissance)。

這才是本則報導的真正新聞重點。ScreenConnect 屬於遠端監控與管理(RMM)軟件,而 RMM 工具正處於管理式服務供應商(MSP)信任鏈的特權位置:在其中一個節點取得立足點,便可成為通往眾多下游客戶網絡的途徑。任何令這批安裝基礎中未修補尾部更易遭利用的因素,都會加大所有仍在運行舊版本者的實際威脅範圍。

ConnectWise 的核心建議相當具體:確保 technician client 正在運行 26.6.5 或更新版本。

系統管理員現階段應採取的措施

  • 將 technician client 升級至 26.6.5 或更新版本,並核對每一台連接到你的 ScreenConnect 實例的系統的版本——而不只是伺服器本身。
  • 審核第三方擴充功能,停用任何不必要或不明確的項目。ConnectWise 將持續的本地自架活動與仍啟用被標記擴充功能的環境聯繫起來。
  • 將自行託管的本地自架安裝視為面向互聯網的攻擊面。可從互聯網到達的 RMM 伺服器配上過時元件,正是 SCKit 之類工具專門用來搜尋的目標。

為何這不只是例行公告

RMM 產品的廠商補丁發布相當頻繁,以至容易令人混淆。本則新聞有別於其他之處,在於三者的結合:正在進行的漏洞利用行動、看似降低攻擊者技術門檻的工具,以及一類透過 MSP 關係蔓延而非止於單一端點的產品。對於 IT 團隊及廣義上的管理式服務供應商——包括那些運行精簡、自行管理部署的——實際的啟示是:「我們自己託管」並不等於「我們置身威脅模型之外」。這通常只意味著修補及擴充功能管理的責任完全由你承擔。

攻擊升級路徑十分直接:未修補的實例、啟用中的第三方擴充功能、特權遠端存取、下游客戶的信任鏈。

來源:The Hacker News。ConnectWise 的完整公告應被視為版本及擴充功能細節的權威參考。

新聞來源 / Original News Source