- Home
- Techniques
- Enterprise
- Compromise Client Software Binary
Compromise Client Software Binary
Adversaries may modify client software binaries to establish persistent access to systems. Client software enables users to access services provided by a server. Common client software types are SSH clients, FTP clients, email clients, and web browsers.
Adversaries may make modifications to client software binaries to carry out malicious tasks when those applications are in use. For example, an adversary may copy source code for the client software, add a backdoor, compile for the target, and replace the legitimate application binary (or support files) with the backdoored one. Since these applications may be routinely executed by the user, the adversary can leverage this for persistent access to the host.
Procedure Examples
Name | Description |
---|---|
Bonadan |
Bonadan has maliciously altered the OpenSSH binary on targeted systems to create a backdoor.[1] |
Ebury |
Ebury has been embedded into modified OpenSSH binaries to gain persistent access to SSH credential information.[2] |
Kessel |
Kessel has maliciously altered the OpenSSH binary on targeted systems to create a backdoor.[1] |
Mitigations
Mitigation | Description |
---|---|
Code Signing |
Ensure all application component binaries are signed by the correct application developers. |
Detection
Collect and analyze signing certificate metadata and check signature validity on software that executes within the environment. Look for changes to client software that do not correlate with known software or patch cycles.
Consider monitoring for anomalous behavior from client applications, such as atypical module loads, file reads/writes, or network connections.