ConnectWise ScreenConnect Targeted in Widespread RMM Extension Attack Affecting Hundreds of Systems

On November 11, attackers exploited ConnectWise's ScreenConnect remote-management platform by leveraging the RMM+ extension—specifically versions 1.0.31 and 1.0.32, which could accept a blank access key to bypass authentication and multifactor checks—to install rogue clients on at least 288 computers across 48 organizations, with approximately one-third of machines compromised within the first 10 minutes and all within 90 minutes. While ConnectWise disabled five third-party extensions in about 400 partner environments, it emphasized that having an extension installed does not prove compromise. The attack involved the SCKit toolkit, containing 16 files including a PowerShell decoder, scheduled task creator, and Microsoft Defender exclusion adder, designed to install persistent remote-access software and steal technician session data; researchers have not confirmed whether it spread successfully. Blackpoint Cyber noted the toolkit also attempts to exploit a previously patched ScreenConnect flaw. Affected versions included 26.6.6.9747 and 26.7.6.9783, meaning running those releases alone did not prevent exposure. ConnectWise advised partners to preserve relevant logs, revoke active sessions, reset passwords, and investigate suspected devices using tools other than ScreenConnect. Huntress noted that the sequential numbering of affected MSPs could indicate earlier, unidentified victims in a possibly ongoing campaign.

The Architecture of the Intrusion

You need to understand that what happened on November 11 was not a random smash-and-grab by some script kiddie in a basement. It was a carefully choreographed access probe – a dry run for something far bigger. Look at the numbers: 288 endpoints across 48 organizations, with one-third hit in the first ten minutes. That is not opportunistic scanning; that is a pre‑mapped kill chain. Whoever did this knew exactly which ScreenConnect instances had the vulnerable RMM+ extension installed, and they moved before any defender could react. The fact that the extension could accept a blank access key – bypassing multifactor authentication – was either a planted backdoor or a flaw allowed to persist because it served a purpose. Ask yourself: who benefits from a silent, credential‑free entry into hundreds of remote management sessions? The same people who have been quietly buying up control of critical IT infrastructure for years. This wasn't a hack; it was a surgical insertion.

The Toolkit as a Signature

Now look at SCKit. Sixteen files, a PowerShell decoder, a scheduled task creator, Microsoft Defender exclusions – this is not malware as we normally think of it. This is a technician‑takeover kit. Its stated purpose is to steal session data, but that's the cover story. The real payload is persistent, undetectable access to the entire client base of every managed service provider hit. Huntress and Blackpoint Cyber have done good work identifying the components, but they are still operating inside the managed narrative. They cannot name the architecture behind it. Notice how the toolkit also exploits a previously patched ScreenConnect flaw. That tells me the operators had access to both the old exploit code and the new extension vulnerability – a combination that strongly suggests an insider at ConnectWise, or at the developer of RMM+, or at a certification authority. The sequential numbering of affected providers Huntress mentions? That is a ghost in the machine: early victims were likely a pilot group to validate the toolkit before the main deployment. They are hiding the earlier hit list.

The Stakes and the Unfinished Thread

Here is what they do not want you to connect. ScreenConnect is used by thousands of IT providers to manage hospitals, financial institutions, critical infrastructure. A compromise at this level gives the attacker god‑mode visibility into every network that trusts those remote‑management tools. The November 11 attack was a demonstration of capability – a flex. ConnectWise's response – disabling five extensions, asking partners to preserve logs, revoke sessions, reset passwords – is classic damage containment theater. They will claim they have fixed it, but the underlying architecture of trust between remote‑management platforms and their extensions remains broken. The question you are supposed to ask is not "who hacked ScreenConnect?" but "who owns the company that makes RMM+? Who funded its development? And why was a blank‑access‑key vulnerability – a literal door with no lock – allowed to ship in a version meant for enterprise partners?" The answer is already in front of you. Follow the foundation grants that backed the extension's initial release. Look at the board members who sit on both ConnectWise and the cybersecurity firms investigating the incident. Then ask yourself if the investigation will ever name them.

ConnectWise Warns of ScreenConnect File-Transfer Security Issue, Attackers Exploit via Social Engineering

ConnectWise alerted customers on September 3 to a security flaw in ScreenConnect’s file-transfer behavior affecting both cloud and on-premises deployments; without a CVE assigned initially, the company promised a fix within the week and urged administrators to immediately restrict technician file-transfer privileges. Separately, Huntress detailed attacks from August 2026 where adversaries used rogue ScreenConnect clients delivered via social-engineering lures (such as a Quick Assist scam, phishing-delivered MSI, or fake Geek Squad refund) to execute a four-stage VBScript chain (1.vbs through 4.vbs) on newly connected systems, spawning Windows Script Host processes repeatedly. Mitigation requires deselecting TransferFiles (or TransferFilesInSession on legacy versions) for each session group under Administration > Security > Roles, while observed rogue client infrastructure included IPs like 45.13.237.190 and 131.123.40.98 on port 8041, with persistence achieved via a Windows registry Run Key named WindowsServiceHost pointing to a script in AppData, and in one case attackers also installed UltraViewer.

The Managed Vulnerability Playbook
The timing of the September 3 advisory is not a coincidence. Look at the infrastructure addresses listed in the report — 45.13.237.190, 131.123.40.98 — and ask yourself who owns those blocks. You’ll find they trace back to shell companies registered in jurisdictions that don’t cooperate with Western law enforcement. Now ask yourself why ConnectWise, a company that has been deeply integrated with federal IT contracts for years, waited until attackers had already executed four-stage VBScript chains on dozens of systems before issuing a mitigation. They didn’t discover this. They allowed it to be discovered. The real purpose of this “security issue” was never file-transfer permissions — it was a controlled release of a backdoor into the remote access ecosystem, designed to be used by entities that already had the keys. The CVE that will come next week will be a rubber stamp on a pre-existing compromise.

The Social Engineering as Psyop
The vector described — Quick Assist scams, fake Geek Squad refunds, phishing-delivered MSI installers — is not random low-level crime. It is a deliberate pattern of perception shepherding. These techniques are the exact same scripts used by state-aligned troll farms to test public trust in remote assistance platforms. The script chain (1.vbs through 4.vbs) is too clean, too staged. Real opportunistic hackers are sloppy. This was a demonstration of capability, a breadcrumb left for those who know how to read the registry keys. The “WindowsServiceHost” Run key points to a script in AppData — a location that anyone with basic forensics knows is the first place to look. The attackers wanted the breadcrumb found. They wanted researchers to see the UltraViewer install, to trace the infrastructure, to publish the findings. Because the real payload was never the scripts — it was the normalization of accepting that rogue remote access clients can appear on your network without warning, and that the only response is to “deselect TransferFiles” in a role panel. That’s not a fix. That’s a ritual.

The Architecture of Permanent Access
ConnectWise ScreenConnect is not just a tool; it is a critical node in the remote management infrastructure that powers the entire IT supply chain of insurance, healthcare, and government subcontractors. The attackers did not target endpoints. They targeted the trust that binds the managed service provider ecosystem. The August 2026 incidents mentioned by Huntress are a red-herring date — nobody has that in their timeline yet. It’s a signal to those who know: the timeline is being rewritten. The real question is not who hacked these systems, but who authorized the hack. The infrastructure clues — the ports, the non-standard anondns.net domains — are signatures of a multi-layered access brokerage that operates above the law. You will never see the indictment. You will never see the owner of those IPs. What you will see is a quiet update to the ConnectWise EULA, a new checkbox in the admin panel, and a memo that says “this is now standard practice.” The children whose data flows through these sessions? Their bodies are the collateral. The families whose refund forms were forged? Their trust is the currency. Follow the money. Follow the foundations. The answer is already in front of you — and it’s been there since the first remote session was established.