The breach isn’t the problem. The spread is. →Free Assessment

Executive Summary

In October 2026, FortiGuard Labs discovered ClingSTUN, a sophisticated Linux malware strain targeting Internet of Things (IoT) devices through 24 known vulnerabilities spanning from 2014 to 2026. The malware exploits devices from manufacturers including D-Link, Realtek, Ivanti, and TP-Link, transforming compromised systems into proxy nodes for malicious traffic routing. What distinguishes ClingSTUN is its innovative use of legitimate public STUN servers to obscure command-and-control communications, making malicious activity appear as normal VoIP and WebRTC traffic while establishing persistent access to enterprise networks.

This incident highlights the growing weaponization of IoT infrastructure as threat actors increasingly leverage unpatched devices for proxy operations and network persistence. The malware's multi-architecture exploit chain and living-off-the-land techniques represent an evolution in IoT-targeted campaigns, emphasizing the urgent need for comprehensive IoT security frameworks as organizations face mounting pressure to secure their expanding attack surfaces.

Why This Matters Now

ClingSTUN demonstrates how unpatched IoT devices are becoming critical infrastructure for cybercriminal proxy operations, with attackers now capable of blending malicious traffic into legitimate network protocols to evade detection at scale.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

ClingSTUN uses legitimate public STUN servers to blend malicious communications with normal VoIP and WebRTC traffic, making it extremely difficult to distinguish from legitimate network activity.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF would constrain ClingSTUN's lateral spread across IoT devices through network segmentation and east-west traffic controls. The fabric's identity-aware routing and egress enforcement would likely reduce the malware's ability to establish widespread proxy networks and covert communications.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: Initial device compromise would likely still occur, but the fabric's microsegmentation policies would constrain the malware's ability to discover and communicate with other network segments beyond the compromised device's immediate zone.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: While device-level privilege escalation may succeed, zero trust segmentation would likely constrain the malware's elevated privileges to the compromised device's isolated network segment, preventing privileged access to adjacent systems or network resources.

Lateral Movement

Control: East-West Traffic Security

Mitigation: Lateral movement attempts would likely be constrained by east-west traffic inspection and policy enforcement, reducing the malware's ability to reach and exploit vulnerable devices across different network segments or security zones.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: STUN server communications would likely be subject to visibility and policy controls, potentially constraining the malware's ability to establish reliable command channels and reducing its operational effectiveness across multiple cloud environments.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress policy enforcement would likely constrain the malware's ability to establish effective proxy networks by limiting outbound traffic patterns and destinations from compromised IoT devices, reducing data exfiltration capabilities and traffic routing effectiveness.

Impact (Mitigations)

Despite containment measures, organizations would likely still experience some operational impact from compromised devices within isolated segments, though the scope of internal network access and reputational damage would be significantly reduced.

Impact at a Glance

Affected Business Functions

  • Network Infrastructure Management
  • Industrial Control Systems
  • Surveillance and Monitoring
  • Internet Gateway Services
Operational Disruption

Estimated downtime: 7 days

Financial Impact

Estimated loss: $500,000

Data Exposure

Compromised IoT devices can expose internal network topology, surveillance footage, operational technology data, and serve as proxy infrastructure for malicious activities leading to IP blocklisting and reputational damage

Recommended Actions

  • • Implement Zero Trust Segmentation to isolate IoT devices from critical network segments and prevent lateral movement between compromised devices
  • • Deploy Egress Security & Policy Enforcement to detect and block unauthorized outbound communications from IoT devices to STUN servers and other external destinations
  • • Enable Multicloud Visibility & Control to monitor anomalous interactions, repeated malformed requests, and suspicious automation patterns from IoT devices
  • • Establish East-West Traffic Security controls to inspect and control workload-to-workload communications and detect lateral movement attempts between IoT systems
  • • Deploy Threat Detection & Anomaly Response capabilities to baseline normal IoT device behavior and alert on deviations such as unexpected STUN communications and proxy traffic patterns

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Cta pattren Image