Hackers exploit GL.iNet cloud flaw to infect routers and KVM devices
GL.iNet says attackers used a cloud vulnerability to infect some routers and KVM devices, leaving owners to check for malware and install security firmware.
GL.iNet says attackers exploited a vulnerability in its cloud remote-management services to install malware on some of the company's routers and KVM devices. The company says it has blocked the attack path, but devices already compromised will need checking and may require a firmware reinstall.12
What GL.iNet says happened
In a security notice dated November 20, GL.iNet said an unauthorised party used a vulnerability in its cloud services to access supported devices and install malicious software. The company said it fixed the vulnerability and blocked the access used in the incident, meaning devices can no longer be newly infected through that route.1
That does not clean devices that were already compromised. GL.iNet recommends that owners check running processes for the exact indicator `crond -i /tmp/.log`, then install the stable security firmware scheduled for November 22. The vendor says a factory reset can also address an infection, although it will erase the device's settings.1
The affected products include GL.iNet routers and KVM devices, which let customers remotely access and control computers. That makes this more serious than a routine router update: an infected KVM could provide a route towards the computer it manages. GL.iNet advises KVM owners to examine the connected computer as well, looking for unfamiliar programmes, browser extensions, accounts, scheduled tasks and unusual network activity.1
Malware found on infected devices
BleepingComputer reports that customers and researchers found custom malware, root-level reverse shells and persistence mechanisms on affected hardware. Its analysis of malicious scripts found device-specific payloads, modified startup files, injected SSH keys and attempts to hide network connections from administrators.2
Those findings do not prove that every reported infection came from the November attack. Researchers told BleepingComputer that some devices showed older backdoors, while GL.iNet continues to investigate the incident and says it plans to notify identified affected customers through their cloud-account email addresses.2
Owners who find signs of compromise should preserve evidence before resetting a device, avoid restoring a potentially infected configuration and rotate credentials or access keys that may have been exposed. GL.iNet also links to a community-developed detection and cleanup tool, but warns that no scanner can guarantee it will find every infection.1
Our opinion
The important distinction here is between blocking an attack path and removing an attacker who is already inside. GL.iNet's cloud fix should stop new infections through the disclosed route, but the company's own guidance makes clear that customers still have to investigate each device rather than assume a firmware update has solved everything.
For owners of travel routers and KVMs, the safest approach is to treat the incident as a potential endpoint compromise: check the device, preserve useful evidence, change exposed credentials and only then rebuild it from trusted firmware. The unusual breadth of the reported persistence techniques also argues against relying on a single process-name check as proof that a device is clean.
GL.iNet's stable firmware release is the immediate next step, but affected owners should follow the vendor's incident guidance rather than simply rebooting and returning the device to service.