WindowsT1202

>ssh.exe

Ssh.exe is the OpenSSH compatible client can be used to connect to Windows 10 (build 1809 and later) and Windows Server 2019 devices.

Default Executable Paths

c:\windows\system32\OpenSSH\ssh.exe

Integrity & Metadata

Category Count: 3 weaponized patterns
Forensics & Triage Insight

Documented in LOLBAS project by Akshat Pradhan.

Detection Engineering Notes

Monitor process creation events where FileName is "ssh.exe" or command line references known attack arguments.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

ssh.exe is a native utility pre-installed on Windows systems. Threat actors and red teams abuse ssh.exe as a Living-off-the-Land Binary (LOLBin) to achieve Execute without triggering traditional antivirus file-hash alerts. Legitimate system administrators use it for routine administration, making behavioral command-line telemetry essential for differentiation.

Primary Abused Tactics
Execute
Minimum Privilege
User
Key Telemetry Source
Sysmon 1 / 4688
ATT&CK Mapping
T1202

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

3 documented methods
Filter Purpose:
ExecutePrivileges: User
T1202: Technique T1202

Executes specified command on host machine. The prompt for password can be eliminated by adding the host's public key in the user's authorized_keys file. Adversaries can do the same for execution on remote machines.

ssh localhost "{CMD}"
ExecutePrivileges: User
T1202: Technique T1202

Executes specified command from ssh.exe

ssh -o ProxyCommand="{CMD}" .
ExecutePrivileges: User
T1202: Technique T1202

Executes a DLL from an SMB share by abusing the PKCS11Provider option. The payload executes upon DLL load (DllMain) and requires exporting C_GetFunctionList to prevent premature termination by `ssh.exe`. Note that all backslashes should be escaped (i.e. every `\` should be turned into `\\`).

ssh -o PKCS11Provider="\\\\127.0.0.1\\Temp\\example.dll" win@github.com

SIEM & EDR Detection Rules

Production telemetry rules configured for Microsoft Defender, Sigma, and Splunk.

Telemetry & SIEM Detection Suite (ssh.exe)

Validated against MITRE T1202
ssh.exe Microsoft Defender Querykql
1// Microsoft Defender XDR / Microsoft Sentinel
2// Tactic: Execute
3DeviceProcessEvents
4| where FileName =~ "ssh.exe"
5| where ProcessCommandLine has_any ("ssh")
6| project
7 Timestamp,
8 DeviceName,
9 AccountName,
10 InitiatingProcessParentFileName,
11 InitiatingProcessFileName,
12 InitiatingProcessCommandLine,
13 FileName,
14 FolderPath,
15 ProcessCommandLine,
16 MD5,
17 SHA256
18| sort by Timestamp desc

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain ssh.exe abuse.

Application Whitelisting

Enforce Windows Defender Application Control (WDAC) or AppLocker publisher rules to prevent execution outside approved enterprise administration scripts.

Attack Surface Reduction

Enable ASR rules: Block executable content from email client and webmail and Block Office applications from creating child processes spawning ssh.exe.

Behavioral Alerting

Deploy the KQL, Sigma, and Splunk detection queries below. Alert on anomalous child processes, web requests to unrated external IPs, or encoded payload strings.

Frequently Asked Questions (FAQ) • ssh.exe

Key operational questions and defensive answers about ssh.exe LOLBin tradecraft.

What is ssh.exe and why is it classified as a LOLBin?

ssh.exe is a legitimate, pre-installed or trusted utility on Windows. It is classified as a Living-off-the-Land Binary (LOLBin) because adversaries abuse its built-in functionality to perform malicious operations—such as Execute—without dropping custom malware binaries on disk.

How do threat actors abuse ssh.exe in cyber intrusions?

Adversaries leverage ssh.exe to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "ssh localhost "{CMD}"" to achieve Execute, masquerading behind legitimate system process lineage.

How can SOC analysts detect suspicious ssh.exe activity?

Detection engineers monitor process creation events (Windows Event ID 4688 or Sysmon Event ID 1; Linux auditd EXECVE; macOS Endpoint Security) inspecting anomalous command line arguments, unusual parent-child process relationships (e.g. Office apps or web servers spawning ssh.exe), and unexpected network connections.

What MITRE ATT&CK techniques does ssh.exe map to?

ssh.exe maps to MITRE ATT&CK technique(s): T1202. These techniques cover adversary actions across tactics such as Defense Evasion, Execution, Persistence, and Command and Control.

How can organizations mitigate and restrict ssh.exe?

Mitigation strategies include implementing Application Control policies (AppLocker or Windows Defender Application Control - WDAC), enforcing Attack Surface Reduction (ASR) rules, configuring strict privilege separation (disallowing standard users from running sensitive switches), and alerting on execution from non-standard directories.

Sharon Ben Moshe
Curated & Verified by
Sharon Ben Moshe
Cybersecurity Researcher & Detection EngineerCheck Point