GL.iNet GoodCloud router malware incident
Cloud management flaw pushed malware onto GL.iNet routers and remote-control KVMs
Posted · Spectrum Delta Research Team
Summary
An unattributed attacker exploited a flaw in GL.iNet's GoodCloud cloud remote management service to install malware on customers' routers and remote keyboard-video-mouse devices, the vendor confirms (A/2), with root reverse shells on routers verified by community device forensics (C/2). The vendor notice of 20 November says the attack path is blocked and fixed firmware shipped on 22 November, but only a factory reset clears installed malware. Verified forensics show the injected command appending a reverse-shell loop to an iptables rule built by the device's cloud client from unvalidated values, piping a root shell through a named pipe to nc at 170.39.226.219; on most enrolled routers the same channel ran a command searching for a KVM implant's folders and reported to that address. GL.iNet's infection indicator is a process running crond -i /tmp/.log, absent from the reverse-shell routers, and netstat may have been replaced so that running it starts the malware. The number of affected devices, the malware's purpose, any impact on computers attached to affected KVMs and the actor remain unknown.
Breakdown
Technical exposure
- GL.iNet router or KVM enrolled in GoodCloud remote management
- Router or KVM firmware without the 22 November security update
- Computer attached to an affected GL.iNet KVM device
Adversary
Unknown (unattributed) · GL.iNet security notice (A/2)
Procedures (3)
Cloud management command injects shell text through an iptables rule builder
Logs
- GoodCloud device log export (vendor cloud account) · command responses of the form {"id":1,"astrowarp":[],"code":0} on 20 November between about 20:46 and 21:31 UTC in the exported device log of a router that never used AstroWarp; the GoodCloud client gl-sdk4-cloud built an iptables rule for chain SDWAN_IP_MAPPING from unvalidated cloud-message values, and the code shipped from firmware 4.7.0
Router process list and syslog via SSH or the admin panel (OpenWrt) · sh -c iptables -t nat -A SDWAN_IP_MAPPING -d 127.0.0.1 -j DNAT --to-destination 127.0.0.1 followed by a reverse-shell loop using mkfifo /tmp/f and nc 170.39.226.219; remote syslog export or interactive SSH inspection required, traces disappear on reboot
Root reverse shell dials a rented server over netcat and retries
- T1095Non-Application Layer Protocol
Logs
- Router connection table and process list · ESTABLISHED connections held by nc to 170.39.226.219 on varying ports (42910, 43104, 43149, 42499 observed), started about 21:40 UTC on 20 November; the loop retries every few seconds when unreachable; the named pipe /tmp/f remains after the shell stops until reboot
- Perimeter firewall or netflow logs for the router uplink · outbound connections from the router to 170.39.226.219 or 170.39.226.0/24 on high ports during 20 to 22 November, repeated at short intervals from unreachable clients
Vendor-indicated implant process and a replaced netstat binary
- T1036.005Masquerading: Match Legitimate Resource Name or Location
Logs
- Router process list and binary inventory via SSH or the admin panel · a running process containing crond -i /tmp/.log (GL.iNet's stated infection indicator for the gl-helper implant, absent from routers that carried the reverse shell, so check for both) and a replaced /bin/netstat that is no longer a busybox link, where running netstat starts the malware
Indicators of compromise
IPs (1)
- 170.39.226.219reverse-shell destination and folder-check report address, Misaka Network rented server suspended by the provider on 21 November; hunt-only for retro-hunting 20 November onward, not forward blocking (RemoteToHome, assessed 2026-11-22)
Sources
- A/2GL.iNet: Security Notice 2026-11-20
- C/2RemoteToHome: GL.iNet security incident 2026 community findings
- B/3SecurityOnline: GL.iNet cloud zero-day exploited in the wild against routers and KVMs (retelling)
Grades are source reliability (A–F) and information credibility (1–6).
Questions, detections or sightings of GL.iNet GoodCloud router malware incident? Bring them to the community.