RondoDoX Botnet Weaponizes React2Shell
A persistent nine-month RondoDoX botnet campaign has been targeting IoT devices and web applications. The threat actors have recently shifted to weaponizing a critical Next.js vulnerability, deploying malicious payloads like 'React2Shell' and cryptominers. The campaign, spanning from March to December 2025, shows quick adaptation to latest attack trends. The activity is divided into three phases: initial reconnaissance, web application exploitation, and IoT botnet deployment. The attackers have been using multiple command and control servers and deploying various malware variants. The campaign has intensified in December 2025 with a focus on Next.js exploitation. The impact includes widespread IoT device compromise, Next.js application risks, credential harvesting, and persistent multi-architecture threats.
AI Analysis
Technical Summary
The RondoDoX botnet campaign is a sophisticated, persistent threat active over nine months in 2025, targeting both IoT devices and web applications built on Next.js, a widely used React framework for server-side rendering. The campaign exploits a critical vulnerability dubbed React2Shell, which allows remote code execution on vulnerable Next.js servers. The attack unfolds in three distinct phases: initial reconnaissance to identify vulnerable targets, exploitation of Next.js web applications to deploy malicious payloads such as React2Shell and cryptominers, and finally the deployment of a botnet composed of compromised IoT devices. The attackers operate multiple command and control servers to manage infected devices and deploy various malware variants, including multi-architecture threats that complicate detection and remediation. The botnet leverages compromised IoT devices to increase attack scale and persistence, enabling credential harvesting and lateral movement within networks. Despite no official CVE or patch availability, the threat actors exploit publicly known weaknesses in Next.js applications, which are prevalent in modern web development. The campaign's use of IoT devices expands the attack surface and challenges mitigation due to the diversity and often weak security of IoT ecosystems. The campaign intensified in December 2025, demonstrating rapid adaptation to emerging vulnerabilities and attack trends, underscoring the operational sophistication of the RondoDoX adversary.
Potential Impact
European organizations face significant risks from this campaign, especially those deploying Next.js for web applications and relying on IoT devices in critical infrastructure. Unauthorized code execution on Next.js servers can lead to data theft, service disruption, and unauthorized access to sensitive information. The compromise of IoT devices facilitates large-scale botnet formation, enabling distributed denial-of-service (DDoS) attacks, cryptomining operations that degrade device performance, and further lateral movement within networks. Credential harvesting threatens both user and administrative accounts, increasing the risk of broader network compromise. The persistence of multi-architecture malware complicates detection and remediation efforts, potentially leading to prolonged exposure. Sectors such as manufacturing, healthcare, and smart city deployments, which heavily utilize IoT devices, are particularly vulnerable. The campaign’s rapid adaptation to new vulnerabilities increases the likelihood of sustained exploitation within European networks, potentially impacting confidentiality, integrity, and availability of critical services.
Mitigation Recommendations
European organizations should immediately conduct comprehensive security assessments of all Next.js web applications to identify and remediate vulnerabilities, even in the absence of official patches. Deploy runtime application self-protection (RASP) and web application firewalls (WAF) with updated signatures specifically targeting React2Shell exploitation attempts. Implement strict network segmentation to isolate IoT devices from corporate and critical infrastructure networks, minimizing lateral movement opportunities. Enforce strong access controls and multi-factor authentication (MFA) on all administrative and user accounts to protect credentials. Regularly update and patch IoT device firmware where possible, and replace unsupported or insecure devices to reduce attack surface. Deploy advanced network monitoring and anomaly detection solutions to identify unusual traffic patterns indicative of botnet activity or cryptomining. Utilize threat intelligence feeds to block known malicious IP addresses and file hashes associated with RondoDoX. Conduct targeted employee awareness training focused on recognizing suspicious activity related to web applications and IoT devices. Finally, develop and regularly test incident response plans tailored to botnet and web application exploitation scenarios to ensure rapid containment and recovery.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden
Indicators of Compromise
- ip: 38.59.219.27
- hash: 3ba4d5e0cf0557f03ee5a97a2de56511
- hash: c798b4bcf337d1c7420871b9a4f55fa8
- hash: ca5515cb5a378bf71c5bef02184b083c126786b7
- hash: dc057522e04f37a6143cf6ce9b5d4a19aab8ef7a
- hash: 50be5257678412f0810d46e0b0bc573eb65c6ce4617346c1527ff0dc9b7fc79e
- hash: 858874057e3df990ccd7958a38936545938630410bde0c0c4b116f92733b1ddb
- hash: 895f8dff9cd26424b691a401c92fa7745e693275c38caf6a6aff277eadf2a70b
- hash: 8e0bc23a87d349e5a5356252ce17576093b7858fdf6ea84919fbdcb2e117168e
- ip: 70.184.13.47
- ip: 89.144.31.18
RondoDoX Botnet Weaponizes React2Shell
Description
A persistent nine-month RondoDoX botnet campaign has been targeting IoT devices and web applications. The threat actors have recently shifted to weaponizing a critical Next.js vulnerability, deploying malicious payloads like 'React2Shell' and cryptominers. The campaign, spanning from March to December 2025, shows quick adaptation to latest attack trends. The activity is divided into three phases: initial reconnaissance, web application exploitation, and IoT botnet deployment. The attackers have been using multiple command and control servers and deploying various malware variants. The campaign has intensified in December 2025 with a focus on Next.js exploitation. The impact includes widespread IoT device compromise, Next.js application risks, credential harvesting, and persistent multi-architecture threats.
AI-Powered Analysis
Technical Analysis
The RondoDoX botnet campaign is a sophisticated, persistent threat active over nine months in 2025, targeting both IoT devices and web applications built on Next.js, a widely used React framework for server-side rendering. The campaign exploits a critical vulnerability dubbed React2Shell, which allows remote code execution on vulnerable Next.js servers. The attack unfolds in three distinct phases: initial reconnaissance to identify vulnerable targets, exploitation of Next.js web applications to deploy malicious payloads such as React2Shell and cryptominers, and finally the deployment of a botnet composed of compromised IoT devices. The attackers operate multiple command and control servers to manage infected devices and deploy various malware variants, including multi-architecture threats that complicate detection and remediation. The botnet leverages compromised IoT devices to increase attack scale and persistence, enabling credential harvesting and lateral movement within networks. Despite no official CVE or patch availability, the threat actors exploit publicly known weaknesses in Next.js applications, which are prevalent in modern web development. The campaign's use of IoT devices expands the attack surface and challenges mitigation due to the diversity and often weak security of IoT ecosystems. The campaign intensified in December 2025, demonstrating rapid adaptation to emerging vulnerabilities and attack trends, underscoring the operational sophistication of the RondoDoX adversary.
Potential Impact
European organizations face significant risks from this campaign, especially those deploying Next.js for web applications and relying on IoT devices in critical infrastructure. Unauthorized code execution on Next.js servers can lead to data theft, service disruption, and unauthorized access to sensitive information. The compromise of IoT devices facilitates large-scale botnet formation, enabling distributed denial-of-service (DDoS) attacks, cryptomining operations that degrade device performance, and further lateral movement within networks. Credential harvesting threatens both user and administrative accounts, increasing the risk of broader network compromise. The persistence of multi-architecture malware complicates detection and remediation efforts, potentially leading to prolonged exposure. Sectors such as manufacturing, healthcare, and smart city deployments, which heavily utilize IoT devices, are particularly vulnerable. The campaign’s rapid adaptation to new vulnerabilities increases the likelihood of sustained exploitation within European networks, potentially impacting confidentiality, integrity, and availability of critical services.
Mitigation Recommendations
European organizations should immediately conduct comprehensive security assessments of all Next.js web applications to identify and remediate vulnerabilities, even in the absence of official patches. Deploy runtime application self-protection (RASP) and web application firewalls (WAF) with updated signatures specifically targeting React2Shell exploitation attempts. Implement strict network segmentation to isolate IoT devices from corporate and critical infrastructure networks, minimizing lateral movement opportunities. Enforce strong access controls and multi-factor authentication (MFA) on all administrative and user accounts to protect credentials. Regularly update and patch IoT device firmware where possible, and replace unsupported or insecure devices to reduce attack surface. Deploy advanced network monitoring and anomaly detection solutions to identify unusual traffic patterns indicative of botnet activity or cryptomining. Utilize threat intelligence feeds to block known malicious IP addresses and file hashes associated with RondoDoX. Conduct targeted employee awareness training focused on recognizing suspicious activity related to web applications and IoT devices. Finally, develop and regularly test incident response plans tailored to botnet and web application exploitation scenarios to ensure rapid containment and recovery.
Affected Countries
Technical Details
- Author
- AlienVault
- Tlp
- white
- References
- ["https://www.cloudsek.com/blog/rondodox-botnet-weaponizes-react2shell"]
- Adversary
- RondoDoX
- Pulse Id
- 6952dc1e4da675337033a2e2
- Threat Score
- null
Indicators of Compromise
Ip
| Value | Description | Copy |
|---|---|---|
ip38.59.219.27 | — | |
ip70.184.13.47 | — | |
ip89.144.31.18 | — |
Hash
| Value | Description | Copy |
|---|---|---|
hash3ba4d5e0cf0557f03ee5a97a2de56511 | — | |
hashc798b4bcf337d1c7420871b9a4f55fa8 | — | |
hashca5515cb5a378bf71c5bef02184b083c126786b7 | — | |
hashdc057522e04f37a6143cf6ce9b5d4a19aab8ef7a | — | |
hash50be5257678412f0810d46e0b0bc573eb65c6ce4617346c1527ff0dc9b7fc79e | — | |
hash858874057e3df990ccd7958a38936545938630410bde0c0c4b116f92733b1ddb | — | |
hash895f8dff9cd26424b691a401c92fa7745e693275c38caf6a6aff277eadf2a70b | — | |
hash8e0bc23a87d349e5a5356252ce17576093b7858fdf6ea84919fbdcb2e117168e | — |
Threat ID: 69544fc0db813ff03e2ae6ff
Added to database: 12/30/2025, 10:18:40 PM
Last enriched: 1/28/2026, 7:05:50 PM
Last updated: 2/7/2026, 12:37:10 PM
Views: 136
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
Technical Analysis of Marco Stealer
MediumNew Clickfix variant 'CrashFix' deploying Python Remote Access Trojan
MediumKnife Cutting the Edge: Disclosing a China-nexus gateway-monitoring AitM framework
MediumThey Got In Through SonicWall. Then They Tried to Kill Every Security Tool
MediumHundreds of Malicious Crypto Trading Add-Ons Found in Moltbot/OpenClaw
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.