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.
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.
GL.iNet provided a specific indicator of compromise for users to check. This provides valuable insight into the malware's behavior.
crond -i /tmp/.log indicates a device has been compromised.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.T1190 - Exploit Public-Facing Application: The initial vector was a vulnerability in the GoodCloud web service.T1219 - Remote Services: The attackers used the legitimate remote management service to push commands to the devices.T1059.004 - Command and Scripting Interpreter: Unix Shell: Shell commands were used to download and execute the malware.T1543.002 - Create or Modify System Process: Systemd/System V: While crond is the specific indicator, similar persistence could be achieved through system services.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.
No traditional file hashes, IPs, or domains were provided in the source article. However, a specific process execution pattern was given as an indicator.
In addition to the specific command provided by GL.iNet, security teams and users should hunt for the following:
crond -i /tmp/.logps aux | grep tmp./tmp/.log/etc/uci-defaults/ and /etc/sysupgrade.confps | grep tmp.crond -i /tmp/.log, the device is compromised.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.
GL.iNet discovered and announced the breach of its cloud services.

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.
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.
Help others stay informed about cybersecurity threats
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.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
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 detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.