Video summary
Secret backdoor in popular router
Main summary
Key takeaways
Tech concepts & what the video investigates
- Embedded networking devices are implicitly trusted, but that trust can be exploited via hidden software backdoors.
- The video compares backdoor types:
- Predictable “hardcoded” root credentials, such as passwords derived from a static string plus the device MAC address, which can be used to access the router after authentication.
- A more severe case: a remote-management backdoor that phones home to a hard-coded external IP and enables arbitrary command execution.
Product / vulnerability details (ZBT-Link “AX3000” class router)
- The router firmware is based on OpenWrt, but the manufacturer adds malware on top of OpenWrt rather than shipping clean OpenWrt.
- The malware uses process masquerade:
- A userland process is named to resemble a Linux kernel thread—a “kworker”-style masquerade using bracketed/kernel-thread-like appearance.
- The disguised process ultimately runs as root.
- Core backdoor behavior:
- The “kworker” (masquerading process) beacons/calls out to a hard-coded IP address on Alibaba Cloud (and possibly other infrastructure).
- The external host at that IP can then run arbitrary commands on the device (effectively a remote shell/command execution channel).
- Manufacturer response (as described in the video):
- After the issue was publicized (referenced by a vulncheck article dated Aug 5), the manufacturer disabled firmware downloads by taking down their CDN.
- The video author still obtained firmware via a Shopify front-end link and reverse engineered it.
- The manufacturer claimed the functionality is an after-sales technical support tool, allegedly used only with customer authorization—though the video frames the “always-on beacon” behavior as suspicious.
How the tutorial / research was done (reverse engineering workflow)
- Firmware acquisition bypass despite download removal from the official site.
- Binwalk analysis of firmware images:
- Detects signatures/filesystems
- Performs recursive extract to unpack nested components
- The extracted filesystem typically includes common embedded formats such as:
- squashfs or jffs2
- Searching within the extracted filesystem:
- Locate strings/process names like “kworker”
- Inspect init scripts (e.g., under
init.d) to determine how the disguised process is started/killed - Run
stringson embedded binaries to identify the relevant component as RCTL/RCTLD-related
- The backdoor’s behavior is described as following a server-client design:
- The router-side component can list connected clients
- It can enable a remote bash shell to a specific target client/device
- Extracted configuration reveals:
- Which WAN interface is used
- The hard-coded remote destination (“phone home” target)
Evidence of broader “campaign” / trust-building concerns (non-technical but relevant)
- The video author suggests the vendor’s branding/presence (e.g., Instagram content about routers, drones, travel/camping) may function as a trust-building strategy that could mask distribution of insecure devices over time.
- The author urges viewers to stop buying routers from Amazon (their recommendation).
Named external references / review-like sources
- vulncheck article (cited as Aug 5 in the narration)
- Jacob Blains, credited as the author of the vulncheck article
- The video author references additional research/findings about other backdoors, including:
- “Endlessdoors implant”
- “Dark Lantern”
- (These are described as related to other work on Amazon routers.)
Main speakers / sources
- Primary speaker: the YouTube narrator/security researcher (no specific name given in the subtitles)
- Referenced source: Jacob Blains (author of the vulncheck article)
- Referenced researcher/context: why you Sunjae (GitHub repo author whose RCTL-related repo is said to have been deleted)