NEWS

GL.iNet Confirms GoodCloud Flaw Was Used to Infect Routers and KVM Devices

Attackers abused GL.iNet's cloud management service to plant backdoors and reverse shells. The cloud hole is fixed, but existing infections are not removed.

Dylan H.

News Desk

November 22, 2026
2 min read
GL.iNet Confirms GoodCloud Flaw Was Used to Infect Routers and KVM Devices

Overview

GL.iNet has confirmed that attackers exploited a vulnerability in its GoodCloud remote management service to install custom malware on customers' routers and KVM devices. Some users report backdoors and reverse shells giving remote access. BleepingComputer reported the details on Nov 22, 2026. No CVE was mentioned.

What Happened

  • On Nov 19, a compromised KVM downloaded malicious scripts and payloads.
  • GL.iNet published its advisory on Nov 20 and says the cloud flaw is fixed and the access path blocked.
  • Some malicious files carry timestamps from December 2025, so some devices may have been infected for months.
  • GL.iNet has not said how the cloud platform was exploited, how many customers are affected or whether data was stolen.
  • Researchers at RemoteToHome Consulting found a possible root-level command injection in the GoodCloud client's AstroWarp/SD-WAN handler. GL.iNet has not confirmed it was used. The same researchers saw suspicious activity on 152 of 183 routers analyzed, 24 with root reverse shells.

The fixes stop new infections through this route. They do not remove malware already installed.

Indicators of Compromise

IndicatorDetail
Processcrond -i /tmp/.log
Script and binariesni.sh, gl-helper, gb
PersistenceStartup scripts and scheduled tasks
Hidden trafficModified netstat hiding connections to 66.245.219[.]252
Reverse shell170.39.226[.]219
Other infrastructure65.20.71[.]131

A malicious Lua payload was also found on a GL-MT2500 router.

What to Do

  1. Install the latest firmware. Minimum KVM versions are 1.10.3 for RM10, RM1, RM1V2, RM1PE and RM4PE; 1.10.3 beta for RM10RC; and 1.8.7 for RMQ1.
  2. Check devices for the indicators above, even if a scan finds nothing. The community detection tool may miss some infections.
  3. If compromised, preserve evidence, then reinstall firmware without keeping settings. Malicious files in configuration directories can survive a normal upgrade.
  4. Rotate credentials and access keys that may have been exposed.
  5. Analyze computers that were connected to infected KVMs. GL.iNet is still investigating that.
  6. Block the listed IPs at your perimeter and search logs for past connections.

Sources