GL.iNet Says Attackers Used Its Cloud Service to Plant Malware on Routers and KVMs
GL.iNet, maker of the small travel routers many people use to run a VPN away from home, says an attacker used a hole in its cloud remote-management service to install malicious software on some of its routers and remote KVM devices.
The company says it found the flaw on 20 November and closed it on discovery. Its security notice doesn’t say how many devices were hit, when the attacks began or what the malware does.
On Saturday, 21 November, owners began receiving the notice by email, and GL.iNet released fixed firmware for its Comet KVMs. Router owners have a check, a reset instruction and a promise of new firmware.
The KVMs are the more alarming half. A Comet sits between you and a computer, so whoever controls it sees that computer’s screen and types on its keyboard.
When we published, the incident had been discussed on GL.iNet’s own forum, Hacker News and the Privacy Guides forum. We found no news coverage.
What GL.iNet Has Said
The notice is short. An “unauthorized party” exploited a vulnerability in GL.iNet’s “cloud remote management services” to access a subset of its routers and KVMs and install malicious software on them.
GL.iNet says it has closed the vulnerability, taken “corrective measures” on affected devices and started an investigation. That investigation includes “any potential impact on computers connected to affected KVM devices.” The company promises firmware with extra protections and an individual email to each affected customer, sent to the address on their cloud account, with guidance for their devices.
The notice doesn’t name the service, but the emails come from [email protected]. GoodCloud is GL.iNet’s cloud platform for managing routers; according to GL.iNet’s documentation, it lets you open a router’s admin panel and its SSH terminal from anywhere. KVMs use the same account system through glkvm.com.
The timeline so far, all on 21 November:
- 04:25 UTC: last update of the notice on GL.iNet’s site.
- 07:57 UTC: a GL.iNet staff member posts it on the company’s forum.
- By 10:37 UTC: owners post the email. The copy we’ve seen repeats the public notice word for word.
- 11:16 UTC: fixed KVM firmware appears on the forum as Google Drive links, then in GL.iNet’s download center as a beta around noon.
- 13:43 UTC: staff post a way to check a KVM for infection.
- 13:56 UTC: the same check follows for routers.
Nothing so far names the router models involved, gives a device count or says whether data was taken.
KVM Owners Now Have a Check and a Fix
GL.iNet’s check takes a minute. Open your KVM’s web console, go to Toolbox → Terminal → Access and run:
ps | grep tmp
If the output contains crond -i /tmp/.log, GL.iNet says the device “is under attack.” No output, or anything else, means it’s healthy. The staff post lists seven models.
The new firmware is labelled a beta. Its release note says it “strengthens the security of the cloud platform’s remote management service.” Unless you’ve joined the beta program, the KVM won’t offer it on its own: download it from the firmware download center and use Local Upgrade.
For an infected KVM, or one you’re unsure about, GL.iNet’s notice recommends a factory reset: hold the Reset button for about 10 seconds while the device is on, then set it up again. Then install the update.
The computer the KVM is plugged into needs a look too. GL.iNet suggests checking it for unfamiliar programs, browser extensions or user accounts, unexpected startup items or scheduled tasks, changed settings and unusual network traffic, and running a full scan with up-to-date security software. If anything looks off, change the passwords of accounts used on that computer and contact GL.iNet.
One detail is worth knowing even if your KVM is clean. GL.iNet’s own documentation says the KVM cloud service is enabled by default. If you never use remote access through GL.iNet’s cloud, turn it off under Cloud Service → gear icon → Disable. A cloud link that’s on before you ask for it is a strange default for a device that can type on your computer.
Router Owners Have a Check, but No Fix Yet
Routers got their own check at 13:56 UTC, and it’s the same one. Log in to the router over SSH, run ps | grep tmp, and look for crond -i /tmp/.log in the output. If you’d rather not use SSH, GL.iNet offers to review the router if you send [email protected] its model, MAC address, firmware version and an exported configuration backup. That backup holds your Wi-Fi password and VPN settings, so change them afterwards.
One owner asked straight away whether a clean result means the router isn’t compromised or only that the malware isn’t running right now. GL.iNet hadn’t answered when we published.
There’s no router firmware yet. The newest router builds in GL.iNet’s download system predate the notice. Its advice is a factory reset (hold Reset for 10 seconds after the router has fully started), setting the router up again, and installing the update once it’s out.
Other questions owners asked on the forum are still open. Were only routers bound to GoodCloud reachable, or only those with remote access switched on? Could the attacker read settings stored in the cloud, such as WireGuard server details? Is it safe to restore a configuration backup after the reset? At 13:46 UTC, one owner wondered whether routers had been targeted at all.
For VPN users, the stakes are specific. A router that runs your VPN holds the VPN keys or login, your Wi-Fi password and its own admin password. It also sees every device’s traffic before that traffic is encrypted and sent into the tunnel. Malware on that router doesn’t need to break your VPN; it sits in front of it.
Our comparison of a VPN on the router versus a VPN on each device explains what each setup protects.
What to Do Now
- Find out whether you use GL.iNet’s cloud. GL.iNet says the hole was in that service. Log in to goodcloud.xyz (routers) or glkvm.com (KVMs) and see whether your devices are bound there.
- KVM owners: run the check above, install firmware 1.10.2 (1.8.6 on the Comet Q), and reset the device if the check shows the infection or you can’t run it. Check the attached computer as GL.iNet describes. In a company network, treat a positive check as a security incident and involve whoever handles them.
- Router owners: run the check over SSH. If it finds the process, or your router is bound to GL.iNet’s cloud, reset it as GL.iNet advises and set it up from scratch. Don’t restore a backup made before the reset until GL.iNet says it’s safe. Choose a new admin password and a new Wi-Fi password while you’re at it.
- If the router runs a VPN client: create a new WireGuard configuration (or new OpenVPN credentials) in your VPN account and delete the old one, so keys copied from the router stop working.
- If you don’t need remote management, switch it off. On routers with firmware 4.7 or later, click the cloud icon in the top right of the admin panel, then the gear icon, then Disable.
- Watch for GL.iNet’s email and the router firmware. The company says affected customers get individual guidance; [email protected] will check a device on request. Open the admin panel yourself rather than through links in any email.
Owners Want More Than a Notice
GL.iNet’s forum thread on the notice passed 800 views in its first six hours. Most replies ask for the same things: affected models and firmware versions, a start date, signs of infection to look for, and whether a reset removes the malware.
“This vague notice is NOT the way to do things,” one owner wrote, asking GL.iNet to publish the root cause, detection steps and mitigations at once and to say whether it had registered a CVE. Another replied that CVEs are usually published after a fix is available. GL.iNet’s security page commits it to disclosing vulnerabilities within 90 days of discovery.
Two owners who checked their GoodCloud logs said the logs showed nothing before Saturday morning.
It isn’t the Comet’s first security problem this year. In an April advisory, GL.iNet fixed flaws found by Eclypsium, including one that let an attacker in the middle or a compromised update server swap the firmware and its MD5 hash and still pass verification.
Remote management is a fine convenience until somebody else does the managing.
We're Contacting GL.iNet
We’re asking GL.iNet how many devices were affected and which router models, when the attacks began, and whether only devices bound to its cloud or with remote access enabled were reachable. We’re also asking what the malware does, whether it collected passwords, VPN keys or traffic, whether it survives a reset or a firmware update, whether it reached computers attached to KVMs, when router firmware and a router check will follow, whether a CVE will be assigned, and which authorities it has notified.
We’ll update this article when GL.iNet replies.
Our Mission
We believe security online security matters and its our mission to make it a safer place.