


Perceptive Security
SOC/SIEM Consultancy

RustDuck Botnet Rebuilds in Rust to Hijack Routers and Servers for DDoS
Published:
30 juni 2026 om 17:45:25
Alert date:
30 juni 2026 om 19:01:30
Source:
thehackernews.com
Mobile & IoT, Network Infrastructure, Ransomware & Malware, Web Technologies
RustDuck is a newly identified two-stage malware family targeting home routers, IP cameras, Android boxes, and poorly secured servers. Researchers at QiAnXin's XLab have been tracking the botnet since February 2026. The malware is written in Rust and is designed to recruit compromised devices into a botnet used for DDoS attacks. The campaign's primary goal is to knock websites and online services offline. What distinguishes RustDuck is not its current scale but the rapid pace at which it is evolving. The botnet represents a growing trend of malware authors leveraging Rust for its performance and evasion advantages. The threat affects a broad range of consumer and enterprise-grade network-connected devices.
Technical details
RustDuck is a two-stage malware botnet first tracked by QiAnXin XLab in February 2026. It targets home routers, IP cameras, Android boxes, and poorly secured servers, recruiting them into a DDoS botnet. Stage 1 is a small loader that decrypts and unpacks a heavier core module (Stage 2). The core module is actively being rewritten from C to Rust, making reverse engineering more difficult. Infection vectors include: brute-forcing weak/default credentials on Telnet and SSH; exploiting unpatched vulnerabilities in devices from TVT, Ruijie, TP-Link, ZTE, Huawei, D-Link, and Totolink; targeting exposed Android Debug Bridge (ADB) interfaces; and exploiting vulnerabilities in web software including ThinkPHP, Jenkins, and Hadoop YARN. The malware employs extensive anti-analysis checks before executing, including: detecting analysis tools (Wireshark, gdb), checking for attached debuggers, fingerprinting honeypot environments, detecting virtual machine hardware, probing reserved internet addresses that should never respond, and comparing system clocks to detect sandbox time acceleration. If the risk score from these checks exceeds a threshold, the malware erases traces and exits. Command-and-control (C2) communications are encrypted using ChaCha20-Poly1305 for the handshake and AES-GCM for command traffic, with keys derived via HKDF-SHA256 and Curve25519 key exchange, rotated every 10 minutes, and disguised as normal HTTPS traffic. C2 infrastructure leverages free dynamic-DNS services, notably duckdns.org. Supported C2 commands include: start attack, stop attack, report status, switch C2 servers, and upgrade malware. More than 20 IP addresses were observed distributing the malware, with 176.65.139[.]204 being the most active. This IP shares a subnet with infrastructure linked to a separate ADB-targeting DDoS botnet reported in spring 2026.
Mitigation steps:
1. Remove remote management interfaces (ADB, Telnet, SSH) from public internet exposure; disable them where not needed and never leave them accessible with default or weak passwords. 2. Apply all available patches for affected software: upgrade Apache CouchDB to a fixed release. 3. Replace unsupported/end-of-life hardware that cannot be patched, including D-Link DIR-823X (CISA advises decommissioning) and Totolink X6000R (vendor has not issued a patch). 4. Update firmware on TVT, Ruijie, TP-Link, and ZTE devices to the latest available versions. 5. Patch ThinkPHP, Jenkins, and Hadoop YARN deployments against known vulnerabilities and avoid exposing them to the public internet unnecessarily. 6. Ingest known indicators of compromise (file hashes, C2 domains, and source IP addresses from XLab's report) into security monitoring and firewall block lists. 7. Monitor for unusual outbound traffic patterns consistent with DDoS participation or C2 communication (encrypted traffic mimicking HTTPS from IoT/router devices). 8. Audit and secure all ADB interfaces on Android-based devices; disable ADB over network where not required.
Affected products:
Huawei HG532 routers (CVE-2017-17215)
D-Link DIR-823X routers (CVE-2025-29635
discontinued/end-of-life)
Totolink X6000R routers (CVE-2024-1781)
Apache CouchDB (CVE-2018-8007)
TVT DVRs and cameras
Ruijie network devices
TP-Link devices
ZTE devices
Android-based devices with exposed ADB interfaces
Android boxes
IP cameras
ThinkPHP (web framework)
Jenkins (CI/CD server)
Hadoop YARN
Related links:
https://blog.xlab.qianxin.com/rustduck-en/
https://nvd.nist.gov/vuln/detail/CVE-2017-17215
https://www.akamai.com/blog/security-research/cve-2025-29635-mirai-campaign-targets-d-link-devices
https://thehackernews.com/2026/04/cisa-adds-4-exploited-flaws-to-kev-sets.html
https://nvd.nist.gov/vuln/detail/CVE-2024-1781
https://docs.couchdb.org/en/stable/cve/2018-8007.html
https://www.fortinet.com/blog/threat-research/new-rust-botnet-rustobot-is-routed-via-routers
https://thehackernews.com/2026/03/doj-disrupts-3-million-device-iot.html
https://thehackernews.com/2026/05/mirai-based-xlabsv1-botnet-exploits-adb.html
Related CVE's:
Related threat actors:
IOC's:
176.65.139[.]204 (primary malware distribution IP), duckdns.org (dynamic DNS service used for C2 domains), File hashes: listed in XLab report at https://blog.xlab.qianxin.com/rustduck-en/, Control domains: listed in XLab report at https://blog.xlab.qianxin.com/rustduck-en/, Source addresses: listed in XLab report at https://blog.xlab.qianxin.com/rustduck-en/
This article was created with the assistance of AI technology by Perceptive.
