DKDKCISSP
PolicyINCIDENTDEVELOPING

Attackers use Crypto Exchange Names to Disguise Unauthorized Sessions on 100+ ScreenConnect Servers

use Crypto Exchange Names has a flaw rated critical -- the kind of severity that moves a fix from the to-do list to today's priority.

DKCISSP News DeskHuntress14 Nov 2026, 7:20 am2 min read
Attackers use Crypto Exchange Names to Disguise Unauthorized Sessions on 100+ ScreenConnect Servers
Image courtesy of Huntress. Original report

use Crypto Exchange Names has a flaw rated critical -- the kind of severity that moves a fix from the to-do list to today's priority.

This requires local or already-authenticated access to reach.

After being tipped off by one of our MSP partners, Huntress investigated a cluster of unauthorized guest sessions appearing on ScreenConnect panels from machines with crypto exchange-themed names.

In total, we found 2,408 unauthorized sessions enrolled since November 3, 2026.

A separate campaign is actively exploiting a critical ScreenConnect flaw (CVE-2026-84869), which lets a malicious guest make a vulnerable technician client run a file.

We found no evidence of web shells, suspicious child processes, or new accounts.

Anyone running use Crypto Exchange Names 25.3.4.9288 is exposed, specifically wherever use Crypto Exchange Names is actually deployed rather than just licensed or installed somewhere unused.

As of November 13, we've seen related activity across at least 118 self-hosted ScreenConnect servers belonging to 109 Huntress-protected organizations.

However, we assess that these sessions could still be risky to organizations, or used as bait to launch an attack.

This is tracked as CVE-2026-84869 and rated critical severity, which is the identifier to use when checking vendor guidance.

The affected versions are 25.3.4.9288, so that's the range to check against your own deployment.

Notably, we haven't seen evidence of any sort of malicious activity linked to these sessions: they haven't pushed files, run commands, or sent anything to technicians who joined them, and joining them hasn't triggered anything so far.

MSPs should update every technician's ScreenConnect client to 26.6.5 or later, check for and delete the fake sessions if they exist, and check whether anyone joined one.

Huntress has investigated various incidents involving ScreenConnect in the last few months: including rogue ScreenConnect installations seen in September and, most recently, activity linked to the SCKit worm on November 11.

On the first server we investigated, we found the MSP's Access installer was publicly downloadable.

Why it matters

What an attacker actually gains: the advisory describes a real security impact once the vulnerable path is reached.

We collected the ScreenConnect session database (App_Data\Session.db) from the Huntress-protected ScreenConnect servers we could reach and looked for the same pattern.

Across our telemetry, we could see the first session was enrolled November 3, and the latest one was enrolled November 13.

What security teams should do

  • Confirm whether use Crypto Exchange Names 25.3.4.9288 is present anywhere in your asset and software inventory.
MORE IN POLICY

More cybersecurity reporting

GTA 6 hacker pleads guilty after release from secure hospitalBBC News · 16 Nov 2026, 7:04 pmRetadup Worm Resurfaces 7 Years After Takedown to Spread CoffeeLoader MalwareThe Hacker News · 16 Nov 2026, 6:03 pmMicrosoft outage put Suffolk GP patients in a serious situationBBC News · 14 Nov 2026, 12:11 pmCritical Red Hat Quay Flaw Lets Attackers Read and Overwrite All Private Container Images in a RegistryThe Hacker News · 12 Nov 2026, 9:57 pm