A new Mirai botnet campaign is actively exploiting a high-severity remote command execution (RCE) vulnerability, CVE-2025-29635, in discontinued D-Link DIR-823X routers. Security researchers at Akamai detected the in-the-wild exploitation beginning in March 2026, over a year after the flaw was disclosed. Attackers are leveraging the vulnerability to download and execute a shell script (dlink.sh) from a malicious server (88.214.20.14), which then installs a Mirai variant called tuxnokill. The compromised routers are then added to a botnet controlled by a C2 server at 64.89.161.130:44300, ready to participate in distributed denial-of-service (DDoS) attacks. The affected routers reached their end-of-life (EoL) in November 2024, and D-Link has stated they will not be patched, underscoring the persistent threat of legacy IoT devices.
/goform/set_prohibiting endpoint on a vulnerable router.This type of vulnerability is common in embedded devices and is trivial to exploit once discovered. It allows the attacker to gain full control over the device's operating system.
The same threat actor was also observed exploiting other known vulnerabilities, including CVE-2023-1389 in TP-Link routers and an RCE in ZTE ZXV10 H108L routers, as part of a broader campaign to build their botnet.
Akamai's honeypot network confirmed active, in-the-wild exploitation of CVE-2025-29635 starting in early March 2026. This is the first observed mass exploitation of this specific flaw. The attack chain is simple and automated:
T1190 - Exploit Public-Facing Application) Upon finding a target, the attacker sends a malicious POST request to /goform/set_prohibiting to execute a command.T1105 - Ingress Tool Transfer) The injected command downloads the dlink.sh script from 88.214.20.14.tuxnokill Mirai variant.64.89.161.130:44300 to receive commands.The immediate impact is the compromise of the affected D-Link routers, adding them to a growing DDoS botnet. For the owners of these routers, this can result in poor network performance and their IP address being implicated in malicious activity. The broader impact is the increased availability of DDoS-for-hire services powered by this botnet. These attacks can be used to disrupt websites, online services, and corporate networks, leading to financial and reputational damage for the victims. This campaign is a classic example of how threat actors leverage a 'long tail' of unpatched, end-of-life IoT devices to build powerful and resilient botnets at a massive scale.
88.214.20.14dlink.sh script.64.89.161.1304430064.89.161.130.dlink.shtuxnokillThe following patterns may help identify vulnerable or compromised systems:
/goform/set_prohibiting88.214.20.14 or 64.89.161.130/goform/set_prohibiting URI path.Since the affected devices are end-of-life, no patch is available. The only effective remediation is removal and replacement.
The most effective mitigation is to physically remove and replace the end-of-life, vulnerable hardware.
Block inbound connections to the router's management interface from the internet. Also, block outbound connections to known malicious IPs.
Mapped D3FEND Techniques:
The core issue with the D-Link DIR-823X routers is that they are end-of-life and cannot be patched. Therefore, the only definitive platform hardening action is to decommission and replace them. Organizations and individuals must adopt a lifecycle management approach for IoT and networking hardware. Any device that is no longer supported by the manufacturer must be considered insecure and removed from the network. For any new router being deployed, the first step should be to change the default admin password and disable remote administration from the WAN interface. This simple step of hardening prevents a huge number of automated attacks that scan for default credentials and exposed management ports. In this specific case, since a patch for CVE-2025-29635 will never be released, replacement is the only viable long-term solution.
To prevent the exploitation of CVE-2025-29635 and similar vulnerabilities, organizations must implement strict inbound traffic filtering at the network edge. The web administration interface of a SOHO router should never be exposed to the public internet. Configure your perimeter firewall to block all inbound connections to the router's management port (typically 80/443) from any external IP address. If remote management is absolutely necessary, it should be restricted to a small set of trusted IP addresses (e.g., a corporate static IP) and ideally done over a VPN. For home users, this setting is often labeled 'Disable Remote Management' in the router's admin panel and should always be enabled. This single control would have prevented this Mirai campaign from successfully compromising these D-Link routers.
D-Link DIR-823X routers officially reach their end-of-life (EoL).
Akamai's honeypot network begins detecting active exploitation of CVE-2025-29635 in the wild.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats