RondoDox Botnet Exploits React2Shell to Widen IoT Infections

RondoDox campaign weaponizes React2Shell to recruit 90,300 web apps and IoT devices—dropping miners, loaders and Mirai; patch Next.js and segment IoT.

  • A persistent nine-month campaign enrolled IoT devices and web apps into the RondoDox botnet using multiple vulnerabilities, including React2Shell (CVE-2025-55182).
  • About 90,300 vulnerable instances remain exposed globally, with 68,400 in the U.S.
  • The campaign used staged activity—reconnaissance, mass probing, and large-scale hourly deployment—and dropped miners, loaders, and a Mirai variant.
  • Defenses include patching Next.js, isolating IoT devices, deploying WAFs, monitoring processes, and blocking known C2 infrastructure.

Cybersecurity teams disclosed a nine-month campaign that recruited Internet of Things devices and web applications into the RondoDox botnet through late 2025. The activity used the critical React2Shell vulnerability (CVE-2025-55182) to gain remote code execution on exposed servers, CloudSEK said. The campaign also added older N-day flaws such as CVE-2023-1389 and CVE-2025-24893.

- Advertisement -

Data from the Shadowserver Foundation show roughly 90,300 instances vulnerable as of December 31, 2025, with 68,400 located in the U.S. Germany, France, and India followed in count.

Researchers mapped three phases of the campaign: March–April 2025 reconnaissance and manual scans; April–June daily mass probing of web apps (WordPress, Drupal, Struts2) and IoT devices like Wavlink routers; and July–early December large-scale automated hourly deployment. The abuse of React2Shell was previously flagged by Darktrace here and noted by other security firms.

In December 2025 infections, actors scanned for vulnerable Next.js servers and attempted to drop cryptocurrency miners and bot components at paths such as "/nuts/poop", "/nuts/bolts", and "/nuts/x86". The "/nuts/bolts" tool removes competing Malware and miners, clears prior campaign artifacts, and installs persistence via "/etc/crontab". As described by CloudSEK, "It continuously scans /proc to enumerate running executables and kills non-whitelisted processes every ~45 seconds, effectively preventing reinfection by rival actors."

Recommended mitigations include updating Next.js to patched versions, segmenting IoT devices into dedicated VLANs, deploying Web Application Firewalls, monitoring for suspicious process execution, and blocking known command-and-control infrastructure.

- Advertisement -

✅ Follow BITNEWSBOT on Telegram, Facebook, LinkedIn, X.com, and Google News for instant updates.

Previous Articles:

- Advertisement -

Latest News

AI Giants Pledge to Pay for Power Grid Strain

Seven top AI firms, including Amazon, Google, and OpenAI, have signed a White House...

X Money Launches Beta with 6% Yield, Shatner Joins

X Money has begun external beta testing, offering users cashback and a 6% annual...

Trump Backs Crypto Act, Citing ‘Meaningful Support’

Analysts from Clear Street suggest the crypto market may be at an inflection point,...

Bitcoin Tops Gold, Oil Amid Iran War Shock

Bitcoin (BTC) surged 12.1% to $73,419 since the U.S.-Israeli military action against Iran began...

Crypto Gains Stall as Bears, Struggling Miners Weigh

Derivatives and onchain data show a lack of bullish conviction, as 43% of Bitcoin...

Must Read

This is How to Buy and Sell Bitcoin

Now more than ever, there are a variety of ways to enter and exit the crypto market. While this is good, the availability of...
🔥 #AD Get 20% OFF any new 12 month hosting plan from Hostinger. Click here!