Has used MeshCentral and ConnectWise to gain initial access, to run administrative command queries and to deploy the custom lateral movement and defacement script [victim_abbreviation]_fanout.sh.12
Remote Access Tools T1219
- Tactic
- Command and Control
- Platforms
- Linux, macOS, Windows
- Version
- 3.0
- Created
- 18 April 2018
- Last modified
- 12 May 2026
- Contributors
- Matt Kelly, @breakersall; Zachary Stanford, @svch0st; Dray Agha, @Purp1eW0lf, Huntress Labs
An adversary may use legitimate remote access tools to establish an interactive command and control channel within a network. Remote access tools create a session between two trusted hosts through a graphical interface, a command line interaction, a protocol tunnel via development or management software, or hardware-level access such as KVM (Keyboard, Video, Mouse) over IP solutions. Desktop support software (usually graphical interface) and remote management software (typically command line interface) allow a user to control a computer remotely as if they are a local user inheriting the user or software permissions. This software is commonly used for troubleshooting, software installation, and system management.[1][2][3] Adversaries may similarly abuse response features included in EDR and other defensive tools that enable remote access.
Remote Access Tools MITRE reference T1219
13 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 leveraged Remote Access Software for lateral movement and data exfiltration.1234 Medusa Group has also been known to utilize Remote Access Software such as AnyDesk, Atera, ConnectWise, eHorus, N-Able, PDQ Deploy, PDQ Inventory, SimpleHelp and Splashtop.2
Uses legitimate utilities such as AnyDesk and PuTTy for maintaining remote access to victim environments.12
All 13 groups for this technique · 6 newest in this preview
2 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During Night Dragon, threat actors used several remote administration tools as persistent infiltration channels.1
During Operation AkaiRyū, MirrorFace used remote access tools including PuTTY.1
All 2 campaigns for this technique
7 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Has utilized remote access software including AnyDesk client through the “adc” module.123 InvisibleFerret has also downloaded the AnyDesk client should it not already exist on the compromised host by searching for C:/Program Files(x86)/AnyDesk/AnyDesk.exe.4
Has established tmate sessions for C2 communications.1
Has checked for the LogMein event log in an attempt to encrypt files in remote machines.1
Contains a module for VNC.1
Has the capability to download a VNC module from command and control (C2).1
All 7 software entries for this technique · 6 newest in this preview
Offense vs defense T1219
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 Access Tools detection strategy DET0496
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.
Behavior-Chain Detection for Remote Access Tools (Tool-Agnostic)
AN1366 · Windows
Chain of remote access tool behavior: (1) initial execution of remote-control/assist agent or GUI under user context; (2) persistence via service or autorun; (3) long-lived outbound connection/tunnel to external infrastructure; (4) interactive control signals such as shell or file-manager child processes spawned by the RAT parent.
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 | WinEventLog:Sysmon | EventCode=1 |
| File CreationDC0039 | WinEventLog:Sysmon | EventCode=11 |
| Windows Registry Key CreationDC0056 | WinEventLog:Sysmon | EventCode=12 |
| Service CreationDC0060 | WinEventLog:System | EventCode=7045 |
| Windows Registry Key ModificationDC0063 | WinEventLog:Sysmon | EventCode=13, 14 |
| 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 |
|---|---|
| TimeWindow | Correlation period binding start→persistence→egress→child (default 15m, adjust per environment). |
| UserContext | Differentiate help-desk/jump hosts and admin accounts from standard endpoints. |
| ProcessAllowlist | Known-good remote support tools; suppress expected events while still correlating anomalous sequences. |
| InstallPathRegex | Alert when services/agents execute from user-writable or temp paths. |
| ExternalIPAllowlist | Vendors’ support clouds/CDNs to reduce false positives on egress detection. |
| ShellSpawnRegex | Define which child shells from GUI parents are acceptable versus suspicious. |
| EgressHeuristics | Thresholds for session duration, connection counts, and bytes_out/bytes_in ratio. |
AN1367 · Linux
Sequence of RAT agent execution, systemd persistence, and long-lived external egress; optional interactive shells spawned from the agent.
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: Agent/headless flags (listen/connect/reverse/tunnel) or remote-control binaries spawning shells |
| File CreationDC0039 | auditd:PATH | WRITE: Drop of binaries/scripts in ~/.local, /tmp, or /opt tool dirs |
| 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 |
|---|---|
| TimeWindow | Bind exec→service→egress events; extend for staged deployments. |
| DaemonAllowlist | Approved .service names/paths to avoid flagging corporate agents. |
| SuspiciousChildProcesses | Define shells/interpreters considered anomalous when spawned by GUI/agent parents. |
| EgressHeuristics | Flow heuristics for long-lived, client-heavy connections post-install. |
AN1368 · macOS
Electron/GUI or headless RAT execution followed by LaunchAgent/Daemon persistence and persistent external connections; interactive children (osascript/sh/curl) spawned by parent.
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 | Process exec of remote-control apps or binaries with headless/connect flags |
| File CreationDC0039 | macos:osquery | CREATE/MODIFY: Creation of LaunchAgents/Daemons plists in user/system locations |
| Network Connection CreationDC0082 | macos:osquery | CONNECT: Long-lived connections from remote-control parents to external IPs/domains |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AllowedAppBundlePaths | Legitimate remote-support apps under /Applications. |
| LaunchdAllowlist | Known-good LaunchAgents/Daemons identifiers. |
| TimeWindow | Window for correlating exec→launchd→egress events. |
| EgressHeuristics | Duration/volume thresholds for persistent sessions. |
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.
Block the use of IP-based KVM devices within the network if they are not required.
Network intrusion detection and prevention systems that use network signatures may be able to prevent traffic to remote access services.
Tests from Atomic Red Team (MIT licence) · technique definition