Exploitation of React2Shell Vulnerability (CVE-2025-55182) in IoT and Web Applications
A critical security vulnerability, React2Shell (CVE-2025-55182), affecting React Server Components and Next.js, has been widely exploited by both state-sponsored and criminal threat actors. The flaw enables unauthenticated remote code execution, making it a prime target for ransomware groups, botnet operators, and espionage campaigns throughout 2025. Notably, the RondoDox botnet leveraged this vulnerability in a persistent nine-month campaign to compromise IoT devices and web applications, enrolling tens of thousands of systems into its network. According to Shadowserver Foundation data, over 84,000 instances remained vulnerable as of early January 2026, with the majority located in the United States.
PolySwarm's annual review highlights React2Shell as the year's most significant exploit, noting its rapid weaponization by both nation-state actors and cybercriminals. Ransomware groups such as Cl0p and Qilin used zero-day exploits, including React2Shell, to target enterprises, government, and healthcare sectors. The widespread abuse of this vulnerability underscores the urgent need for organizations to patch affected systems and monitor for signs of compromise, as attackers continue to exploit trusted software components for initial access and lateral movement.
Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
3 events from the most recent confirmed update back to the earliest known activity.
Large-scale React2Shell exploitation reaches 8.1 million attack sessions
By early January 2026, researchers reported more than 8.1 million attack sessions targeting React2Shell since disclosure. The campaign used over 8,000 source IPs across 101 countries, with heavy use of cloud infrastructure and evasion techniques such as AMSI bypass.
React2Shell rapidly weaponized by state and criminal actors
Following disclosure, both state-sponsored and criminal threat actors began weaponizing React2Shell for real-world attacks. The vulnerability became a major driver of exploitation activity during 2025.
React2Shell vulnerability disclosed in React/Next.js apps
The critical React2Shell flaw, tracked as CVE-2025-55182, was disclosed in 2025 as an unauthenticated remote code execution vulnerability affecting React/Next.js applications. It was identified as one of the year's most impactful vulnerabilities.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
2 references tracked. Mallory keeps watching after this page renders.
See the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Related stories
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Exploitation of React2Shell Vulnerability by Botnets and Threat Actors
A critical unauthenticated remote code execution (RCE) vulnerability, identified as React2Shell (`CVE-2025-55182`), was disclosed in December 2025, affecting applications built with React Server Components and related frameworks such as Next.js. Public proof-of-concept exploits were released shortly after disclosure, enabling attackers to inject and execute arbitrary code on vulnerable systems. Security researchers and vendors, including Sysdig, responded by publishing detection guidance and threat bulletins, urging organizations to patch affected software, update dependencies, and monitor for signs of compromise. The vulnerability's severity and ease of exploitation have made it a high-priority target for both opportunistic and advanced threat actors. Notably, botnet operators, including those behind the RondoDox botnet, have begun actively targeting the React2Shell flaw to compromise systems at scale. Security advisories recommend immediate patching and enhanced monitoring, as exploitation attempts have increased rapidly following the public release of exploit code. The incident underscores the ongoing risk posed by supply chain and framework vulnerabilities, especially when widely used components are affected and attackers move quickly to weaponize new flaws.
Mar 21, 2026
React2Shell Remote Code Execution Vulnerability in React 19 and Next.js
A critical remote code execution vulnerability, dubbed **React2Shell**, was discovered in the React 19 library, specifically affecting React Server Components. The flaw allows unauthenticated attackers to execute arbitrary code on servers by sending crafted requests, making it a severe risk for organizations using default React and Next.js deployments. Within hours of public disclosure, security firms including Google’s Threat Intelligence Group and AWS confirmed active exploitation in the wild, highlighting the shrinking window between vulnerability awareness and real-world attacks. Researchers from Wiz and Unit 42 demonstrated that even clean, default deployments were susceptible, emphasizing the widespread impact due to the popularity of these frameworks. Threat actors rapidly weaponized the React2Shell vulnerability, with the RondoDoX botnet launching automated exploitation campaigns targeting both web applications and IoT devices. CloudSEK’s analysis of command and control logs revealed a multi-month campaign, with a significant spike in attacks following the vulnerability’s disclosure in December 2025. The RondoDoX botnet deployed various payloads, including web shells and cryptominers, and quickly adapted its infrastructure in response to security firm reports. Organizations with technology stacks overlapping the targeted vectors were promptly alerted, underscoring the urgent need for patching and monitoring in environments using React 19 and Next.js.
Mar 21, 2026
React2Shell RCE in React Server Components Drives Mass Server Compromise
Threat actors are actively exploiting **React2Shell**, a critical remote code execution flaw in React Server Components tracked as `CVE-2025-55182`, with related exposure also noted in Next.js as `CVE-2025-66478`. The bug stems from insecure deserialization in the React Server Components Flight protocol and allows unauthenticated attackers to upload malicious payloads and execute arbitrary code on vulnerable internet-facing servers. Public disclosure was quickly followed by advisories, proof-of-concept code, and reports of broad exploitation, while Microsoft and other researchers said hundreds of machines had already been hacked. Follow-on campaigns have been widespread and largely opportunistic, ranging from credential-harvesting operations to malware deployment against organizations in multiple sectors and regions. Cisco Talos-linked reporting said at least **766 servers** were compromised by an automated campaign that stole SSH keys, cloud tokens, API keys, Kubernetes and GitHub credentials, Docker metadata, and other environment secrets, including keys tied to AI platforms and payment services. Other investigations tied exploitation to **XMRig**, **RustoBot**, **Kaiji**, **Sliver**, **CrossC2**, **Tactical RMM**, **VShell**, and **EtherRAT**, along with persistence, reconnaissance, DNS-based exfiltration, and SSH key installation, underscoring how rapidly the vulnerability was weaponized after disclosure.
May 25, 2026