Security

ScreenConnect: a campaign against IT providers' servers installs fake “Windows Update” clients (CVE-2026-84869)

Since October 20, Huntress has detected hundreds of thousands of requests against 42 ScreenConnect servers. The flaw was fixed on September 8, but patching the server is not enough: each technician's client has to be updated too. Here is what to check if your IT depends on this tool.

Published on November 17, 2026 · The mitza.es team

We summarize what is known as of November 17, 2026, based on Huntress's report (November 16) and on SecurityWeek's coverage. Back in September we covered the critical ScreenConnect flaw (CVE-2026-84869) when CISA added it to its catalog of exploited vulnerabilities. What is new is that there is a real, ongoing campaign with concrete data.

What Huntress has detected

  • At least 688,000 requests to “run file” from guest connections, looking for update*.bat files, against 42 ScreenConnect servers belonging to IT providers (MSPs), from 29 IP addresses.
  • The period runs from October 20 to November 16.
  • Huntress observed a real compromise on November 12: a fake client was installed in about nine seconds. The attackers push files that run on the technician's client, which installs remote access disguised as “Windows Update”.
  • Updating the server is not enough. According to Huntress, each technician's client must be updated to version 26.6.5 or later.

The flaw: CVE-2026-84869

According to the data cited by Huntress and SecurityWeek, ConnectWise disclosed it on September 8 with a score of 9.9 out of 10 and a provisional mitigation: removing the TransferFiles permission. CISA added it to its catalog on September 11. SecurityWeek also says that Huntress then warned of exploitation since August 20; we have not been able to confirm that figure in Huntress's report, so we present it as unverified.

Huntress distinguishes this campaign from another one, the “SCKit” kit, which spreads through a vulnerable third-party extension and does not directly exploit CVE-2026-84869.

What to check

If you are the provider or you run a ScreenConnect server

  • Update the server and the technician clients to 26.6.5 or later.
  • Remove or limit the TransferFiles permission and file execution for guests.
  • Review the server's session database (a copy of App_Data\Session.db) for file execution or file sending events from guest connections, and for names such as update*.bat, marker.txt, Run-Lateral.bat or svc_payload.cmd, according to Huntress.

If you are a customer and your provider uses ScreenConnect

  • Ask whether they use ScreenConnect, whether they have updated the server and the clients, and whether they have reviewed the logs since October 20.
  • On your computers, look for remote access clients you don't recognize. Huntress mentions wclient_ folders followed by eight hexadecimal characters, wupdate_ installers in MSI format, an unknown Sync.bat in the startup folder and outbound connections on port 8041 to a suspicious domain. The full report with indicators is in Huntress's publication.
  • A “Windows Update” that is not from Microsoft is a clear sign: legitimate Windows updates are not installed with a remote access client.

Why this is especially delicate

The attackers are not going after your company specifically: they are going after your provider's remote access server, and from there they reach all of its customers. It is the same logic as in this week's N-able N-central crisis: the tool they use to support you is a door into your computers. A vendor patch from ten weeks ago is no use if part of the installation is still missing the update.

What to do: checklist for a small business

  1. Ask your provider in writing which remote access tools they use and which version their servers and their clients are on.
  2. Ask them to limit file transfer and file execution, and to enable two-step verification for their technicians.
  3. Take an inventory of the remote access software on your computers and remove what you don't use.
  4. Watch for new installations of programs that look like system updates.
  5. If you find anything suspicious, isolate the computer, change credentials and notify your provider and INCIBE (017).

To gauge how urgent this kind of advisory is, see the guide to reading a security advisory.

Quick questions

Is ScreenConnect insecure?

There is no reason to generalize: this flaw was fixed in September and the campaign takes advantage of installations that are not fully updated. But it is a very powerful tool, so whoever uses it should keep it up to date and limit what it allows.

How do I know whether my provider uses it?

Ask them; they should be able to tell you right away. You can also look at the programs installed on your computers, or in the system tray, in case a remote access client shows up.

How we can help at Mitza

We review your company's remote access, its version and its permissions, and we help you ask your provider for guarantees. See how we approach IT maintenance for small businesses or write to us from the contact page.

Related reading: attacks on Check Point gateways with PHP2Shell and the NIS2 regulation for small businesses.

Do you know which remote access tool your provider uses and whether it is up to date?

We review what remote management software is on your computers and servers, its version and who can use it.

No spam. No sales calls. Just your personalised reply.