The GL.iNet GoodCloud incident calls for checking each managed router and KVM before deciding whether cleanup is needed. GL.iNet says an unauthorized party exploited a cloud remote management vulnerability to install malware on some devices. The company says it closed that attack path, but the cloud fix does not remove malware already installed.
This playbook follows GL.iNet’s customer notice, issued November 20 and last updated November 21, 2026 UTC. The notice schedules stable security firmware for routers and KVMs on November 22; it does not confirm that those releases are available. Check the vendor’s current notice and download page for your exact model before planning an update.
Why This GL.iNet GoodCloud Incident Needs a Device Check
The reported entry point was GL.iNet’s cloud remote management service. GL.iNet says the attacker used the vulnerability to reach some routers and KVM devices, then installed malicious software. The company reports that it fixed the cloud flaw and blocked the access used in this incident.
That service change prevents new infections through the reported path, according to GL.iNet. It does not establish that a previously reached device is clean. The notice does not define the full affected model set, the attack window, or whether connected computers were affected. Keep those questions open during third-party risk management platform review of cloud-managed equipment.
- InventoryIdentify GL.iNet routers, KVMs, models, and cloud account owners.
- CheckFollow the vendor’s router or KVM process-view instructions.
- DecideTreat a matching process as infection; ask support when uncertain.
- CleanUse the vendor’s KVM beta or factory reset guidance as applicable.
- UpdateVerify and install stable security firmware for each model when available.
- ReviewCheck computers attached to infected KVMs and record the outcome.
Step 1: Inventory the Devices and Their Owners
List GL.iNet routers and KVMs that your team administers, including remote sites and spare units. Record each model, firmware version, cloud account owner, location, and the computer attached to each KVM. This inventory is our response recommendation; GL.iNet has not published a complete affected-device list in its notice.
Assign an operator who can access the local device interface and document the check result. Do not treat a missing customer email as a clean-device finding. GL.iNet says it will email customers it identifies as affected, but advises everyone to check and update without waiting.
Step 2: Check the Router or KVM Using GL.iNet’s Instructions
For a router, open its Admin Panel, then System → Advanced Settings and sign in to LuCI. In LuCI, open Status → Processes and compare running process details with the exact text in GL.iNet’s security notice. The vendor also provides an SSH option if the web interface is unavailable.
For a KVM, use Toolbox → Terminal → Access in the KVM web interface. Run the model-specific process command from the notice in the KVM terminal, not on its connected computer. GL.iNet distinguishes RMQ1 from other KVM models, so select the command for the device actually being checked.
Compare the full running-process entry with the vendor’s exact match, since the entry may contain additional text. A search command appearing by itself does not count as a match. Record which interface and model you used, when you checked, and whether the process was present.
Step 3: Make the Cleanup Decision from the Result
If the vendor’s process indicator appears, GL.iNet says to treat the device as infected. For an infected KVM, its model-specific security beta is available as an immediate option. The vendor also says a factory reset can address infection, while warning that it erases settings and requires setup again.
Preserve relevant configuration and incident records under your own response procedure before erasing a device. Review any backup before restoring it, so the reset does not silently reintroduce an unwanted setting. These preservation and backup checks are our response recommendations, not vendor claims about the malware’s persistence.
If the check completes without the indicator and there is no other reason to suspect infection, GL.iNet says no reset or other cleanup is needed. It still recommends the stable security firmware. If the check cannot be completed or its result is uncertain, contact GL.iNet support rather than labeling the device clean.
Brandefense Blackhole counted 10 dark-chat posts matching the broad term “GL.iNet” from August 24 through November 22, 2026. The measured unit is matching posts, not unique actors, devices, or incidents. That broad count cannot establish how many devices this GoodCloud incident affected or whether a given device was infected.
Step 4: Separate KVM Beta Builds from Stable Firmware
GL.iNet’s November 21 notice lists security beta builds for seven KVM models. Six models have version 1.10.2 beta or later: RM10, RM10RC, RM1, RM1V2, RM1PE, and RM4PE. RMQ1 has version 1.8.6 beta or later. These are KVM beta options for devices showing signs of infection, not a stable-router firmware list.
The same notice schedules stable security firmware for both product classes on November 22, 2026. A scheduled date is not release confirmation, so verify the current file and model on GL.iNet’s official download page. Install the stable security build for each model once available, even when its process check was negative.
After a beta installation or factory reset, GL.iNet still recommends the latest stable security firmware. Record the installed build and repeat the vendor’s device check when the device returns to service. The closed cloud path addresses the reported entry route; it does not replace cleanup of a device already infected.
Step 5: Review Connected Computers and Close the Record
If a KVM was infected, GL.iNet advises a precautionary check of its connected computer. Look for unfamiliar programs, browser extensions, accounts, startup items, scheduled tasks, or unusual settings and network activity. Run a full scan with current security software, and investigate findings through the organization’s normal incident response workflow.
GL.iNet says it is still investigating whether connected computers were affected. A clean computer scan cannot answer every question about an earlier access window. Record device status, firmware version, check evidence, connected-system review, owner, and unresolved questions in an incident response plan template.
Revisit the record when GL.iNet publishes model-specific stable releases or more precise scope information. Escalate a positive result or uncertain check to the vendor and your incident lead. Do not merge the vendor’s confirmed device infections with the still-open question of impact to connected computers.
Frequently Asked Questions
Does GL.iNet's cloud fix clean an infected router or KVM?
No. GL.iNet says its cloud fix blocks the reported attack path but does not remove malware already installed on a device.
Is a factory reset needed after a negative device check?
GL.iNet says no reset or other cleanup is needed when the check completes without the indicator and there is no other reason to suspect infection. Install stable security firmware when available.
Are GL.iNet's November 22 stable firmware builds already available?
The November 21 vendor notice schedules those builds for November 22 but does not confirm release. Verify the current official download for each model before updating.
