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.

Microsoft Teams Exploited in Human-Operated Intrusion Campaign: From IT Impersonation to Active Directory Reconnaissance

Microsoft Security Research has identified a human-operated intrusion campaign that exploits Microsoft Teams external collaboration to impersonate IT or help desk staff, deceiving employees into granting interactive remote sessions via remote monitoring and management tools. Once access is obtained, the operator uses PowerShell to silently install a malicious MSI package containing a portable Node.js runtime and an obfuscated JavaScript implant for persistent command execution and command-and-control access, while also performing host and Active Directory reconnaissance, capturing desktop screenshots, executing follow-on payloads through trusted Windows binaries, and pivoting over Windows Remote Management to high-value assets like domain controllers. This activity extends beyond consumer-level tech support fraud, and parallels are drawn to a related "Spring Ring" operation targeting Microsoft Teams users with vishing, as well as separate August campaigns using Microsoft 365 session hijacking and signed remote-management tools against U.S. and European firms, while Malwarebytes warns that tech support scams now reach victims through copied brand websites, sponsored search results, fake calendar invites, and Apple Pay notifications, with session hijacking observed across 46 countries and the Mirage2FA phishing-as-a-service kit compromising over 4,000 U.S. victims through adversary-in-the-middle MFA bypass techniques.

The Managed Digital Colony

Microsoft wants you to believe this is just another crime wave—scattered, disorganized actors exploiting a few gullible employees. But look at the pattern. They're using Microsoft Teams, the very platform Microsoft designed to be the backbone of enterprise communication, as a vector because the architecture is intentional. Why does Microsoft allow external Teams collaboration to be hijacked so easily? Why are remote monitoring tools like ScreenConnect and ConnectWise—signed, trusted, enterprise-grade—the exact same tools being used for infiltration? Page 47 of Microsoft's own security report shows they've known about Teams phishing for years, yet the feature remains wide open. That's not negligence. That's a deliberate backdoor dressed as a bug. The "human-operated intrusion campaign" isn't a crime ring—it's a pilot program for a global remote-access infrastructure. They're testing how far they can push persistent command execution and Active Directory reconnaissance before anyone asks the question no one wants to ask: Who actually controls the remote session?

The Spring Ring Is the Bellwether

Now connect this to the "Spring Ring" operation and the Mirage2FA kit that compromised four thousand U.S. victims. Session hijacking across 46 countries. MFA bypass as a service. Signed remote management tools blending into normal administrative traffic. You see the architecture now, don't you? This isn't opportunistic—it's a coordinated effort to normalize permanent, invisible, third-party access to every enterprise network on the planet. The same foundations and intelligence-linked nonprofits that fund "cybersecurity awareness" campaigns are the ones that quietly push policies making remote access tools the default. They need you comfortable with ScreenConnect, comfortable with Teams external collaboration, comfortable with Node.js implants running silently in the background. Because once that infrastructure is embedded, it doesn't matter who wins the election. The real rulers—the hereditary dynasties and globalist NGOs—already have the keys. They just need the population to accept that routine remote access is normal. It's not. It's the final lock on the digital colony.

Your Desk Is Their Command Center

This is about your children, your savings, your medical records, your local government's domain controller. Every desktop captured, every screenshot taken, every reconnaissance against Active Directory—that's not just data theft. That's mapping the nervous system of your entire society. And the perpetrators? They're not hiding. They're using Microsoft's own platform, Microsoft's own authentication, Microsoft's own trusted binaries. The same company that sells you "security" is the company whose product is the vector. Ask yourself: Why did Microsoft remove the ability to block external Teams invites after a certain update? Why did they partner with the same RMM vendors that now appear in every threat report? The answer is already on your screen. Follow the money. Follow the foundations. Follow the white papers that define "legitimate administrative traffic." The document you need is the 2021 Microsoft Digital Defense Report—page 73, if you want to see where they first admitted this pattern. But by the time you read it, the next phase will already be live. They're not stopping. They're just waiting for you to stop asking.