GL.iNet says it has closed a cloud vulnerability that attackers used to install malware on customers’ routers and KVM devices, but infected equipment still needs attention. The company disclosed the incident in a November 20 advisory, BleepingComputer reported on November 22: blocking further infections through that route does not clean devices already compromised.
The incident concerns GL.iNet’s cloud remote management services. Its GoodCloud platform lets customers administer supported equipment, including home and travel routers and KVM devices that provide remote control of connected computers and servers. GL.iNet is also investigating whether computers attached to infected KVMs were compromised.
The company recommends checking devices and installing the latest security firmware even when checks find no malware. Its public account leaves the customer total, precise exploitation method and any information theft unresolved.
Researchers find remote access across a managed fleet
After the disclosure, customers and researchers reported several forms of malicious access. These included reverse shells, which let attackers issue commands over connections initiated by an infected device. Some operated with root privileges—the highest level of administrative access—and used the Linux nc utility to reach 170.39.226[.]219.
RemoteToHome Consulting found suspicious activity on 152 of the 183 routers it owns or manages. That included 24 routers with root-level reverse shells, 47 carrying an older persistent backdoor and 81 showing that commands supplied by attackers had run. The researchers cautioned that their fleet might differ from other customers’ devices and that the older backdoors could be unrelated to the November attacks.
RemoteToHome also described a possible command injection weakness, where inadequately checked input becomes part of an executable command, in the GoodCloud client. A handler for AstroWarp/SD-WAN functionality allegedly inserts values received from the cloud into shell commands running as root without sufficient validation. Whether that weakness enabled these attacks remains unconfirmed by GL.iNet.
A separate account from a GL-RM1 KVM owner places malicious activity on November 19. The owner posted logs showing downloads of ni.sh, a malicious installation script, and additional executable files from 66.245.219[.]252.
The same owner reported daily communications with approximately 1,800 residential IP addresses and repeated requests to the TRON blockchain API, an interface for interacting with that network. The pattern suggested peer-to-peer activity, but its purpose, possible use for residential proxies and any connection to a larger botnet remain unconfirmed.
Installer can conceal traffic and restore malicious processes
BleepingComputer’s examination of ni.sh found an installer built to recognize numerous GL.iNet router and KVM models. It retrieves malicious programs named gl-helper and gb from servers whose addresses are embedded in the code.
Startup scripts and scheduled tasks give the malware persistence: mechanisms that bring it back after a reboot or restart it when its processes are stopped. The installer can present a malicious process as crond -i /tmp/.log, matching the sign of infection in GL.iNet’s initial detection instructions.
It also interferes with a common administrative check. The script replaces netstat, a utility for viewing network connections, with a shell script that omits connections to 66.245.219[.]252. Someone inspecting traffic through that altered utility could miss the malware’s connection to the address.
Other functions allow the installer to add SSH public keys for remote login, alter file timestamps and repeatedly fetch and execute commands from a remote server. BleepingComputer identified 66.245.219[.]252 and 65.20.71[.]131 as infrastructure used by the attacker; both addresses also appeared in the KVM owner’s logs.
Developer comments written in Chinese discuss persistence, reporting and interaction with GL.iNet’s cloud software. BleepingComputer interpreted them as suggesting a Chinese-speaking author.
The outlet separately examined malicious Lua code recovered from a GL-MT2500 router. A modified urandom_seed startup script launched that payload, which could gather device information, communicate with remote servers and retrieve and run further programs.
Some recovered malicious files bore December 2025 timestamps, suggesting potentially months-old compromises, although their relationship to the November incident or the same attackers is unclear.
Device checks and firmware updates require separate attention
GL.iNet initially directed users to look for crond -i /tmp/.log. Forum members warned that relying on that process alone could miss other backdoors or reverse shells.
The company’s official router and KVM support instructions now link to a community-developed scanner. Beyond known malicious files and suspicious processes, it checks system utilities for alterations and configuration files for changes that maintain an attacker’s access. It can preserve forensic evidence and, optionally, remove known malware components.
The developers caution that the scanner cannot identify every infection. Cleaning a compromised device may require reinstalling firmware without keeping its settings: malicious files in configuration directories can survive a normal firmware upgrade.
GL.iNet scheduled stable router and KVM firmware containing additional security fixes for November 22, 2026. The KVM upgrade guidance reported by BleepingComputer specifies:
- RM10, RM1, RM1V2, RM1PE and RM4PE: 1.10.3 or later.
- RM10RC: 1.10.3 beta or later.
- RMQ1: 1.8.7 or later.
Router owners should install the latest security firmware available for their particular model. GL.iNet also asks scanner users to submit the anonymous report when prompted, helping developers establish how many devices and which types were affected. The company continues investigating and plans to email identified affected customers at the addresses associated with their cloud accounts.
Customers who suspect an infection should preserve evidence before resetting equipment, avoid restoring potentially infected configurations, and rotate credentials and access keys that may have been exposed. KVM users should also examine the computers those devices control for possible compromise.




