Renaming of OpenSSH Binaries
Adversaries may modify SSH related binaries for persistence or credential access by patching sensitive functions to enable unauthorized access or by logging SSH credentials for exfiltration.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the 5 ATT&CK techniques it maps to.
- Log source category
- event_index
Known benign triggers
- Trusted OpenSSH executable updates. It's recommended to verify the integrity of OpenSSH binary changes.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| blog.angelalonso.es/2016/09/anatomy-of-real-linux-intrusion-part-ii.html | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 0415f22a-2336-45fa-ba07-618a5942e22c
- Tagged by the source as
- Data Source: Elastic DefendData Source: Elastic EndgameDomain: EndpointNoise: MediumOS: LinuxPerformance: NormalPlatform: LinuxResources: Investigation GuideResources: OsqueryRule Type: Custom Query (KQL)Tactic: Credential AccessTactic: Lateral MovementTactic: PersistenceUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Oct 9, 2026
- Version
- 5