T1563

Remote Service Session Hijacking

Linux · macOS · Windowsnothing on this site yetT1563 on attack.mitre.org

Adversaries may take control of preexisting sessions with remote services to move laterally in an environment. Users may use valid credentials to log into a service specifically designed to accept remote connections, such as telnet, SSH, and RDP. When a user logs into a service, a session will be established that will allow them to maintain a continuous interaction with that service.

MITRE ATT&CK 19.2, retrieved 2026-09-12

If this is happening now

1

Checklists and playbooks to open while the alert is still live.

Playbook for this stage

Cloud account compromise

Impossible travel, an unrecognised inbox rule, or a reported invoice-fraud attempt.

how MITRE says to see it

Detection of Remote Service Session Hijacking

  • Detection of anomalous RDP or remote service session activity where a logon session is hijacked rather than newly created. Indicators include mismatched user credentials vs. active session tokens, service session takeovers without corresponding successful logon events, or RDP shadowing activity without user consent.
  • Detection of SSH/Telnet session hijacking via discrepancies between authentication logs and active session tables. Adversary behavior includes reusing or stealing active PTY sessions, attaching to screen/tmux, or issuing commands without corresponding login events.
  • Detection of hijacked VNC or SSH sessions on macOS where adversaries take over an existing session rather than authenticating directly. Indicators include process execution from active sessions without new logon events, manipulation of TTY sessions, or anomalous network activity tied to dormant sessions.

what reduces it

  • M1030 Network Segmentation. Enable firewall rules to block unnecessary traffic between network security zones within a network.
  • M1027 Password Policies. Set and enforce secure password policies for accounts.
  • M1018 User Account Management. Limit remote user permissions if remote access is necessary.
  • M1026 Privileged Account Management. Do not allow remote access to services as a privileged account unless necessary.
  • M1042 Disable or Remove Feature or Program. Disable the remote service (ex: SSH, RDP, etc.) if it is unnecessary.

sub-techniques

The description, detection analytics and mitigations are reproduced from MITRE ATT&CK, version 19.2, under its terms of use. The checklists, hunts, labs and everything else linked here are this site’s.