Adversaries may use Valid Accounts to log into remote machines using Secure Shell (SSH). The adversary may then perform actions as the logged-on user.
SSH is a protocol that allows authorized users to open remote shells on other computers. Many Linux and macOS versions come with SSH installed by default, although typically disabled until the user enables it. On ESXi, SSH can be enabled either directly on the host (e.g., via vim-cmd hostsvc/enable_ssh) or via vCenter.[1][2][3] The SSH server can be configured to use standard password authentication or public-private keypairs in lieu of or in addition to a password. In this authentication scenario, the user’s public key must be in a special file on the computer running the server that lists which keypairs are allowed to login as that user (i.e., SSH Authorized Keys).
| ID | Name | Description |
|---|---|---|
| G0087 | APT39 |
APT39 used secure shell (SSH) to move laterally among their targets.[4] |
| G1023 | APT5 |
APT5 has used SSH for lateral movement in compromised environments including for enabling access to ESXi host servers.[5] |
| G0143 | Aquatic Panda |
Aquatic Panda used SSH with captured user credentials to move laterally in victim environments.[6] |
| G0098 | BlackTech | |
| C0032 | C0032 |
During the C0032 campaign, TEMP.Veles relied on encrypted SSH-based tunnels to transfer tools and for remote command/program execution.[8] |
| S0154 | Cobalt Strike |
Cobalt Strike can SSH to a remote service.[9][10] |
| C0029 | Cutting Edge |
During Cutting Edge, threat actors used SSH for lateral movement.[11] |
| S0363 | Empire |
Empire contains modules for executing commands over SSH as well as in-memory VNC agent injection.[12] |
| G1016 | FIN13 |
FIN13 has remotely accessed compromised environments via secure shell (SSH) for lateral movement.[13] |
| G0046 | FIN7 |
FIN7 has used SSH to move laterally through victim environments.[14] |
| G0117 | Fox Kitten |
Fox Kitten has used the PuTTY and Plink tools for lateral movement.[15] |
| G0036 | GCMAN | |
| G0119 | Indrik Spider |
Indrik Spider has used SSH for lateral movement.[17] |
| S0599 | Kinsing | |
| G0032 | Lazarus Group |
Lazarus Group used SSH and the PuTTy PSCP utility to gain access to a restricted segment of a compromised network.[19] |
| G0065 | Leviathan | |
| C0049 | Leviathan Australian Intrusions |
Leviathan used SSH brute force techniques to move laterally within victim environments during Leviathan Australian Intrusions.[21] |
| G0045 | menuPass |
menuPass has used Putty Secure Copy Client (PSCP) to transfer data.[22] |
| G0049 | OilRig | |
| S1187 | reGeorg |
reGeorg can communicate using SSH through an HTTP tunnel.[24] |
| G0106 | Rocke | |
| G1045 | Salt Typhoon |
Salt Typhoon has modified the loopback address on compromised switches and used them as the source of SSH connections to additional devices within the target environment, allowing them to bypass access control lists (ACLs).[26] |
| G1015 | Scattered Spider |
Scattered Spider has used SSH to move laterally in victim environments and to access the vSphere vCenter Server GUI.[27][28] |
| G1046 | Storm-1811 |
Storm-1811 has used OpenSSH to establish an SSH tunnel to victims for persistent access.[29] |
| G0139 | TeamTNT |
TeamTNT has used SSH to connect back to victim machines.[30] TeamTNT has also used SSH to transfer tools and payloads onto victim hosts and execute them.[31] |
| G1048 | UNC3886 |
UNC3886 has established remote SSH access to targeted ESXi hosts.[32][33] |
| ID | Mitigation | Description |
|---|---|---|
| M1042 | Disable or Remove Feature or Program |
Disable the SSH daemon on systems that do not require it, especially ESXi servers. For macOS, ensure Remote Login is disabled under Sharing Preferences.[34] |
| M1032 | Multi-factor Authentication |
Require multi-factor authentication for SSH connections wherever possible, such as password protected SSH keys. |
| M1018 | User Account Management |
Limit which user accounts are allowed to login via SSH. |
| ID | Name | Analytic ID | Analytic Description |
|---|---|---|---|
| DET0596 | Behavioral Detection of Remote SSH Logins Followed by Post-Login Execution | AN1638 |
SSH login from a remote system (via sshd), followed by user context execution of suspicious binaries or privilege escalation behavior. |
| AN1639 |
SSH login detected via Unified Logs, followed by unusual process execution, especially outside normal user behavior patterns. |
||
| AN1640 |
SSH login via hostd or |