SCKit Exploits Patched ScreenConnect Flaw to Target MSPs

Introduction
A campaign aimed at ConnectWise ScreenConnect deployments is being powered by exploitation of an already-patched critical vulnerability rather than a fresh zero-day, according to research from Blackpoint Cyber's Adversary Pursuit Group (APG). The team shared its findings with The Hacker News and described a recovered attacker toolkit, tracked as SCKit, that weaponises CVE-2026-84869, a flaw carrying a CVSS score of 9.9.
That combination — a maximum-severity rating attached to a bug for which a fix already exists — is the detail that matters most for IT and security teams. It means the window of exposure is being held open not by an unknown defect in the software but by deployments that have not yet been brought up to date, or by configurations that keep the remote support surface reachable from the internet. For managed service providers, whose entire business model rests on remote access into customer environments, the consequences can extend well beyond a single host.
What SCKit does, and what remains unknown
According to the source material, APG recovered the attacker toolkit and attributed its operation to exploitation of CVE-2026-84869 in ScreenConnect. The group's reporting is explicit that this is not a new vulnerability, and that the underlying flaw has already been patched by the vendor.
Several details are not yet public and should not be assumed. The source does not specify:
- The exact affected product versions or the release in which the fix landed.
- The technical mechanics of the exploitation chain, or what post-exploitation actions SCKit performs once access is obtained.
- Which threat actor or group is behind the campaign, or whether the activity is financially or strategically motivated.
- The number of organisations affected, or the geographic distribution of victims.
- Published indicators of compromise, file hashes or command-and-control infrastructure.
Readers should treat any specific claim about those points — circulating on social media or in vendor marketing — with caution until it appears in primary reporting from the researchers or the vendor.
Why support sessions are the real attack path
ScreenConnect is legitimate remote support software. That legitimacy is precisely what makes it valuable to an intruder. A support session is, by design, an authenticated channel that grants interactive control of an endpoint, often with elevated privileges and often with the implicit trust of the person sitting in front of the machine. Security tooling tends to allow it, users are trained to expect it, and helpdesk workflows depend on it.
When an attacker can obtain or manufacture that kind of session, they inherit the trust rather than breaking it. Instead of dropping bespoke malware that might trip endpoint detection, they operate through a signed, sanctioned remote access tool — a living-off-the-land approach that blends into normal administrative noise.
The MSP dimension raises the stakes considerably. A single managed service provider typically holds persistent remote access into dozens or hundreds of downstream customer environments. Compromise of the provider's ScreenConnect instance is therefore not one incident but a potential multiplier, giving an adversary a foothold that maps neatly onto the provider's own customer list. This is the same structural risk that has made remote monitoring and management platforms such a persistent target for years, and it is why the phrase "MSP attack path" appears in the reporting rather than a simple description of isolated intrusions.
Patching is necessary but not sufficient
The most uncomfortable lesson in this story is that a patch existing and a patch being applied are two very different states. Remote access software frequently sits on the perimeter, exposed to the internet because that is how it does its job. Internet-facing services are continuously scanned, and exploitation of known vulnerabilities typically begins within hours or days of a fix being published, as attackers reverse-engineer the patch and target the population that has not yet deployed it.
For organisations running ScreenConnect — whether on-premises or through a provider — the practical question is not "is there a fix?" but "can I prove every instance I am responsible for is running it?" Shadow deployments, forgotten test servers and instances stood up by individual departments are the usual culprits when an organisation believes it is patched but is not.
What defenders should do now
Given the limited public detail, the priority actions are hygiene and visibility rather than indicator-chasing:
- Inventory every ScreenConnect deployment you own or consume, including trial, test and departmental instances. Confirm the running version against the vendor's advisory for CVE-2026-84869 and remediate anything behind the fixed release.
- Reduce exposure. Where the architecture allows, restrict management interfaces to known administrative networks or place them behind a VPN or identity-aware proxy rather than leaving them openly reachable.
- Enforce strong authentication on all administrative and support accounts, and review accounts that have been recently created, modified or granted elevated rights.
- Audit session logs and access records for support sessions that do not correspond to a legitimate ticket, unusual source addresses, off-hours activity or sessions initiated from unexpected infrastructure.
- Hunt for the toolkit. Ask your endpoint and EDR teams to look for artefacts consistent with SCKit once indicators are published; in the meantime, treat unexpected binaries or scripts appearing alongside ScreenConnect activity as suspicious.
- Segment and contain. Limit what a compromised support session can reach, so that a single foothold does not translate into domain-wide or tenant-wide access.
- MSPs should notify customers proactively if any instance was exposed during the vulnerable window, and review contractual incident-response obligations before an incident forces the conversation.
Grivyonx Expert Analysis
The headline reads like a malware story, but the underlying dynamic is an asset-management story. SCKit is notable less for novelty than for what it reveals about the economics of remote support: the same tooling that lets a provider fix a customer's laptop in minutes gives an adversary a trusted, signed and frequently allow-listed channel into the same estate. Defenders who respond only by patching will close this specific gap and remain exposed to the next one, because the structural weakness is the assumption that anything used for administration is inherently trustworthy. The organisations that fare best are those that treat remote access platforms as tier-zero infrastructure — inventoried, authenticated, logged, segmented and reviewed — rather than as a helpdesk convenience. It is also worth noting how quickly a patched vulnerability becomes an active campaign; the gap between disclosure and exploitation is now short enough that patch velocity is itself a security control, and one that should be measured and reported at board level rather than assumed.
Conclusion
The SCKit campaign is a reminder that critical severity and active exploitation are not the same thing as an unsolvable problem. CVE-2026-84869 has a fix, and organisations that can demonstrate complete coverage of their ScreenConnect estate have largely removed themselves from this particular attack path. The harder, longer-term work is architectural: shrinking the number of internet-reachable administrative services, proving that every instance is accounted for, and assuming that any remote access tool will eventually be targeted. Teams looking to reduce that manual burden across multi-tenant environments can lean on Grivyonx's AI automation, DevSecOps and cloud security services to keep asset inventories, patch state and access reviews continuously verified rather than reconstructed after an incident.
- #SCKit malware
- #ConnectWise ScreenConnect
- #CVE-2026-84869
- #MSP security
- #Blackpoint Cyber
- #remote access software
- #patch management



