Has installed NetBird on victim devices to create a mesh network that facilitated control of several victim devices at once.1
Remote Desktop Software T1219.002
- Tactic
- Command and Control
- Platforms
- Linux, macOS, Windows
- Version
- 1.0
- Created
- 24 March 2025
- Last modified
- 12 May 2026
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, 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.[1][2][3]
Remote access modules/features may also exist as part of otherwise existing software such as Zoom or Google Chrome’s Remote Desktop.[4][5]
Remote Desktop Software MITRE reference T1219.002
11 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has used legitimate remote monitoring and management (RMM) tools including AnyDesk, NinjaOne, and Level.io.1
Has downloaded remote management and monitoring software such as “AnyDesk” for post compromise activities.12345
Has abused multiple types of legitimate remote access software and tools, such as ScreenConnect, NetSupport Manager, and AnyDesk.12
In addition to directing victims to run remote software, Scattered Spider members themselves also deploy RMM software including TeamViewer, AnyDesk, LogMeIn, ngrok, and ConnectWise to establish persistence on the compromised network.12345
Has installed TeamViewer on targeted systems.1
All 11 groups for this technique · 6 newest in this preview
3 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During C0027, Scattered Spider directed victims to run remote monitoring and management (RMM) tools.1
During C0018, the threat actors used AnyDesk to transfer tools between systems.12
During C0015, the threat actors installed the AnyDesk remote desktop application onto the compromised network.1
All 3 campaigns for this technique
1 software entry is documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Can use the Splashtop remote management service (SRManager.exe) to execute the Linux ransomware binary directly on Windows systems.1
All 1 software entries for this technique
Offense vs defense T1219.002
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Remote Desktop Software detection strategy DET0259
MITRE names one behaviour worth catching for this technique and breaks it into 3 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Remote Desktop Software Execution and Beaconing Detection
AN0714 · Windows
Adversary installation or use of RMM software (e.g., TeamViewer, AnyDesk, ScreenConnect) followed by outbound beaconing or remote session establishment
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| File CreationDC0039 | WinEventLog:Sysmon | EventCode=11 |
| Firewall Rule ModificationDC0051 | WinEventLog:Microsoft-Windows-Windows Firewall With Advanced Security/Firewall | new rule allowing inbound or outbound connections for remote desktop software |
| Network Connection CreationDC0082 | WinEventLog:Sysmon | EventCode=3, 22 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| Image | RMM software can vary; defenders should update rules to account for additional binaries (e.g., ConnectWise, Zoho Assist) |
| DestinationPort | RMM software may use configurable or random high ports outside of standard (e.g., 7070, 5650) |
| ParentImage | Expected parent process may vary in different enterprise contexts |
| TimeWindow | Correlation window for install-to-beacon or process-to-network event should match operational environment |
AN0715 · Linux
Execution of known or custom VNC/remote desktop daemons or tunneling agents that initiate external communication after launch
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | auditd:SYSCALL | execve |
| Network Connection CreationDC0082 | NSM:Flow | outbound connections to RMM services or to unusual destination ports |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| binary_name | Custom-compiled or renamed VNC servers (e.g., x11vnc, tightvncserver) may require local tuning |
| OutboundIPRange | Destination IP or ASN may shift depending on geolocation of cloud-hosted RMM backends |
AN0716 · macOS
Initiation of remote desktop sessions via AnyDesk, TeamViewer, or Chrome Remote Desktop accompanied by unexpected user logins or system modifications
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | macos:unifiedlog | launch of remote desktop app or helper binary |
| Network Connection CreationDC0082 | macos:unifiedlog | network sessions initiated by remote desktop apps |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| process_signature | App may be notarized and signed differently depending on distribution method (App Store vs .pkg) |
| sandbox_exception | If the remote desktop tool circumvents sandbox, it may produce additional telemetry in local TCC logs |
Consider disabling unnecessary remote connection functionality, including both unapproved software installations and specific features built into supported applications.
Use application control to mitigate installation and use of unapproved software that can be used for remote access.
Properly configure firewalls, application firewalls, and proxies to limit outgoing traffic to sites and services used by remote access software.