← Voltar ao feed

Fake Binance and KuCoin guest sessions planted on 118 ScreenConnect servers, apparent bait for technicians (CVE-2026-84869)

1 fonte(s) · 1 atualização(ões) · publicado 16/11/2026 10:34 · coletado há 1 dia

Huntress researchers report that an unknown operator has planted more than 2,000 fake guest sessions on self-hosted ScreenConnect servers. The sessions are named after cryptocurrency exchanges, for example "LAPTOP-BINANCE" and "KUCOIN-SRV". Since 3 November the campaign has hit at least 118 servers at 109 organisations protected by Huntress, mostly MSPs. Huntress' leading hypothesis is that the sessions are bait for technicians, who could be exposed to CVE-2026-84869 if they join one with an unpatched client. Huntress has not seen the flaw exploited in this campaign, and it reports no confirmed compromise, files pushed, commands run or data sent. This summary is based only on the article. No vendor advisory or CVSS data was reviewed.

Entenda a falha

A vulnerabilidade

CVE-2026-84869 is a critical flaw in ConnectWise ScreenConnect that lets a malicious guest session make the technician's client run a file. The attacker needs a technician to join the guest session using an unpatched client. The articles name no other prerequisites. Technician clients and Access agents before 26.6.5 are affected, and 26.6.5 or later is the fix. Huntress has not seen the flaw exploited in the campaign described, in which more than 2,000 fake crypto-themed guest sessions appeared on at least 118 self-hosted servers. The summary is based only on the Huntress-sourced article, with no vendor advisory or CVSS data reviewed.

Como funciona

The operator downloaded publicly available guest installers, which revealed the relay address of each server. A scripted emulator impersonating a genuine Windows ScreenConnect client then registered fake guest sessions with names like LAPTOP-BINANCE and KUCOIN-SRV, and reconnected about every 151 seconds so they always looked online. A technician who sees a seemingly valuable customer may join the session. If the technician's client is unpatched, Huntress says a malicious guest could make it run a file. The articles do not describe the internal steps of the flaw itself.

Por que é vulnerável

The articles do not explain the root cause of CVE-2026-84869 or what the fix changes in code. They only say the client lets a malicious guest run a file on the technician's machine and that 26.6.5 addresses it. The campaign itself was possible because guest installers were publicly downloadable and exposed the relay address.

Como foi descoberta

Huntress researchers uncovered the fake-session campaign, which began on 3 November, across servers of organisations they protect, mostly MSPs. An MSP first reported the activity, and its server was clean. The articles do not say who found CVE-2026-84869 or how it was disclosed. Huntress rejected a public theory that the sessions were a by-product of Joe Sandbox malware analysis, saying the behaviour matched an emulator.

Explicação gerada por IA a partir da matéria e dos artigos, em 16/11/2026 12:16.

Detalhes técnicos

  • A scripted emulator impersonates a genuine Windows ScreenConnect client. It registered sessions because guest installers were publicly downloadable and revealed the relay address.
  • It revisits each server about every 151 seconds, so the sessions always appear online. The researchers counted more than 1,000 distinct fake machine names.
  • About 97.8% of the crypto-named connections came from a single IP address hosted by IONOS.
  • Huntress rejected the theory that the sessions were a by-product of Joe Sandbox malware analysis.
  • Some technicians opened the fake sessions, mostly for under 30 seconds. One technician typed text into a session twice, which Huntress treats as possible credential exposure.
  • CVE-2026-84869 is a critical flaw that lets a malicious guest run a file on the technician's client.
  • Detection markers: an empty guest public key, guest version 25.3.4.9288, and many guests connecting from one external IP.

Remediação

  • Upgrade all technician ScreenConnect clients and affected Access agents to 26.6.5 or later.
  • Back up App_Data\Session.db and its WAL file, then delete the fake sessions.
  • Check whether any technician joined a fake session. If one did so with an unpatched client, inspect that workstation.
  • Technicians should not join sessions they cannot tie to a known customer.
  • Restrict installer and web access, keep Access installer links private, and rebuild leaked installers.
  • Block the known bad IPs, although the operator may move.

Linha do tempo

  1. itsecurityguru.org ↗ · pub. 16/11/2026 10:34 · coletado 16/11 12:00 primeiro registro

    Fake Binance and KuCoin guest sessions planted on 118 ScreenConnect servers, apparent bait for technicians (CVE-2026-84869)

    ler a análise desta fonte

    Huntress researchers report that an unknown operator has planted more than 2,000 fake guest sessions on self-hosted ScreenConnect servers. The sessions are named after cryptocurrency exchanges, for example "LAPTOP-BINANCE" and "KUCOIN-SRV". Since 3 November the campaign has hit at least 118 servers at 109 organisations protected by Huntress, mostly MSPs. Huntress' leading hypothesis is that the sessions are bait for technicians, who could be exposed to CVE-2026-84869 if they join one with an unpatched client. Huntress has not seen the flaw exploited in this campaign, and it reports no confirmed compromise, files pushed, commands run or data sent. This summary is based only on the article. No vendor advisory or CVSS data was reviewed.

    Technical Details

    • A scripted emulator impersonates a genuine Windows ScreenConnect client. It registered sessions because guest installers were publicly downloadable and revealed the relay address.
    • It revisits each server about every 151 seconds, so the sessions always appear online. The researchers counted more than 1,000 distinct fake machine names.
    • About 97.8% of the crypto-named connections came from a single IP address hosted by IONOS.
    • Huntress rejected the theory that the sessions were a by-product of Joe Sandbox malware analysis.
    • Some technicians opened the fake sessions, mostly for under 30 seconds. One technician typed text into a session twice, which Huntress treats as possible credential exposure.
    • CVE-2026-84869 is a critical flaw that lets a malicious guest run a file on the technician's client.
    • Detection markers: an empty guest public key, guest version 25.3.4.9288, and many guests connecting from one external IP.

    Remediation

    • Upgrade all technician ScreenConnect clients and affected Access agents to 26.6.5 or later.
    • Back up App_Data\Session.db and its WAL file, then delete the fake sessions.
    • Check whether any technician joined a fake session. If one did so with an unpatched client, inspect that workstation.
    • Technicians should not join sessions they cannot tie to a known customer.
    • Restrict installer and web access, keep Access installer links private, and rebuild leaked installers.
    • Block the known bad IPs, although the operator may move.