EDGE DEVICE COMPROMISE

GL.iNet GoodCloud Flaw Used to Backdoor Routers and KVM Devices at Scale

Attackers abused a vulnerability in GL.iNet's GoodCloud remote management service to push custom malware and root reverse shells onto customer routers and KVM devices.

Matt Lucas  |  November 22, 2026  |  5 min
Editorial hero illustration
152 of 183
routers with suspicious activity in one fleet
24
devices with root reverse shells
~1,800
residential IPs contacted daily by one KVM
Nov 22
stable security firmware release
TL;DR
  • What: Attackers exploited a vulnerability in GL.iNet's GoodCloud cloud management service to install custom malware, backdoors and root reverse shells on customer routers and KVM devices.
  • Impact: Infected devices give attackers root on the network edge, and infected KVMs may expose the computers and servers they control, with one researcher fleet showing 152 of 183 routers affected.
  • Fix / mitigation: GL.iNet fixed the cloud flaw and released security firmware on November 22, 2026, with KVM targets of 1.10.3 or later for the RM10, RM1, RM1V2, RM1PE and RM4PE, 1.10.3 beta or later for the RM10RC and 1.8.7 or later for the RMQ1, but the patch does not remove existing malware.
  • Who's at risk: Any organization or remote worker running GL.iNet routers or KVM devices enrolled in GoodCloud remote management, along with every machine connected to those KVMs.

GL.iNet has confirmed that attackers exploited a vulnerability in its GoodCloud remote management service to install malware on customer routers and KVM devices. Affected users report custom backdoors and root-level reverse shells. One consultancy that manages 183 GL.iNet routers found suspicious activity on 152 of them. The cloud attack path is now closed, but GL.iNet says plainly that its fix does not remove malware from devices that were already infected.

This is an edge device compromise delivered through the management plane, not through the internet-facing services most teams watch. It also hits KVM-over-IP hardware, which gives whoever controls it keyboard, video and mouse access to the computers and servers plugged into it.

What GL.iNet Disclosed

In an advisory published November 20, 2026, GL.iNet said an unauthorized party exploited a flaw in its cloud remote management services to access devices and install malicious software. The company says it fixed the cloud vulnerability and blocked the access used in the incident, so devices can no longer be newly infected through this path.

GL.iNet has not disclosed how the cloud platform was exploited, how many customers were affected or whether data was stolen from compromised devices. It is still investigating whether computers connected to infected KVM devices were compromised. The first indicator the company published was a process running as crond -i /tmp/.log, which disguises itself as the standard cron scheduler.

Patching does not clean an infected device

GL.iNet states that its cloud fix stops new infections only. The developers of the community scanner GL.iNet links to warn that malicious files stored in configuration directories can survive an ordinary firmware upgrade, so a device that was compromised before the fix can stay compromised after the update.

Malware, Reverse Shells and Attacker Infrastructure

After the disclosure, customers and researchers shared evidence of malware built specifically for GL.iNet devices. Compromised routers ran root-level reverse shells that used the Linux nc utility to connect out to 170.39.226[.]219, giving the operators remote command execution as root.

In a separate forum report, the owner of a compromised GL-RM1 KVM shared network logs showing the device downloading a malicious script named ni.sh and additional executable payloads from 66.245.219[.]252 on November 19. After infection the device began talking to about 1,800 residential IP addresses every day and repeatedly contacted the TRON blockchain. That traffic pattern fits a device recruited into proxy or botnet infrastructure, with blockchain lookups commonly used to resolve command-and-control addresses, though GL.iNet has not attributed the activity.

One Fleet, 152 Suspicious Devices

RemoteToHome Consulting analyzed 183 routers it owns or manages. It found suspicious activity on 152, or 83 percent. Of those, 24 had root-level reverse shells, 47 carried an older persistent backdoor and 81 showed evidence that attacker-supplied commands had executed. The researchers note that their fleet may not represent the broader customer base and that the older backdoor may not be tied to the November campaign. Even so, a second, earlier persistence mechanism on 47 devices suggests GL.iNet hardware has been a target for longer than this incident.

RemoteToHome also identified a possible command injection flaw in the GoodCloud client, in a handler used for AstroWarp and SD-WAN functionality. According to the researchers, the handler passes values supplied by the cloud into shell commands that run as root without proper validation. GL.iNet has not confirmed this is the flaw used in the attacks, but the design means anyone who controls the cloud side can run root commands on every enrolled device.

Detection Gaps

GL.iNet forum members warn that the company's single process indicator will miss devices infected with other backdoors or running reverse shells. GL.iNet now links to a community-developed detection and cleanup tool in its official support instructions. The tool checks for known malware files, suspicious processes, modified system utilities and configuration files changed for persistence, and it can collect forensic evidence and remove known components.

Its developers say it cannot detect every infection and that compromised devices may need a firmware reinstall without keeping existing settings. GL.iNet has asked anyone who runs the scanner to upload the anonymous report so the scale of the campaign can be measured.

Vendor Fix and Guidance

GL.iNet scheduled stable security firmware for routers and KVM devices for November 22, 2026, and recommends installing it even where no malware is found. For KVM devices the targets are:

The vendor and the scanner developers advise preserving evidence before any reset, not restoring configurations that may be infected, and rotating credentials and access keys the devices could have exposed. For KVM deployments, GL.iNet says the computers those devices control should be analyzed for compromise too.

RedEye assessment

The real exposure here is trust in a vendor cloud that can run root commands on edge hardware. A KVM sitting in a server rack or a travel router on an executive's laptop gives an attacker a foothold that EDR does not see. Organizations should treat any GoodCloud-enrolled device as suspect until it has been verified clean, and should scope the investigation to every system those devices could reach.

Why It Matters

Cloud management planes for small network devices are rarely in an asset inventory and almost never in a threat model. This incident shows the result: one vendor-side flaw turned into root access across a customer base, delivered through a channel the devices were built to trust. Shadow IT routers and KVMs bought for remote access are exactly the gear that slips past change control, and they are now confirmed targets.

RedEye Security can assess your edge and remote access estate, find unmanaged GL.iNet and similar devices, and determine whether any were used as a bridge into your environment. Contact our team to schedule an assessment.

Questions about your exposure?

RedEye Security provides assessments for organizations that need to understand their real risk.

Talk to us