New Malware Campaign Exploits Windows OpenSSH: How Hackers Are Turning Trusted Tools Against Us

Listen to this Post

Featured Image

Introduction

In an age where cybersecurity threats are growing more stealthy and sophisticated, a newly uncovered malware campaign is exploiting a widely trusted component in Windows: the built-in OpenSSH client. What once was considered a helpful tool for system administrators has now become a double-edged sword, offering hackers a discreet pathway into corporate systems. This alarming discovery sheds light on how attackers are now favoring subtlety over brute force, using legitimate utilities to silently create persistent backdoors and compromise entire networks. The threat isn’t coming from new viruses or ransomware, but from the very tools we rely on for secure communication and system management.

Hackers Hijack OpenSSH in Windows for Stealthy Backdoor Attacks

Cybersecurity analysts have identified a sophisticated malware strain that targets Windows systems by exploiting the built-in OpenSSH client. First observed by security expert Xavier Mertens from the Internet Storm Center, the malware disguises itself as a legitimate Windows process named “dllhost.exe.” What makes this malware particularly dangerous is its ability to go largely undetected—it was flagged by only 18 out of 71 scanners on VirusTotal.

The malicious payload specifically targets machines with OpenSSH installed, a component Microsoft began bundling with Windows 10 starting with version 1803. The attackers use the OpenSSH client to create a covert channel between the compromised system and their command-and-control server. This clever abuse of trusted software mirrors past incidents, including similar attacks using modified versions of SSH tools like PuTTY.

The malware works in multiple stages. It first attempts to start an SSH-related service on the infected system. If that fails, it scans the system registry for previously saved data to continue its attack. During its first run, it saves a randomly selected port number in the registry for future communication. Then it creates a custom SSH configuration file in the Windows temp folder, pointing to an attacker-controlled IP address (193.187.174.3) over port 443.

Once established, the malware enters an infinite loop, quietly launching ssh.exe processes at intervals using the rogue configuration. This makes the activity appear as normal SSH traffic, allowing it to blend in and potentially avoid detection from standard security tools.

Security experts warn this is part of a larger trend of “Living off the Land” (LotL) attacks. These strategies rely on exploiting built-in system tools—often called LOLBINs—instead of introducing foreign code that might trigger alarms. In this case, the Windows-integrated OpenSSH suite is weaponized to maintain unauthorized access and possibly exfiltrate data using legitimate methods like scp.exe.

To combat this, experts recommend that IT teams closely monitor OpenSSH activity, including unusual config files, unexpected services, and strange connections to unfamiliar IP addresses. Monitoring registry keys used by this malware variant can also help with early detection. Most importantly, organizations should establish baseline behavior for SSH usage and flag any anomalies.

The campaign serves as a stark reminder that even well-intentioned software updates, like including OpenSSH by default in Windows, can open doors for cyberattacks if not properly managed and monitored.

What Undercode Say:

This malware campaign illustrates a critical shift in modern cyberattack strategies—from flashy, obvious threats to stealthy, embedded ones. Instead of crafting new attack tools, threat actors are increasingly turning to what’s already available inside the operating system. The OpenSSH client in Windows, once a symbol of increased flexibility and secure remote access, is now being exploited as a backdoor by attackers who understand how to stay under the radar.

This is not just a technical problem but a visibility issue. Many organizations fail to monitor the internal usage of tools like ssh.exe because they assume it’s part of routine system administration. That blind spot is exactly what hackers are targeting. Once inside, these attackers use legitimate traffic patterns, making traditional signature-based defenses nearly useless.

The multi-stage persistence method used in this attack is clever. By storing a random port in the registry and using it consistently in future communications, the malware maintains a unique fingerprint while staying inconspicuous. Its infinite loop execution model with long sleep intervals further reduces its chances of being flagged as malicious behavior.

Another red flag is the use of the Windows temp directory to store malicious configuration files. Security teams often overlook temporary directories, yet these are frequently abused by malware for both payload staging and evasion. Moreover, the use of port 443, a standard HTTPS port, helps the malware bypass firewall rules that allow secure web traffic, increasing its ability to fly under the radar.

The classification of OpenSSH as a LOLBIN is important. It reflects the dual-use nature of many binaries in today’s security landscape. Tools meant for good can just as easily be turned into weapons, depending on who controls them. This means that endpoint detection solutions must evolve. They should focus not only on the binaries themselves but also on how, when, and by whom they are being used.

The malware’s impersonation of “dllhost.exe” is another example of using trusted Windows processes as camouflage. Process masquerading is a classic yet effective tactic that, when combined with network evasion techniques, makes forensic analysis even more difficult.

Administrators must now think differently. It’s not just about blocking malware, but about understanding behavior. Why is ssh.exe running on a user’s machine? What configuration is it using? Who is it connecting to? These questions need routine answers in modern security operations.

The incident also puts Microsoft in a tricky position. Including OpenSSH in Windows was meant to help IT teams, but it inadvertently broadened the attack surface. While it’s impractical to remove it, Microsoft and enterprise defenders need to collaborate on visibility, default configurations, and usage monitoring to minimize the associated risks.

In conclusion, this attack is a blueprint for the future of malware: low profile, high impact, and native to the operating system itself. Defensive strategies must catch up—and quickly.

Fact Checker Results ✅

Malware sample confirmed to be detected by only 18/71 scanners on VirusTotal.
IP address 193.187.174.3 and port 443 usage validated via malware config files.
Classification of OpenSSH as a LOLBIN supported by multiple cybersecurity advisories. 🔍

Prediction 🔮

The misuse of built-in tools like OpenSSH will continue to rise, especially as attackers refine LotL techniques. Expect to see more campaigns focusing on SSH-based persistence and data exfiltration. Future malware variants may further blur the lines between legitimate activity and compromise, demanding stronger behavioral analytics and endpoint visibility from security teams worldwide.

References:

Reported By: cyberpress.org
Extra Source Hub:
https://www.stackexchange.com
Wikipedia
Undercode AI

Image Source:

Unsplash
Undercode AI DI v2

Join Our Cyber World:

💬 Whatsapp | 💬 Telegram