#react2shell

RondoDoX botnet exploits React2Shell flaws and IoT vulnerabilities, spreading cryptomining malware and further threatening corporate networks, especially those using Next.js.

Source: CloudSEK

December 2025 showed how quickly modern vulnerabilities now translate into real-world impact across cloud, enterprise, and developer ecosystems.

The month was defined by several high-impact developments:

Mass exploitation of React2Shell, rapidly weaponised by state-linked and criminal actors.

Escalating supply chain compromises via malicious developer tools and poisoned extensions.

Intensified state-sponsored espionage prioritising persistence through edge devices and cloud misconfigurations.

Continued evolution of ransomware, shifting towards hypervisor-level attacks and packer-as-a-service ecosystems.

Sustained pressure from zero-days and DDoS, including record-breaking botnet activity.

Threat cluster UAT-10608 exploited React2Shell CVE-2025-55182 to steal SSH keys, AWS secrets, Stripe API keys, and GitHub tokens from 766 Next.js hosts.

Source: Cisco Talos

The evolution of web development has shifted significant complexity from the client to the server, particularly with the rise of React Server Components (RSC) and Next.js. While these technologies offer substantial performance benefits, they also introduce new attack vectors that challenge traditional security assumptions. The recent emergence of the React2Shell vulnerability and the sophisticated EtherRAT malware serves as a critical reminder that modern cloud-native attacks often chain subtle framework behaviors into devastating exploits.

Understanding the React2Shell Vulnerability

The React2Shell vulnerability, tracked under CVE-2025-55182 (React) and CVE-2025-66478 (Next.js), represents a high-impact Remote Code Execution (RCE) flaw. It specifically targets the Flight protocol used by React Server Components to serialize data between the server and the client.

What React2Shell Breaks

Unlike traditional vulnerabilities that can be fixed with a simple patch, React2Shell exploits the fundamental way server-side rendering (SSR) handles user-controlled input.

Sandbox Bypass: Once components render on the server, they exit the browser's security sandbox. An attacker can inject malicious JavaScript that executes within the backend runtime, gaining the same permissions as the application itself.

Sanitization Gaps: Client-side input validation is insufficient for server-rendered paths. Patterns that appear safe in a browser environment can become executable code when processed during SSR.

Implicit Trust: Developers often assume server-rendered components are safe because they originate from application logic. React2Shell proves that implicit framework behaviors can be abused to shift execution from the user's browser to the enterprise server.

The Rise of EtherRAT: Stealth via Blockchain

Following the disclosure of React2Shell, threat actors—including nation-state groups—began deploying a novel remote access trojan dubbed EtherRAT. This malware is notable for its unconventional command-and-control (C2) mechanism.

How EtherRAT Operates

Instead of relying on centralized servers that can be easily seized or blocked, EtherRAT utilizes the Ethereum blockchain for its infrastructure.

Blockchain C2: The malware queries specific Ethereum smart contracts to retrieve its current C2 server URL. This "EtherHiding" technique makes the infrastructure highly resilient and difficult to disrupt.

Stealthy Communication: Blockchain traffic often blends into legitimate enterprise network noise, especially in environments that utilize Web3 technologies or decentralized finance (DeFi) tools.

Staged Payloads: EtherRAT is typically delivered in stages, allowing it to pull down additional malicious modules based on the target environment's specific characteristics.

Security Checklist for React and Next.js Apps

To defend against React2Shell and similar threats, teams must move beyond static analysis and implement robust runtime protections. Use the following checklist to secure your production workloads.

1. Environment Inventory and Patching

Identify every service utilizing React Server Components, Next.js server actions, or traditional SSR.

Audit internal tools, admin panels, and dashboards, as these are often less frequently updated than customer-facing apps.

Ensure all framework versions are updated to the latest security advisories (React 19+ and Next.js 15+ contain critical mitigations).

2. Data Flow and Input Auditing

Trace all user-controlled input to ensure it is never passed directly into server-rendered components without strict server-side validation.

Review dynamic rendering paths that evaluate serialized content or complex data structures.

Implement a "zero-trust" approach to data originating from application logic; verify its integrity before it reaches the rendering engine.

3. Permission and Runtime Hardening

Apply the principle of least privilege to service accounts; ensure web processes cannot write to sensitive disk directories or spawn unauthorized child processes.

Restrict outbound internet access for server-side rendering workloads to only necessary endpoints.

Monitor for unexpected process behaviors, such as a Node.js process spawning a shell (sh, bash) or executing new binaries at runtime.

4. Network and Filesystem Monitoring

Watch for blockchain-related traffic (e.g., JSON-RPC calls to Ethereum nodes) originating from web servers that have no business requirement for Web3 connectivity.

Investigate long-lived outbound connections to unfamiliar external IP addresses.

Audit writes to temporary directories (/tmp) from web-facing processes, as these are common staging areas for malware payloads.

Conclusion

The transition to server-side execution in modern frameworks like React and Next.js requires a corresponding shift in security strategy. Vulnerabilities like React2Shell demonstrate that the boundary between frontend and backend is increasingly porous. By combining proactive patching with rigorous runtime observation and a robust security checklist, organizations can defend against sophisticated threats like EtherRAT and ensure the integrity of their modern web applications.

References

A security checklist for your React and Next.js apps - The New Stack

Defending against the CVE-2025-55182 (React2Shell) vulnerability in React Server Components - Microsoft Security Blog

Multiple Threat Actors Exploit React2Shell (CVE-2025-55182) - Google Cloud Blog

DPRK uses novel Ethereum implant in React2Shell attacks - Sysdig Threat Research Team

Exploitation of Critical Vulnerability in React Server Components (CVE-2025-55182) - Palo Alto Networks Unit 42

React2Shell (CVE-2025-55182): Detection & Mitigation - JFrog Security Research

Read the full report on -

Read the full report on -

Cisco AsyncOS zero-day CVE-2025-20393 was actively exploited against Secure Email Gateway and Secure Email and Web Manager appliances, with attacks linked to the Chinese-nexus group UAT-9686. SonicWall also confirmed in-the-wild exploitation of CVE-2025-40602 affecting SMA1000 appliances, while React2Shell CVE-2025-55182 enabled rapid Weaxor ransomware deployment on exposed servers. Amazon warned of cryptomining campaigns abusing compromised AWS IAM credentials, alongside FBI and French law enforcement actions disrupting ransomware laundering and responding to a government breach.