Skip to content
NewA calmer, faster ZeroHour
Exploit / PoCcriticalExploited in the wild

ScreenConnect flaw used to install rogue clients on technician PCs

Original title: Hackers Abuse ScreenConnect Vulnerability to Install Rogue Remote Access Clients on Technician Systems

GBHackersby Mayura Kathir ()3 min read
Part of a story covered by 14 sourcesConnectWise says ScreenConnect attacks continue on unpatched systemsMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Huntress saw at least 688,000 guest run-file requests across 42 MSP servers from October 20 to November 16.

Huntress says attackers exploited CVE-2026-84869 in ConnectWise ScreenConnect to run files on technicians’ workstations and install attacker-controlled ScreenConnect clients. A November 12 compromise ran a guest-pushed batch file, notified Telegram, and opened a rogue session in about nine seconds. Clients before 26.6.5 lack authorization checks, so joining a malicious session can execute a file without a confirmation prompt. Servers themselves are not affected.

Unconfirmed: Huntress assessed with high confidence that the spray operator controlled masterdarky[.]com; that link is not independently confirmed.

Key facts
  • ConnectWise disclosed the flaw on September 8, 2026, with a CVSS score of 9.9.
  • The confirmed payload came from masterdarky[.]com and connected to relay port 8041.
  • The same batch name appeared on five MSP servers, with spraying starting about 43 minutes earlier.
  • Requests came from 29 IP addresses and repeatedly offered update.bat-style files.
  • Startup-folder traversal was also seen, but successful persistence was not established.
Security assessment · AI, from the articleExploited in the wild

Impact: Unauthorized file execution and a rogue remote-access client on technician PCs

ProductAffectedFixed in
ConnectWise ScreenConnectclients before 26.6.526.6.5
What to do
  1. 1.Update every technician host client and affected Access agent to 26.6.5 or later.
  2. 2.If patching is impossible, remove TransferFiles permissions from applicable roles and session groups.
  3. 3.Isolate confirmed hosts, remove rogue clients, revoke sessions, and rotate accessible credentials.
Analyze CVE-2026-84869 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-84869
Missing authorization in ScreenConnect client allows unauthorized file execution
9.91%KEV
KEV

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
domainmasterdarky.comative privileges. It then downloaded WindowsUpdate.msi from masterdarky[.]com. An administrative MSI extraction placed the payload bene
sha256f8871b1561d5c77c297378a7f49c84de52a01ff297395544f0e95d13ef972841e-2 installer containing the rebranded ScreenConnect client f8871b1561d5c77c297378a7f49c84de52a01ff297395544f0e95d13ef972841 WindowsUpdate.WindowsClient.exe , rogue ScreenConnect clien
urlhttps://masterdarky.com/WindowsUpdate.msim Attacker ScreenConnect relay (port 8041) and payload host hxxps://masterdarky[.]com/WindowsUpdate.msi Stage-2 installer containing the rebranded ScreenConnect

From the original article

3 min read at gbhackers.com

Hackers are exploiting CVE-2026-84869 in ConnectWise ScreenConnect to execute malicious files on technicians’ workstations and deploy attacker-controlled remote access clients. Huntress confirmed a November 12 compromise in which a guest-pushed batch file notified a Telegram bot, downloaded an installer, and established a rogue ScreenConnect connection within approximately nine seconds.

GBHackers

By Mayura Kathir · gbhackers.com

Read the full article at GBHackers

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.