GL.iNet: Cloud flaw exploited to install malware and reverse shells on routers/KVM devices
Severity: high · Patch status: partial · Since 2026-11-20
GL.iNet says that on 20 November 2026 it identified a vulnerability in its cloud remote management service (GoodCloud) that an unidentified party used to install malicious software on some routers and KVM devices. It has fixed the cloud flaw and blocked the attack path, but says that does not remove malware from devices already infected, and its published check looks for a single process. RemoteToHome Consulting, which is not affiliated with GL.iNet, reports root reverse shells to 170.39.226.219 on GL-AXT1800 (firmware 4.8.2 and 4.8.3) and GL-MT6000 (4.9.1) routers starting between 20:06 and 21:40 UTC on 20 November, found that single process on none of the routers it examined, and found older backdoors and attacker commands on other models. Its counts come from its own fleet and are not a prevalence estimate; GL.iNet has not published a device count. Stable router and KVM firmware was scheduled for 22 November, but the only fixed builds named in the fetched sources are KVM betas (1.10.2 or later, and 1.8.6 or later for RMQ1), and RemoteToHome saw no router firmware released as of 06:20 UTC on 22 November. No CVE, advisory ID, or threat actor is named in any fetched source.
What to do
- Treat GL.iNet routers and KVM devices that had GoodCloud enabled as potentially compromised. GL.iNet's check (process containing 'crond -i /tmp/.log') is necessary but not sufficient: RemoteToHome did not find that process on any router it examined, while the remote shell and backdoor were present. Use the wider checks in RemoteToHome's README (shell process to 170.39.226.219, named pipe /tmp/f, the SDWAN_IP_MAPPING NAT rule, the /etc/init.d/urandom_seed and /lib/upgrade/keep.d/netifd changes).
- Until a router firmware fix is confirmed, switch GoodCloud off on the device. RemoteToHome reports the router cloud client only starts when GoodCloud is enabled. Block the 170.39.226.0/24 range seen in the remote-shell cases.
- Isolate suspected devices from production networks and preserve logs and evidence before resetting or reflashing. GoodCloud logs may be missing for 20 November; export what remains.
- Reinstall firmware with 'Keep Settings' off, from an image downloaded directly from GL.iNet, and do not restore a configuration from a suspect device. A factory reset alone leaves the installed image in place (RemoteToHome).
- KVM devices: install the 1.10.2 beta or later now (1.8.6 beta or later for RMQ1). Move to the stable build when it is published; the download list names 1.10.3 or later (RMQ1: 1.8.7 or later) as the stable minimum, but no stable release is confirmed in fetched sources. Note that the RM1 1.10.2 build does not contain the boot-time cleanup that RM1PE 1.10.2 does (RemoteToHome).
- Rotate every credential, key and VPN profile stored on a suspect device, and remove its access on the server side as well. Analyse computers connected to affected KVM devices for compromise; GL.iNet says that investigation is ongoing.
Fixed versions
- KVM beta, per GL.iNet notice: 1.10.2 beta or later for RM10, RM1, RM1V2, RM1PE, RM4PE; 1.10.2 beta or later for RM10RC; 1.8.6 beta or later for RMQ1
- Stable minimums named on the KVM download list in forum thread 73069 (attributed to GL.iNet upgrade guidance by Bleeping Computer): 1.10.3 or later for RM10, RM1, RM1V2, RM1PE, RM4PE; 1.10.3 beta or later for RM10RC; 1.8.7 or later for RMQ1. Stable release not confirmed in fetched sources
- Routers: no fixed build confirmed released in fetched sources; GL.iNet scheduled stable firmware for 2026-11-22 without version numbers
Sources
All live incidents on Threat Watch