# ClingSTUN Linux Backdoor Exploits Dozens of Flaws via STUN Protocol > FortiGuard Labs identifies ClingSTUN, a Linux backdoor that abuses the STUN protocol and exploits dozens of flaws for self-propagation. - Published: 2026-10-06T03:51:26.000Z - Severity: high - Category: Malware - Tags: Linux, Backdoor, Iot Security, ClingSTUN, STUN Protocol - Author: Runtime Rebel Intel - Primary source: https://www.securityweek.com/linux-backdoor-abuses-stun-protocol-exploits-dozens-of-flaws/ - Canonical: https://runtimerebel.com/blog/clingstun-linux-backdoor-exploits-dozens-of-flaws-via-stun-protocol ## Key points - Linux systems are compromised by ClingSTUN, a backdoor creating proxies and enabling remote command execution. - Embedded Linux devices from vendors like Avtech, D-Link, Ivanti, and Realtek are vulnerable to ClingSTUN exploits. - Prioritize patching known vulnerabilities, monitor STUN activity, and investigate suspicious UDP connections immediately. ## ClingSTUN: A Linux [Backdoor](/glossary#backdoor) Abusing STUN Protocol for Covert Operations FortiGuard Labs recently uncovered ClingSTUN, a sophisticated Linux backdoor transforming infected systems into back-connect proxies. This [malware](/glossary#malware) notably abuses the Session Traversal Utilities for NAT (STUN) protocol to maintain connectivity and exploits a broad range of vulnerabilities for [initial access](/glossary#initial-access) and self-propagation, posing a significant threat to various embedded Linux devices, as detailed by [SecurityWeek](https://www.securityweek.com/linux-backdoor-abuses-stun-protocol-exploits-dozens-of-flaws/). ClingSTUN's primary function is to establish a covert proxy network, allowing its operators to maintain access to compromised systems despite network address translation (NAT). This is achieved by leveraging legitimate public STUN servers to discover external IP addresses and port mappings. This technique helps maintain NAT connectivity without relying on a distinct command-and-control ([C2](/glossary#c2)) server registration, complicating detection efforts. ### Technical Details: ClingSTUN's Modus Operandi The ClingSTUN backdoor exhibits several malicious capabilities aimed at [persistence](/glossary#persistence) and propagation: * **[Vulnerability](/glossary#vulnerability) Exploitation**: The malware targets a substantial number of vulnerabilities—dozens in total—for initial access. FortiGuard Labs observed indiscriminate exploitation of flaws in devices from vendors including Avtech, EnGenius, D-Link, Hytec, Ivanti, Lantronix, Linear, MeiG, Realtek, Sunhillo, Tenda, and TP-Link. This wide net indicates an opportunistic approach to compromise. Additionally, its self-propagation mechanism contains hardcoded exploits for seven more specific vulnerabilities affecting China Mobile, KGUARD, Linksys, LB-LINK, MVPower, Realtek, and TBK devices. * **Multi-Architecture Support**: To maximize its reach, ClingSTUN downloaders fetch payloads tailored for diverse architectures, including AMD X86-64, ARM, Intel 80386, MIPS R3000, and PowerPC. This broad compatibility enables it to infect a wide array of Linux-based embedded and IoT devices. * **Persistence Mechanisms**: The malware ensures its continued execution by copying itself to two hidden files with executable permissions. It then modifies three system initialization scripts by appending startup commands, securing its presence during the boot sequence. * **Back-Connect Proxy and STUN Abuse**: ClingSTUN establishes a UDP socket, binding to a random local port. It then sends standard STUN binding requests to legitimate public STUN servers. After completing these exchanges, the malware periodically reports its group identifier and mapped-port list to the STUN endpoints, effectively creating its proxy chain. This makes it challenging to differentiate legitimate STUN traffic from malicious activity. * **Remote Command Execution**: Operators can perform remote code execution and trigger the self-propagation mechanism by sending specific packets to the compromised systems. * **Anti-Forensics/Anti-Competition**: Three observed variants of the [botnet](/glossary#botnet) consistently kill competitor processes and terminate watchdog timers, suggesting efforts to maintain exclusive control over infected hosts. ### Analysis: The [Threat Landscape](/glossary#threat-landscape) of ClingSTUN ClingSTUN represents a notable threat, particularly to the Internet of Things (IoT) and embedded device ecosystems. The indiscriminate exploitation of numerous vulnerabilities across a wide range of vendors indicates a campaign aimed at mass compromise rather than highly targeted attacks. The abuse of legitimate STUN protocol for communication not only aids in bypassing traditional network defenses but also complicates [threat hunting](/glossary#threat-hunting), as STUN traffic might not immediately be flagged as malicious. The multi-architecture support ensures a broad [attack surface](/glossary#attack-surface), affecting potentially millions of devices globally. ### Mitigation and Detection: Defending Against ClingSTUN Defending against the ClingSTUN backdoor requires a multi-layered approach, focusing on patching, network monitoring, and [endpoint](/glossary#endpoint) detection. * **Prioritize Patching**: The most critical immediate action is to apply all available security updates for devices from the identified vendors (Avtech, EnGenius, D-Link, Hytec, Ivanti, Lantronix, Linear, MeiG, Realtek, Sunhillo, Tenda, TP-Link, China Mobile, KGUARD, Linksys, LB-LINK, MVPower, TBK). Regularly checking vendor advisories for [vulnerabilities exploited by ClingSTUN](https://www.securityweek.com/linux-backdoor-abuses-stun-protocol-exploits-dozens-of-flaws/) is essential. * **Network Monitoring**: Implement strict network monitoring to detect anomalies: * **STUN Traffic Analysis**: While STUN is legitimate, assess STUN activity alongside other suspicious behaviors. Look for STUN requests originating from devices that typically should not be initiating such connections. * **Unusual UDP Connections**: Monitor for unexpected or high volumes of UDP connections, especially those on random local ports. * **Recurring Keepalive Traffic**: Watch for consistent, periodic keepalive traffic patterns that might indicate a persistent backdoor communication channel. * **Endpoint Security**: Implement endpoint detection and response ([EDR](/glossary#edr)) solutions capable of monitoring Linux systems. Focus on detecting: * **Suspicious Process Behavior**: Look for unusual processes or command executions, particularly those initiated during system boot. * **File System Integrity Monitoring**: Monitor for unauthorized file creation in hidden directories or modifications to system initialization scripts (e.g., `/etc/rc.local`, `/etc/init.d/boot.local`, `/etc/profile`). This is key to understanding how to detect ClingSTUN malware persistence. * **Resource Utilization**: Keep an eye on unexpected spikes in network traffic or CPU usage that could indicate proxy activity or remote command execution. By combining proactive patching with diligent network and endpoint monitoring, organizations can significantly reduce their exposure to threats like ClingSTUN and enhance their ability to detect and respond to such sophisticated backdoors. **Related:** [New Linux Backdoors Mimic Asian Mail Security Products](/blog/new-linux-backdoors-mimic-asian-mail-security-products), [UEFI Shim Bootloader Vulnerabilities: Secure Boot Blind Spot](/blog/uefi-shim-bootloader-vulnerabilities-secure-boot-blind-spot) --- AI-generated analysis from the primary source above; not human-reviewed before publication — verify anything operational against the original (https://runtimerebel.com/editorial). Quote with attribution and a link to the canonical URL: https://runtimerebel.com/blog/clingstun-linux-backdoor-exploits-dozens-of-flaws-via-stun-protocol