ScreenConnect Vulnerability MSP Guide: Harden Your RMM
In November 2026, BleepingComputer reported that ConnectWise was investigating an active malware campaign against MSPs. Attackers used compromised ScreenConnect environments to push rogue remote-access clients to customer devices. Huntress believes initial access came through RMM+, a third-party ScreenConnect extension, and it reported a worm-like malware called SCKit, covered in a second BleepingComputer article.
On November 17, SC World reported a critical ScreenConnect flaw (CVE-2026-84869) that lets a guest run a malicious file on a technician's computer. This guide turns those reports into practical steps for MSP owners and IT leaders.
How do I check whether my ScreenConnect instance or its extensions were exposed?
Start by listing every ScreenConnect server you run, every installed extension, and every version in use. Then review logs for activity you cannot explain, and compare your deployed clients against what you intended to install. Treat any gap as a lead to investigate.
Work through this in order:
- Inventory. Record each instance, its version, who administers it, and whether it faces the internet. Include test and legacy servers, which are often forgotten.
- Extensions. List all third-party extensions, including RMM+ if you use it. Note who installed each one, when, and whether you still need it.
- Logs. Look for new administrator accounts, changed permissions, unfamiliar extensions, odd login locations and sessions at unusual hours.
- Endpoints. Compare the remote-access agents present on client devices with your own deployment records. Any agent tied to an instance you do not recognize is suspect.
- Technician sessions. Check whether guests recently ran files on technician machines, given the CVE-2026-84869 report.
If you find anything unexplained, preserve logs and snapshots before you clean up. Evidence you delete cannot help your investigation or your insurer.
Which RMM hardening steps cut the risk of one compromised tool reaching every client?
The goal of RMM security hardening is to stop one foothold becoming a fleet-wide event. Limit who can reach the tool, limit what each account can do, and limit how far one instance spans across clients. A compromise should hit a small segment, not everyone.
This is the core of defending against an MSP supply chain attack, because attackers target you precisely to reach your clients.
- Enforce phishing-resistant MFA on every technician and administrator login, with no shared accounts.
- Restrict network access. Put the admin interface behind a VPN or an allowlist where you can, rather than leaving it open to the internet.
- Apply least privilege. Give technicians access only to the clients they support, and keep full administrator rights to a very small group.
- Segment by client or tier. Separate instances or tightly scoped roles reduce how many devices one stolen credential reaches.
- Remove unused extensions and accounts, and restrict who can install new ones.
- Control the agent. Use allowlisting so only your approved remote-access clients can run on managed endpoints, and alert on any others.
- Log centrally. Send RMM logs to a system the RMM admins cannot edit.
- Test your backups and keep them isolated from the RMM's reach.
These measures also make secure remote access for MSPs easier to explain to clients and auditors, because each control is concrete and checkable.
How should an MSP tell clients about a possible tool compromise?
Tell clients early, plainly and in writing, even when facts are incomplete. Say what you know, what you do not yet know, what you are doing, and what they should do. Good MSP incident communication to clients protects trust better than silence followed by a polished report.
A workable approach:
- Decide who speaks. Name one owner for messaging and one technical lead, so clients hear a consistent story.
- Send a first notice quickly. State that you are investigating a possible compromise of a remote management tool, whether their environment is confirmed affected, and when the next update will arrive.
- Give actions. For example, watch for unexpected remote-access software, report odd prompts, and confirm that any technician contact is genuine.
- Offer a direct channel. Provide a phone number and a named contact, since email may be part of the concern.
- Update on a schedule, even if the update is that nothing has changed.
- Follow up after containment with findings, fixes and what changes going forward.
Avoid speculation, blame and technical jargon. Check contract terms and any legal or insurance notification duties with your counsel before you send anything.
Why are technician workstations now a target, and how do we protect them?
Technician workstations hold the keys: logged-in RMM sessions, stored credentials and access to many client networks. The reported flaw, which lets a guest run a malicious file on a technician's computer, shows the technician's machine can be the entry point. Protect these endpoints like servers.
Practical protections:
- Dedicated admin devices used only for management work, not general browsing or email.
- Hardened builds with endpoint detection and response, disk encryption and application allowlisting.
- Isolated sessions. Open guest or client-initiated sessions in a sandbox or virtual machine where possible.
- No local admin by default, and no saved passwords in browsers.
- Prompt patching of the remote-support client and operating system.
- Training. Technicians should know that a file offered during a session is a risk, however routine the request looks.
- Monitoring. Alert on unusual processes spawned by the remote-support client.
How can an outside NOC or helpdesk partner reduce the impact of an RMM compromise?
An outside partner adds independent eyes and a second set of hands. It can watch for abnormal behavior around the clock and help you triage during an incident. It does not replace your own controls, and it must be held to the same hardening standards.
A white-label NOC for MSPs can monitor networks, servers and endpoints independently of your RMM, so a compromised tool is less likely to blind you. Round-the-clock alert triage can catch unexpected agents or traffic outside your working hours, when attackers often move. Extra helpdesk capacity also helps when you need to contact many clients quickly.
Before you choose a partner, ask:
- How do their technicians access your tools, and with what MFA and device controls?
- Do they use separate credentials per person, with logging you can review?
- What are their response times by priority, and are they in the contract?
- Which security frameworks do their practices align with, and what evidence can they show?
- What is the plan if their own environment is compromised?
HEX64 Infosolutions provides 24/7 NOC monitoring, alert triage and incident response, plus white-label NOC and helpdesk for MSPs. Response times are set by contract, with P1 within 5 minutes. New clients begin with a pilot, so you can test the working relationship before committing further.
How fast should third-party RMM plugins and patches be reviewed and applied?
Apply critical patches for internet-facing management tools within days, not weeks, and sooner when exploitation is reported. Review third-party plugins before installing and again on a regular schedule. Speed matters most for the tools that can reach all your clients.
Build a simple policy:
- Subscribe to vendor and extension advisories, and assign someone to read them daily.
- Rank by exposure. Internet-facing RMM servers and anything reported as actively exploited go first.
- Test quickly on a staging instance, then roll out in stages with a rollback plan.
- Vet extensions. Check the publisher, what permissions it needs, how it is updated, and whether you could live without it.
- Set an emergency path. Define in advance who can approve an out-of-cycle patch or disable an extension immediately.
- Review quarterly. Remove extensions nobody uses.
If a vendor has not patched a reported flaw, consider temporary measures: restrict access, disable the affected feature or extension, and increase monitoring until a fix is available.
Frequently asked questions
What should I do first if I suspect my ScreenConnect server is compromised?
Isolate the server from the internet, preserve logs and snapshots, and rotate all administrator and technician credentials. Then check endpoints for agents you did not deploy. Bring in your insurer and incident response help early.
Is a ScreenConnect vulnerability MSP risk only about ScreenConnect?
No. The same pattern applies to any RMM or remote access tool, because attackers value a single path into many networks. The hardening steps here apply to whatever platform you run.
Do I have to tell clients if I am not sure they were affected?
Often it is wise to, but your contracts and local laws decide the obligations, so check with counsel. A short, factual notice that you are investigating usually serves clients better than waiting.
Should we stop using third-party extensions altogether?
Not necessarily, but each one widens your attack surface. Keep only those with a clear business need, vet the publisher, limit permissions and patch them as quickly as the core product.
Can a white-label partner see everything in my RMM?
Only what you grant. Give partner technicians named accounts, least-privilege roles and MFA, and review their access and logs regularly.
To see how HEX64 works with MSPs on monitoring and helpdesk support, visit the MSP partnership page.