SSH and RDP provide remote access to server machines (Linux and Windows respectively) for administration. Both protocols are vulnerable to brute-force attacks if solid passwords and access controls are not implemented.
Exposed SSH ports (default 22) are scanned by attackers who attempt unauthorized logins to gain control of the server.
Once in, they can deploy malware or steal data, while attackers can also use SSH to move laterally within a compromised network.
Attackers scan for open port 22 (SSH) and use dictionary attacks to gain access to Linux systems by first identifying potential targets with port scanners and banner grabbers, then leveraging SSH dictionary attack tools to try username and password combinations from a wordlist.
Analyze any MaliciousURL, Files & Emails & Configuration With ANY RUN : Start your Analysis
Successful logins allow them to steal configuration data and potentially install malware to find more vulnerable systems, as researchers identify these attacks by detecting multiple login failures.
Attackers exploit weak SSH configurations to gain access to systems, and after compromising an initial server, some malware like Kinsing can self-propagate by using the stolen credentials to launch scans and dictionary attacks on other vulnerable machines.
This process allows attackers to expand their reach and potentially build a network of infected devices for further malicious activities.
Security solutions can monitor suspicious commands issued through SSH connections to help administrators identify and stop such attacks before they spread.
Kinsing malware leverages SSH key-based authentication for lateral movement. The malware’s “spre.sh” script extracts hostnames, ports, usernames, and key file locations from SSH configuration files and credential caches on infected systems.
It then iterates through this data, attempting SSH logins with each key-user combination, and upon successful login, the script utilizes curl or wget to download and execute a malicious downloader script, further propagating Kinsing across the network.
ASEC outlines a data collection strategy for identifying potential SSH propagation points, which focuses on system files and processes that might contain usernames, SSH hostnames, and public key locations.
The collector will search for SSH configuration files (*/.ssh/config), bash history (*/.bash_history), system hosts file (*/etc/hosts), known SSH hosts (*/.ssh/known_hosts), and processes connected to port 22.
To identify users, it will look for private keys (*/id_rsa and */.bash_history) and public keys (*/.ssh/config, */.bash_history, and *.pem), which aims to gather evidence of established SSH connections and credentials that could be leveraged to spread access across a network.
They identify malicious lateral movement attempts by monitoring file access behavior. Specifically, it detects instances where a file attempts to read both a system log file and an SSH key file.
The combination suggests the file might be malware trying to gather user login credentials from logs and then leverage SSH keys to spread to other machines on the network.
Looking for Full Data Breach Protection? Try Cynet's All-in-One Cybersecurity Platform for MSPs: Try Free Demo