CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

ScreenConnect crypto-exchange bait sessions (November 2026)

campaign · campaign:screenconnect-crypto-bait-sessions-2026-11 single-source

Unattributed enrolment of thousands of fake guest sessions named after crypto exchanges into self-hosted ScreenConnect consoles from 2026-11-03, which Huntress hypothesises is bait for technicians running clients older than 26.6.5 and has seen used for nothing so far; Huntress found no overlap with the SCKit indicators (Huntress, 2026-11-14).

Coverage
1
first 2026-11-15 → last 2026-11-15
Latest activity
2026-11-15
Huntress: 2,223 crypto-named fake sessions sit on 118 ScreenConnect servers, likely bait for unpatched…
Peak priority
notable
1 notable
Targets
technology
sectors: technology
Sources cited
1
1 hosts

Action items (1)

Do-now tasks recorded on the entries about ScreenConnect crypto-exchange bait sessions (November 2026), newest first. Check the date before acting on an older one.

  • On every self-hosted ScreenConnect server your organisation or its IT providers run, list guest sessions with an exchange-and-role name or empty company or site fields, copy App_Data\\Session.db and its WAL file before deleting any, and where a technician connected to one from a client older than 26.6.5, inspect that workstation's ScreenConnect Temp and Startup folders and process history and treat text sent through the session as exposed credentials, because Huntress suspects the sessions are bait for the file-transfer flaw CVE-2026-84869.
    2026-11-15Huntress: 2,223 crypto-named fake sessions sit on…

Defender insights

What each entry about ScreenConnect crypto-exchange bait sessions (November 2026) tells a defender to do, newest first.

2026-11-15NOTABLEHuntress: 2,223 crypto-named fake sessions sit on 118 ScreenConnect servers, likely bait for unpatched technicians

Exposure · triage · detection

Relationships explore in graph

Typed, source-stated connections from the entity registry; each edge cites the entry whose reporting establishes it.

affects

Story timeline

  1. 2026-11-15ScreenConnect: Huntress finds 2,223 fake guest sessions named after crypto exchanges on 118 self-hosted servers, enrolled from 2026-11-03 and, in its leading hypothesis, bait for technicians whose clients predate 26.6.5; it saw no malicious use and no overlap with SCKit
    active-threatsHuntress: 2,223 crypto-named fake sessions sit on 118 ScreenConnect servers, likely bait for unpatched technicians

Hunting pivots

Affected products
ATT&CK techniques (2 across 2 tactics)

2 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • StealthMasquerading: Match Legitimate Resource Name or Location
  • Command and ControlRemote Access Tools: Remote Desktop Software

Stealth TA0005

T1036.005Masquerading: Match Legitimate Resource Name or Location×1

Adversaries may match or approximate the name or location of legitimate files, Registry keys, or other resources when naming/placing them. This is done for the sake of evading defenses and observation.

Evidence: 2026-11-15/screenconnect-crypto-bait-guest-sessions-118-servers · ATT&CK page ↗

Command and Control TA0011

T1219.002Remote Access Tools: Remote Desktop Software×1

An adversary may use legitimate desktop support software to establish an interactive command and control channel to target systems within networks. Desktop support software provides a graphical interface for remotely controlling another computer, transmitting the display output, keyboard input, and mouse control between devices using various protocols. Desktop support software tools, such as `VNC`, `Team Viewer`, `AnyDesk`, `ScreenConnect`, `LogMein`, `AmmyyAdmin`, and other remote monitoring and management (RMM) tools, are commonly used as legitimate technical support software and may be allowed by application control within a target environment.

Evidence: 2026-11-15/screenconnect-crypto-bait-guest-sessions-118-servers · ATT&CK page ↗

Entries about ScreenConnect crypto-exchange bait sessions (November 2026) (1)

2026-11-15 · view entry permalink →

NOTABLENATOB2

ScreenConnect: Huntress finds 2,223 fake guest sessions named after crypto exchanges on 118 self-hosted servers, enrolled from 2026-11-03 and, in its leading hypothesis, bait for technicians whose clients predate 26.6.5; it saw no malicious use and no overlap with SCKit

Huntress counted 2,223 fake guest sessions on 118 self-hosted ScreenConnect servers across 109 MSP and organisation accounts, enrolled between 2026-11-03 and 2026-11-13: always-online "computers" named after crypto exchanges (an exchange word joined to a role word) with a trading-desktop thumbnail (Huntress, 2026-11-14). An MSP asked about them on 2026-11-12; its own server showed no web shells, suspicious child processes or new accounts, and the first Access installer Huntress examined was publicly downloadable, which ScreenConnect allows without authentication by design, and a guest client needs the server's relay address, which is embedded in that server's guest installer, to register. Huntress saw no malicious activity from the sessions: technicians who opened them mostly stayed under 30 seconds, and in one case a technician used the send-text feature, which ScreenConnect does not log, so Huntress treated it as a possible credential exposure. On 29 servers with complete history the operator revisited every 151 seconds to keep the sessions online (Huntress, 2026-11-14).

Huntress's leading hypothesis, which it has not observed, is bait: a technician who connects with a client older than 26.6.5 would let a malicious guest use the file-transfer flaw CVE-2026-84869 to run a file on the technician's workstation, often the MSP's most privileged machine; it cannot rule out capturing what a technician types, and it found no overlap with the published SCKit indicators (Huntress, 2026-11-14). It considers the public suggestion that the sessions are a malware sandbox detonating installers unlikely.

Triage: a malware-analysis sandbox detonating a ScreenConnect installer also creates guest sessions; per Huntress, a sandbox session sends a key and JPEG screenshots of the analysis VM, while these send no key, reuse seven screenshot families and randomise hardware and OS details (Huntress, 2026-11-14).

As of this writing, we've found 2,223 fake sessions on 118 servers across 109 MSP and organization accounts.

This is our leading hypothesis, but it's important to note that we have not observed the guest sessions being used this way.

Huntress 2026-11-14

Builds on: ConnectWise patches a ScreenConnect flaw Huntress had already watched turn every infected… · ScreenConnect SCKit: second wave hits on-prem; disable RMM+, update technician clients to…

threat15 Nov 04:27Zsingle-sourceOpen finding →
Sources: Huntress

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Threats1

Source distribution

  • huntress.com1 (100%)