Every claim in this post is either a quotation from a named source with its date, or a measurement I took myself. Where something is not known, I say it is not known. Where a claim comes from a single forum user, I label it as such. Nothing here is speculation presented as fact.
What GL.iNet has confirmed, in their own words
GL.iNet staff posted the security notice on their official forum on November 20, 2026, last updated November 21. Verbatim from that notice:
On November 20, 2026, GL.iNet identified a vulnerability in its cloud remote management services. An unauthorized party exploited the vulnerability to access and install malicious software on some GL.iNet routers and KVM devices.
The attack path has been blocked. We fixed the cloud vulnerability and blocked the access used in this incident. Devices can no longer be newly infected through this attack path. These measures do not remove malware from devices that were already infected.
The notice tells owners to look for one exact string in the process list, crond -i /tmp/.log, in the router via SSH or LuCI, or in the KVM’s own terminal. If it is found: treat the device as infected, install the security beta or factory reset, and check the computer attached to a KVM for unfamiliar programs, extensions, accounts, startup items and scheduled tasks. If it is not found and nothing else is suspicious: no reset needed, but still install the stable security firmware when it arrives. KVM beta builds (1.10.2 for most models, 1.8.6 for the RMQ1) were posted the same day; stable builds for routers and KVMs were scheduled for November 22.
The community advisory: CSA-2026-01
While GL.iNet’s notice names no vulnerability class, no affected model list, and no CVE, a community project assigned its own ID, CSA-2026-01, and maintains an advisory page and triage script. The advisory’s own metadata, as I read it on November 22: CVE none assigned. Severity Critical, their rating, flagged on the page as the community’s own. Exploited: yes. Confirmed by GL.iNet, publicly. Fixed in: not released at time of writing. The same page carries this disclaimer, which is worth repeating: a clean result does not prove that a device is clean, and it does not replace a factory reset or GL.iNet’s security firmware.
The community check covers files beyond GL.iNet’s one process string, plus autostart entries, the firewall configuration, and overlay-storage traces. Its author (admon, on the GL.iNet forum, November 22) argues the vendor’s check misses a class of live compromise: an active remote shell leaves no file and no trace of that named process, and disappears after a restart. That is a community claim, not a verified one, but it is exactly why the advisory page tells you to run the script before rebooting, resetting or updating anything. Those actions wipe evidence. One development changes the standing of that script: BleepingComputer reports (Nov 22) that GL.iNet now links the community detection and cleanup tool in its own official support instructions for routers and KVMs, and asks owners who run it to submit the optional anonymous report. The community check is no longer unofficial advice. That request is also the caveat attached to every community percentage quoted below: those numbers measure who scanned and who reported, not the installed base. For reach, the vendor’s notice had drawn 331 comments on r/GlInet by the time I checked, shortly after 20:00 UTC on November 22.
One operational detail from the same page, which owners have independently confirmed: if your device is under GoodCloud management, export its cloud-side logs from your account before you change your cloud password. One owner reported the device log, which contained the attacker’s command, was gone after the password change.
What the attack is
Publicly established, across sources:
- GL.iNet confirms malware was installed on some routers and KVM devices through their cloud remote management service (forum notice, Nov 20).
- The marker process GL.iNet names is
crond -i /tmp/.log; the vendor’s own cleanup keys on marker files namedgl-helperandgbunder/etc/glinet/.cache/and/etc/config/.gl/(vendor and community sources agree on the paths). - Media coverage agrees on the confirmed core. heise online (Nov 22) and Borncity (Nov 21, Günter Born) both report: cloud flaw, exploitation by an unauthorized third party, malware on a subset of devices, vendor closed the path, patches scheduled Nov 22, factory reset or security firmware as remediation. EnosTech (Nov 22, Joe Edwards) adds that the exploit obtains root-level access on GoodCloud-connected devices and that no CVE had been assigned as of that article. BleepingComputer (Nov 22, Lawrence Abrams) corroborates the same core and published the malware analysis I summarize below; the same reporter covered it in a Lawrence Systems video titled after the finding that matters most: a factory reset may not fix it.
- The attacker infrastructure is at least partly gone: the forum coordinator rthco reported (thread post 70, November 21) that the abuse/takedown request against the reverse-shell VPS at 170.39.226.219 succeeded, with the hosting provider confirming the machine suspended and preserved for investigation. Community-side action, not a vendor announcement.
- The advisory page’s community data puts the start of exploitation around November 15. That is a community estimate from anonymous telemetry, not a vendor statement. The earliest dated public evidence with logs behind it is a forum owner’s record cited by BleepingComputer (Nov 22): a GL-RM1 KVM downloading an installer script from an external server on November 19. The same owner logged the device then contacting roughly 1,800 residential IP addresses a day and repeatedly hitting the TRON blockchain API. Both the owner and BleepingComputer state plainly that the purpose is unclear, and that nothing confirms a residential-proxy or botnet role.
One mechanism detail deserves every owner’s attention because it changes the advice. The Borncity article carries a reader report, and I found the same behavior on my own hardware: removing the device from your GoodCloud account does not stop the cloud client. On my router, and per the Borncity reader’s report, the gl-cloud process keeps its connection open to GL.iNet’s own cloud endpoint (the reader names 18.209.114.161:28883, which matches the endpoint my estate logs show for the same process). What stops it is disabling GoodCloud on the device: the switch in the admin panel, or stopping the client. The community advisory makes the same point in stronger terms: never having used the remote-access features does not protect you, because the cloud client code runs whenever the service runs. Verify the switch again after every firmware upgrade. The advisory page records one owner’s report of an online upgrade with settings kept silently re-enabling the cloud client and its remote access. That is a single report. The check costs two minutes, so make it.
What published analysis says the malware does
BleepingComputer obtained and analyzed copies of the attack tooling, and Lawrence Systems covered the same findings in his video. The technical substance, attributed throughout:
- The installer, named
ni.shin the forum evidence and examined by BleepingComputer (Nov 22), recognizes many GL.iNet models and downloads exactly the two payloads the vendor’s own cleanup keys on:gl-helperandgb. Persistence runs through startup scripts and scheduled tasks. - It disguises the malicious process as the very string GL.iNet tells customers to search for,
crond -i /tmp/.log. That is camouflage, not a signature. Its absence proves nothing, which is the sharpest published support for the community’s criticism of the one-line check. - It replaces the legitimate
netstatwith a wrapper that filters out the malware’s own connections. Triage on these devices should read connections from/proc/net/tcp, not from netstat. My sweep did exactly that before I saw this published, so it reads as confirmation of method rather than news. - It can install SSH public keys for standing remote access, and it stamps its files to imitate legitimate firmware dates. Two rules follow: never date an infection from modification times, and treat an unrecognized authorized-keys entry as active compromise, not an artifact.
- BleepingComputer separately examined a Lua payload from a GL-MT2500, launched through a modified
urandom_seedstartup script. That matches the older backdoor family described below rather than the November malware. Some recovered files carry December 2025 timestamps, so a few devices may have been hit for months. Whether the two campaigns share operators is not established.
What I found on my own network
I run GL.iNet hardware at three sites. On November 21 I swept every reachable device with a read-only check implementing the full published indicator set, on the devices themselves, before any reset or reboot. The numbers below are my measurements, not anyone else’s:
- Nine devices swept: six routers (a Flint 4, a Flint 3, a Flint 2, a Beryl 7 running as an access point, and two whose models I have not verified myself) and three Comet KVMs.
- Two Comet KVMs carried all four marker files, with identical binary hashes on both units. One payload set. These devices control physical machines over HDMI and USB.
- Analysis of the preserved binaries shows a lookalike command-and-control domain in the configuration (not GL.iNet’s real domain), polling for commands keyed to the device MAC. I am not republishing the malware’s config details here; get the indicator list from the advisory’s own source.
- Both infected KVMs were dormant at sweep time: no running process, no autostart reference I could find. Staged, not executing. Treated as fully compromised anyway, because that is the vendor’s own position on these markers.
- Every router came back clean that night on the full indicator set available at the time. That line has aged badly, and I am leaving it here deliberately, next to its replacement: within about thirty-six hours the community’s detection had improved, and the tally across my own estate grew to six KVM devices and five routers where the attack landed. The routers were not clean on November 21. The check was blind.
- One further KVM appliance in the estate was confirmed infected by its owner and taken offline the same evening.
Containment I ran myself: GoodCloud disabled on every router and every reachable KVM, using the device-side switch and not just removal from the cloud account, for the reason given above; the lookalike C2 domain blocked at the network resolver, with NXDOMAIN verified afterwards; evidence and hashes preserved off-device; no factory reset performed while evidence was still live. Then, later that evening, both infected Comets rebooted within 21 seconds of each other, firmware unchanged, and the marker files were gone from both when I re-checked, wiped from inside the overlay filesystem. I do not know what deleted them. It was not me and it was not a firmware update. If a device ever carried these markers, treat it as compromised regardless of what a later scan shows. That is also the vendor’s position.
The dispute about checking routers (why the forum thread is at 140 posts)
GL.iNet’s public check looks for crond -i /tmp/.log. On November 22, a frequent forum contributor (rthco) posted that this string is a KVM indicator only, that it appeared on not one compromised router in the community’s data, and that the vendor’s notice was therefore steering router owners to a check that clears infected devices. rthco put the community’s report-based compromise rate for GoodCloud-connected routers on firmware 4.7 and newer at roughly 95 percent, and asked GL.iNet staff directly to pull the check from the public notice.
I reported on November 21 that my own router sweep had come back clean on the extended indicator set, and I held that against rthco’s claim as an open contradiction. It resolved the way most such contradictions do when the data is still moving: the community’s detection kept improving over the following day, and my routers stopped looking clean. rthco was right, my earlier check was the false negative, and this post carries the correction rather than the original. What is certain from the public record, independent of any rate estimate, is this: GL.iNet confirms routers were targeted, and no publicly documented check reliably clears a router. If your router joined GoodCloud, the defensible reading of every source above is: assume exposure and act accordingly.
The other discovery: a backdoor with an older history
Separate from this incident, forum users report a different, older implant, most visibly a modified /bin/ulogd with changes to startup scripts, across several router models. File dates in user reports range from September 2025 into 2026. The community advisory documents these reports and attributes nothing: how it got onto the devices is not known, and the advisory explicitly flags them as user reports that GL.iNet’s notice does not mention. RemoteToHome, the firm behind much of the technical reporting, published fleet numbers through BleepingComputer (Nov 22): of 183 routers it owns or manages, 152 showed suspicious activity, 24 had running root-level reverse shells, 47 carried the older persistent backdoor, and 81 showed evidence that attacker-supplied commands had executed. The firm states its fleet may not be representative of other customers. Their published finding that root can write to the firmware image a factory reset restores from, on most routers they tested, is what moves the advice from reset to reflash. That is why several sources recommend reflashing from a file you downloaded yourself, with keep-settings off, over a plain reset, for any hit device. The advisory is equally clear that nobody has reported such a change on an actually-affected device: it is a reason to prefer the reflash, not a confirmed second compromise. And per forum user elvisimprsntr: files under /etc/kvmd/user/ on a KVM can survive firmware upgrades and resets. If you reflash, treat every preserved configuration file as untrusted.
Firmware status, checked directly on November 22
Rather than trusting any article’s snapshot, including this one, check the download center for your exact model. What I verified myself on November 22 (UTC), both before and after the evening’s moves:
- Comet PoE (GL-RM1PE): stable 1.10.3, dated 2026-11-22, listed. The November 22 schedule held.
- Comet Pro (GL-RM10): stable 1.10.3, dated 2026-11-22, listed.
- Flint 2 (GL-MT6000): stable 4.11.1, dated 2026-11-22, listed.
- For KVMs, the version to aim for, per the vendor guidance BleepingComputer relays (Nov 22): 1.10.3 or later for RM10, RM1, RM1V2, RM1PE and RM4PE; 1.10.3 beta or later for RM10RC; 1.8.7 or later for RMQ1. The download-center listings I checked myself for the RM1PE and RM10 carry exactly those stable numbers. One timing note: my checks ran on the scheduled release day itself, late in UTC. Model pages can gain builds over the following hours, so re-check rather than trusting anyone’s snapshot, including mine.
- And the finding that shows exactly why per-model checking matters, live at my desk: my first pass on the Flint 4 (GL-BE14000) stable page shortly after 19:00 UTC showed nothing newer than 4.9.2 from September. A re-check around 20:40, while this post was being written, listed 4.9.3, dated 2026-11-23, built the 22nd. The page had changed inside ninety minutes. The Flint 3 (GL-BE9300), re-checked at the same moment, still showed nothing newer than 4.10.1 from September. That is the model-by-model rollout staff described on the forum, happening in real time. If your model is still waiting, staying off GoodCloud until it lands is the mitigation every source agrees on. And the lesson of my own ninety-minute window: any statement in this post about which builds exist is a timestamp, not a fact.
The sequence that every source converges on
- Check before you touch. Run the extended check (at minimum, the process string) before any reboot, reset or update. A restart clears the one artifact GL.iNet tells you to look for.
- Preserve first. Export GoodCloud logs from the cloud account before changing any password. In a business or insured environment, the forum advice is unanimous and matches every professional source cited here: talk to your insurer or incident-response provider before you reset anything.
- Disable the client, not just the account. GoodCloud off on the device itself. Then verify the connection is actually gone by watching your firewall or connection table, because removing the device from the account does not stop the client. My logs and the Borncity reader’s agree independently.
- If infected: reflash or replace. Factory reset is the vendor minimum. Better: reflash with a file you downloaded yourself, settings not kept, and rebuild the config by hand. Rotate everything the device knew: a root shell had access to VPN profiles, keys and passwords. Take the keys back at the other end too, on the VPN server and every machine that trusted the device’s SSH key.
- KVM owners: the attached computer is in scope. The vendor says so in the notice. Check the machine the KVM controls for programs, extensions, accounts, startup items and scheduled tasks you do not recognize, and scan it.
- Re-verify after every firmware change. Cloud client still off, firewall still yours. The one silent re-enable report is enough reason for a two-minute check.
What nobody has answered yet
- How the cloud vulnerability works, or did. No CVE is assigned and GL.iNet has published no technical details. RemoteToHome has a concrete hypothesis, reported by BleepingComputer (Nov 22): a command-injection flaw in the GoodCloud client’s AstroWarp/SD-WAN handler, which passes cloud-supplied values into shell commands executed as root without validating them. GL.iNet has neither confirmed that vulnerability nor linked it to this incident, so it stands as the best public answer to the how, and still a hypothesis.
- The mechanism behind the older, separate backdoor described in user reports. Unknown, as far as the public record shows.
- GL.iNet’s own timeline for when exploitation began, and the total affected count. The community’s around-November-15 estimate is the best public number, with the limits I noted.
- Whether account or personal data beyond the devices was exposed. The GL.iNet notice does not address it; EnosTech reported no confirmed data leak as of its article; BleepingComputer states (Nov 22) that GL.iNet has not disclosed how many customers were impacted or whether information was taken.
- The dispute over the router check. rthco’s claim, the community reports and GL.iNet’s notice cannot all be right. I re-read the whole 140-post forum thread shortly before 21:00 UTC on November 22: posts after rthco’s are from other community members. No staff answer yet.
How to check your device, and how to clean it
The community has stepped up and published a detection and cleanup script here. Please make sure to submit your reports at the end of the script. The info you submit goes into a repo where these developers can continue to update the detection and removal scripts.
Sources
Each claim above is attributed in place to one of these. Retrieved and re-checked November 22, 2026 (UTC):
- GL.iNet official forum, security notice posted by staff: 2026-11-20: GL.iNet Security Notice, GoodCloud / KVM / Routers
- Community advisory CSA-2026-01 (independent project, not affiliated with GL.iNet): CSA-2026-01 advisory
- Community triage script: admonstrator/glinet-csa-2026-01 on GitHub
- GL.iNet firmware download center, per-model stable lists: dl.gl-inet.com
- heise online: GL.iNet: Schwachstelle entdeckt, Patch verfügbar
- Borncity, Günter Born: GL.iNet-Sicherheitsvorfall bei Cloud-Fernverwaltung
- EnosTech, Joe Edwards: GL.iNet vulnerability discovered on routers and KVMs
- BleepingComputer, Lawrence Abrams: Hackers exploit GL.iNet cloud flaw to infect routers, KVM devices
- Lawrence Systems, forum post with video: GL.iNet GoodCloud Was Compromised. A Factory Reset May Not Fix It.
- The vendor notice as the community spread it: r/GlInet, GL.iNet Security Notice 2026-11-20
How this post was checked, and what is deliberately left out
Vendor statements here are quoted or cited from GL.iNet staff posts with dates attached. Community claims are named to their author and marked as community claims. My own numbers come from read-only scans of devices I own, taken before any remediation changed them. No device hostname, LAN address, or account identifier from my network appears in this post. The malware’s indicator specifics (paths, hashes, addresses) are summarized behaviorally on BleepingComputer’s analysis and otherwise left to the sources that maintain the live lists; a stale copy here would be worse than none. If you found your own evidence that contradicts anything above, the forum thread is where the conversation is actually happening.
By reading and using the information on this site you accept the terms of this blog: WickedYoda.com and associated TOS / policy. Views are my own; sources belong to their authors and are linked above.