Skip to content

Cybersecurity

ScreenConnect abused: how to make remote IT support secure

A campaign of attacks used ScreenConnect, a remote support tool, to install unauthorised access and target technicians. Here is what it means for your company and which checks to make now.

6 min read

The tools that let your IT provider connect to your company PCs are convenient, but they are also a privileged way in. A newly documented case involving ScreenConnect shows why remote support security deserves to be treated as a priority, even if you have never heard of this software.

At a glance

  • In November 2026 a campaign came to light that abused ScreenConnect, remote support software used by IT providers, to install hidden access on their clients' PCs.
  • The attack also targets the technicians who connect to provide support, and from there it can reach other clients of the same provider.
  • Uninstalling the suspicious program is not enough: scheduled tasks, antivirus changes and still-valid login sessions remain.
  • Every company should know which remote access tools are installed on its devices and ask its IT provider how they are protected.

What happened with ScreenConnect and SCKit

Since 11 November 2026 ConnectWise, the maker of ScreenConnect, has reported unauthorised access to cloud instances of the software belonging to MSPs, the managed service providers that run IT for other companies. Microsoft has confirmed the activity and analysed how it works in a report by its threat intelligence team.

In short, the attackers use the provider's legitimate console to install a second copy of ScreenConnect on clients' PCs, this time connected to servers they control. They then download a set of tools called SCKit, which hides in the system, adds antivirus exclusions and sets a trap, RelayTrap, designed to infect the computer of the technician who connects to provide support.

The kit also searches the technician's browsers for console login session data, so it can use that session to push malicious code to other managed devices. ConnectWise points to a flaw in some platform extensions as a possible entry point, but the exact method is still under investigation.

Why it matters even if you do not use ScreenConnect

Many small and medium-sized companies do not choose their support tool directly: the IT provider installs it, often years ago, and nobody thinks about it again. If your provider uses ScreenConnect, your PCs could be among those within reach. If it uses another product, the principle still holds: whoever controls the support console controls every computer connected to it.

The most delicate point is the knock-on effect. A technician who supports ten clients can, if compromised, become the vehicle for reaching all of them. It is a supply chain risk, much like handing the keys to your warehouse to a cleaning company.

Think of a manufacturer with remote maintenance on its machines, a shop whose management software is supported remotely, a professional practice or a local authority that outsources all its IT. In every one of these cases remote access is continuous and often unattended, meaning it is active even when nobody is sitting at the screen.

How to improve remote support security now

You do not need to be technical to take the first steps. Many checks can be done with a list and a few targeted questions.

If your company also has equipment connected to the network for remote maintenance, include it in the inventory: in Industry 4.0 interconnection projects, remote access by machine manufacturers is one of the points to document most carefully.

  • Make an inventory of all remote access software installed on PCs and servers, and of who uses it.
  • Remove any that nobody can justify, going through your provider rather than acting on the systems yourself.
  • Check that your antivirus is active, up to date and has tamper protection enabled.
  • Look for antivirus exclusions that nobody has authorised.
  • Ask for access to the support console to require multi-factor authentication.

What to ask your IT provider

A good provider does not take offence at precise questions: it sees them as part of the relationship. Here are the ones to ask over the coming days, ideally by email so there is a record of the answer.

If the answers are vague, that is a signal not to ignore. A cyber risk assessment carried out by a third party can help you understand where you are exposed without calling your whole relationship with the provider into question.

  • Which remote support tool do you use on our devices, and which version?
  • Have you checked that you are not affected by the campaign reported by ConnectWise and Microsoft?
  • Are the clients used by your technicians up to date? ConnectWise indicates version 26.6.5 or later as the one that blocks the jump to the technician.
  • Do you use additional extensions on the console, and who configured them?
  • If something looks suspicious, how do you respond without using the same channel that might be compromised?

What are the limits of quick fixes?

The temptation is to uninstall the suspicious program and consider the matter closed. Microsoft is explicit: removing the unauthorised client does not remove scheduled tasks, autostart entries or web sessions that have already been stolen. Changing the password on its own does not close every open session either.

If a device turns out to be affected, the response must be methodical: isolate the PC, preserve the logs, invalidate sessions from a clean computer and, where you cannot be sure of its integrity, reinstall from scratch. This takes time and specific skills, at a cost that depends on the number of devices and the quality of the logs available.

Prevention, by contrast, costs relatively little: an inventory, updates, strong authentication and a few written rules on who can connect and when. At Teknet we see it often: companies with these basics in place react in hours, not weeks.

What to expect in the coming months

ConnectWise's investigation is still ongoing and further details on the origin of the attack may emerge. No figures have been released on the number of companies affected, nor any specific to Italy or Europe.

Similar cases are likely to recur with other remote management tools, because they give attackers ready-made access that is considered trustworthy. That is why it makes sense to treat remote support as a critical supplier: with clear contracts, regular checks and a shared response plan.

Frequently asked questions

What is SCKit and why is it dangerous?

SCKit is a set of malicious tools spread by abusing ScreenConnect, remote support software used by IT providers. It installs hidden access on PCs, makes itself persistent and tries to infect the technicians who connect as well, in order to reach other clients.

If my company does not use ScreenConnect, am I safe?

Not necessarily, because your IT provider may have installed the tool without you knowing. The same attack pattern can also apply to other remote access software, so it is worth making an inventory and asking your provider how it protects them.

Is uninstalling the suspicious program enough to fix the problem?

No. According to Microsoft, removing the unauthorised client does not remove scheduled tasks, antivirus changes or login sessions that have already been stolen. A full response is needed, carried out through a separate channel, and sometimes the device has to be reinstalled.

How exposed is your remote support?

If you would like to review your company's remote access and how it is protected, tell us about your situation: we will talk it through calmly and with no obligation.

Source: SCKit abuses ScreenConnect to deploy remote access and target technician sessions · Microsoft Security, 13 November 2026

Journal

Keep reading

All articles →