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.
ID | Name | Description |
---|---|---|
S0486 | Bonadan |
Bonadan has maliciously altered the OpenSSH binary on targeted systems to create a backdoor.[1] |
S0377 | Ebury |
Ebury has been embedded into modified OpenSSH binaries to gain persistent access to SSH credential information.[2] |
S0604 | Industroyer |
Industroyer has used a Trojanized version of the Windows Notepad application for an additional backdoor persistence mechanism.[3] |
S0487 | Kessel |
Kessel has maliciously altered the OpenSSH binary on targeted systems to create a backdoor.[1] |
S0641 | Kobalos |
Kobalos replaced the SSH client with a trojanized SSH client to steal credentials on compromised systems.[4] |
S0595 | ThiefQuest |
ThiefQuest searches through the |
S0658 | XCSSET |
XCSSET uses a malicious browser application to replace the legitimate browser in order to continuously capture credentials, monitor web traffic, and download additional modules.[7] |
ID | Mitigation | Description |
---|---|---|
M1045 | Code Signing |
Ensure all application component binaries are signed by the correct application developers. |
ID | Data Source | Data Component |
---|---|---|
DS0022 | File | File Creation |
File Deletion | ||
File Metadata | ||
File Modification |
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.