The short version
- The flaw. GL.iNet confirmed in a 20 November advisory that an unauthorised party exploited a vulnerability in its cloud remote management services to reach devices and install malicious software. The company says it has fixed the cloud flaw and blocked the access used in the incident.
- What was installed. Customers and researchers found custom malware written for GL.iNet hardware and root-level reverse shells, which allow an attacker to execute commands on the device. An installer examined by BleepingComputer disguises the malicious process as crond -i /tmp/.log, filters out connections to one attacker address from netstat output and installs SSH public keys for remote access.
- Detection limits. GL.iNet's first indicator was a process running as crond -i /tmp/.log, and forum members warn this may miss other backdoors. The company links a community scanner in its support instructions, but its developers say it cannot find every infection.
- Scope unknown. GL.iNet has not disclosed how many customers were affected, how its cloud platform was exploited, or whether information was stolen. It is investigating whether computers connected to infected KVM devices were also compromised.
Timeline
| Date | Event |
|---|---|
| 19 Nov | The owner of a compromised GL-RM1 KVM reports logs showing the device downloading a malicious ni.sh script and further payloads from 66.245.219[.]252. |
| 20 Nov | GL.iNet publishes an advisory confirming that its cloud remote management services were exploited and says the attack path is blocked. |
| 22 Nov | GL.iNet says stable firmware updates with additional security fixes for routers and KVM devices are scheduled for release. |
How the attack worked
GL.iNet's advisory covers GoodCloud, the platform customers use to manage supported routers and KVM devices remotely, including computers and servers attached to its KVM products. The company says it fixed the cloud vulnerability and blocked the access used in the incident, and it warned that these measures do not clean devices that were already infected.
BleepingComputer examined a copy of the malicious installer, ni.sh, and found code tailored to GL.iNet hardware. It recognises a range of the company's models, downloads payloads named gl-helper and gb from hardcoded servers, and survives reboots through startup scripts and scheduled tasks. It also replaces the legitimate netstat utility with a script that filters out connections to one attacker address, installs SSH public keys, alters file timestamps and periodically fetches commands from a remote server. The script contains Chinese-language developer comments.
Who is affected
The products involved are routers and KVM devices managed through GoodCloud. GL.iNet has not said how many customers were affected, how the attackers got in, or whether information was stolen, and it is investigating whether computers connected to infected KVM units were compromised. Customers and researchers have reported custom malware and root-level reverse shells connecting back to 170.39.226[.]219.
RemoteToHome Consulting analysed 183 routers it owns or manages and found suspicious activity on 152: 24 with root-level reverse shells, 47 carrying an older persistent backdoor and 81 showing signs that attacker commands had run. The researchers caution that their results may not reflect other customers and that the older backdoor infections may not be tied to the November attacks. Separately, the owner of a compromised GL-RM1 KVM reported the device contacting roughly 1,800 residential IP addresses a day and repeatedly reaching a blockchain API; the purpose is unclear and there is no confirmation the devices were used as proxies or as part of a botnet.
The unconfirmed cause
Researchers at RemoteToHome Consulting described a possible command injection flaw in GL.iNet's GoodCloud client, in a handler used for AstroWarp/SD-WAN functions, which they say passes cloud-supplied values into shell commands run with root privileges without validating them. GL.iNet has not confirmed that this flaw was used in the attacks, and it has not explained how its cloud platform was exploited.
What is not known yet
- Who carried out the attack, and whether specific customers were targeted.
- How many devices or customers were infected.
- Whether data was taken from compromised devices or from computers attached to infected KVM units.
- Whether the command injection flaw described by RemoteToHome Consulting is the one that was exploited.
- What the connections to roughly 1,800 residential IP addresses were for.
What to do
If you use GL.iNet routers or KVM devices
- Look for a process running as crond -i /tmp/.log, the indicator GL.iNet published, and run the community scanner the company links from its support instructions, uploading the anonymous report when prompted.
- Install the latest security firmware for your model; KVM owners should check GL.iNet's advisory for the minimum version, which is 1.10.3 or later for several models.
- Preserve evidence before resetting a suspect device, and if you reinstall firmware do not keep existing settings or restore a configuration taken from an infected device.
- Rotate credentials and access keys that may have been exposed through the device.
If you run KVM devices
- Analyse the computers and servers controlled through the KVM for signs of compromise.
- Check network logs for outbound connections to 66.245.219[.]252, 65.20.71[.]131 and 170.39.226[.]219, and for reverse shells built on the Linux nc utility.
For everyone else
- Inventory routers, KVM units and other hardware managed through vendor cloud services, and put their firmware updates on a scheduled patch cycle rather than waiting for an incident.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.