<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ddos — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/ddos/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 23 Apr 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/ddos/feed.xml" rel="self" type="application/rss+xml"/><item><title>Mirai Campaign Exploiting CVE-2025-29635 in D-Link Routers</title><link>https://feed.craftedsignal.io/briefs/2026-04-mirai-dlink-rce/</link><pubDate>Thu, 23 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-mirai-dlink-rce/</guid><description>A new Mirai-based malware campaign is exploiting CVE-2025-29635, a command-injection vulnerability affecting D-Link DIR-823X routers, to enlist devices into the botnet.</description><content:encoded><![CDATA[<p>A new Mirai-based malware campaign has been observed exploiting CVE-2025-29635, a high-severity command injection vulnerability affecting D-Link DIR-823X routers. Discovered by Akamai&rsquo;s SIRT in March 2026, the campaign involves attackers sending malicious POST requests to vulnerable D-Link routers to execute arbitrary commands. This vulnerability allows attackers to download and execute a shell script, ultimately leading to the deployment of Mirai-based malware. The affected D-Link routers reached end-of-life in November 2024, meaning a patch is unlikely. The same actor is also exploiting CVE-2023-1389 impacting TP-Link routers, and an RCE flaw in ZTE ZXV10 H108L routers, deploying the same Mirai payload.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker sends a POST request to the <code>/goform/set_prohibiting</code> endpoint on the D-Link DIR-823X router.</li>
<li>The POST request exploits CVE-2025-29635 to inject and execute arbitrary commands.</li>
<li>The injected commands change directories across writable paths on the router.</li>
<li>A shell script named <code>dlink.sh</code> is downloaded from an external IP address.</li>
<li>The <code>dlink.sh</code> script is executed on the compromised router.</li>
<li>The script installs a Mirai-based malware variant named &ldquo;tuxnokill&rdquo;.</li>
<li>&ldquo;tuxnokill&rdquo; establishes persistence and begins scanning for new targets.</li>
<li>The compromised device is then used to launch DDoS attacks, leveraging Mirai&rsquo;s standard capabilities, including TCP SYN/ACK/STOMP, UDP floods, and HTTP null attacks.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2025-29635 allows attackers to remotely execute arbitrary commands on vulnerable D-Link DIR-823X routers. The compromised routers are then incorporated into the Mirai botnet, increasing its size and DDoS capabilities. Given that these routers are end-of-life, many remain unpatched, potentially leading to a large number of compromised devices. This can result in network disruptions and service outages for targeted entities, as well as potential data exfiltration.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor network traffic for POST requests to the <code>/goform/set_prohibiting</code> endpoint on D-Link routers, as described in the Attack Chain, to detect potential exploitation attempts.</li>
<li>Deploy the Sigma rule <code>Detect Mirai dlink.sh Download</code> to identify attempts to download the malicious shell script.</li>
<li>If using affected D-Link DIR-823X routers, TP-Link, or ZTE ZXV10 H108L routers, upgrade to a supported device or implement network segmentation to limit potential damage.</li>
<li>Block the external IP address hosting the <code>dlink.sh</code> script if it can be reliably determined and is observed on your network.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>mirai</category><category>ddos</category><category>rce</category><category>iot</category></item><item><title>Disruption of Large IoT DDoS Botnets</title><link>https://feed.craftedsignal.io/briefs/2024-01-iot-ddos-disruption/</link><pubDate>Fri, 20 Mar 2026 05:50:09 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-iot-ddos-disruption/</guid><description>Law enforcement has disrupted significant IoT botnets responsible for launching record-breaking distributed denial-of-service (DDoS) attacks, impacting the availability of targeted systems.</description><content:encoded><![CDATA[<p>Authorities have dismantled a globally distributed network of compromised Internet of Things (IoT) devices that were being leveraged to conduct large-scale DDoS attacks. The botnets consisted of a large number of IoT devices. These attacks overwhelmed target systems, rendering them inaccessible. While the specific devices, malware, and attribution remain undisclosed in the provided source, the disruption of these botnets is a significant event for defenders, as it reduces the overall capacity for attackers to launch extremely large DDoS attacks. The botnets were responsible for record-breaking attacks.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Compromise IoT Devices: Attackers exploit vulnerabilities (e.g., default credentials, unpatched firmware) on IoT devices such as routers, cameras, and DVRs.</li>
<li>Install Malware: Malicious software specifically designed for the IoT architecture is installed on the compromised devices.</li>
<li>Botnet Formation: The malware turns the IoT devices into bots, which are controlled remotely by a command-and-control (C2) server.</li>
<li>C2 Communication: The bots maintain persistent communication with the C2 server, awaiting instructions for launching attacks.</li>
<li>DDoS Attack Initiation: The C2 server issues commands to the bots, instructing them to flood a target system with malicious traffic.</li>
<li>Traffic Amplification: The bots, now acting in unison, send high volumes of traffic to the target, overwhelming its resources.</li>
<li>Service Disruption: The target system becomes unavailable to legitimate users due to the sheer volume of malicious traffic.</li>
<li>Impact: Disruption of services for targeted organizations, potentially leading to financial losses and reputational damage.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The DDoS attacks launched by these IoT botnets caused significant service disruptions for targeted organizations. The scope of the attacks was described as &ldquo;record-breaking&rdquo;, suggesting a large number of victims and potential financial losses. Sectors affected are not detailed in the source, but DDoS attacks can impact any organization with an online presence. Successful attacks lead to website and application unavailability, impacting business operations and customer access.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor network traffic for unusual spikes in volume and traffic patterns indicative of DDoS attacks.</li>
<li>Implement rate limiting and traffic filtering on network infrastructure to mitigate the impact of DDoS attacks.</li>
<li>Although no specific IOCs are available, investigate any alerts related to high-volume network traffic originating from internal devices.</li>
<li>Enable logging on network devices to capture potential indicators of compromise and attack activity.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>iot</category><category>ddos</category><category>botnet</category><category>disruption</category></item></channel></rss>