GL.iNet Cloud Breach Leads to Malware on Routers

GL.iNet Cloud Flaw Actively Exploited to Deploy Malware on Routers

HIGH
November 21, 2026
5m read
CyberattackVulnerabilityIoT Security

Related Entities

Organizations

Products & Tech

GoodCloud

Full Report

Executive Summary

On November 20, 2026, networking product manufacturer GL.iNet issued a security notice informing customers of a breach affecting its cloud remote management platform, GoodCloud. An unidentified threat actor exploited a vulnerability in the cloud service to push malicious software to an unknown number of customer-managed GL.iNet routers and KVM devices. The company reports that it has since closed the vulnerability on its cloud infrastructure. However, devices that were compromised remain so until remediated by their owners. GL.iNet has provided a command to help users identify infected devices and recommends a firmware upgrade or device reset as the solution.

Threat Overview

This incident is a classic example of a supply chain attack targeting a vendor's cloud management platform to compromise downstream customer devices. By exploiting a single vulnerability in GL.iNet's GoodCloud service, the attackers were able to gain remote access and execute commands on connected devices. The exact nature of the vulnerability was not disclosed. The goal of the attack was to install malicious software, though the purpose of this malware (e.g., credential theft, DDoS bot, traffic interception) has not yet been specified by the company.

Technical Analysis

GL.iNet provided a specific indicator of compromise for users to check. This provides valuable insight into the malware's behavior.

  • Indicator of Compromise: A running process matching the pattern crond -i /tmp/.log indicates a device has been compromised.
  • Analysis: The use of crond suggests the malware is establishing persistence through a scheduled task. The -i flag is not a standard crond option on most systems, suggesting it may be a custom-compiled version or the command is being used to disguise its true purpose. The output being directed to a hidden file (.log) in the temporary directory (/tmp/) is a common technique to hide malicious activity and components.
  • Potential TTPs:

Impact Assessment

The compromise of edge networking devices like routers poses a significant risk. An attacker with control of a router can monitor all unencrypted network traffic, redirect users to phishing sites (DNS hijacking), launch attacks against other devices on the local network, or use the device as part of a larger botnet for DDoS attacks. The lack of a CVE and detailed technical disclosure from GL.iNet has drawn criticism, as it hinders defenders' ability to fully assess the risk and hunt for related malicious activity.

IOCs — Directly from Articles

No traditional file hashes, IPs, or domains were provided in the source article. However, a specific process execution pattern was given as an indicator.

Cyber Observables — Hunting Hints

In addition to the specific command provided by GL.iNet, security teams and users should hunt for the following:

  • Command Line Pattern: crond -i /tmp/.log
    • Context: Check running processes via SSH or terminal access using ps aux | grep tmp.
    • Confidence: High
  • File Path: /tmp/.log
    • Context: Check for the existence of this hidden file. Its contents may reveal more about the malware.
    • Confidence: High
  • File Path: /etc/uci-defaults/ and /etc/sysupgrade.conf
    • Context: As suggested by community members, check these paths for unexpected scripts or configuration changes that could indicate a persistence mechanism designed to survive reboots or firmware upgrades.
    • Confidence: Medium
  • Network Traffic Pattern: Unexplained outbound connections from the router to unknown IP addresses, especially on non-standard ports.
    • Context: Firewall logs, Netflow.
    • Confidence: Medium

Detection & Response

  1. Check for Compromise: All GL.iNet users should immediately log into their device's terminal and run the command ps | grep tmp.
  2. Analyze Output: If the output contains crond -i /tmp/.log, the device is compromised.
  3. Remediate: If compromised, the device should be disconnected from the internet. The recommended actions are to perform a factory reset and then immediately upgrade to the latest available firmware version. Before reconnecting, it is advisable to inspect configuration files for any signs of persistence mechanisms.

Mitigation

  • Update Firmware: Proactively update all GL.iNet devices to the latest firmware version, as this may contain patches that prevent the malware from re-infecting the device.
  • Disable Remote Management: If remote cloud management via GoodCloud is not a critical requirement, disable it in the device settings. This severs the connection to the cloud platform, removing this attack vector entirely.
  • Change Default Credentials: Ensure that the device's local administrative password is changed from the default to a strong, unique password.

Timeline of Events

1
November 20, 2026
GL.iNet discovered and announced the breach of its cloud services.
2
November 21, 2026
This article was published

MITRE ATT&CK Mitigations

Updating device firmware is a critical step to remove the malware and patch any local vulnerabilities it may have exploited.

Disabling the cloud remote management feature removes the attack vector used in this incident.

If remote management is necessary, restricting its access to specific trusted IP addresses can prevent widespread exploitation.

Timeline of Events

1
November 20, 2026

GL.iNet discovered and announced the breach of its cloud services.

Sources & References

forum.gl-inet.com
GL.iNet (forum.gl-inet.com)

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

GL.iNetIoTRouterMalwareVulnerabilityCloud SecuritySupply Chain Attack

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

⚡ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.