Executive Summary
In June 2025, a critical remote code execution vulnerability named React2Shell (CVE-2025-55182) was exploited in the wild against organizations using React Server Components. Within hours of the public disclosure and patch release, Chinese state-linked groups such as UNC5174 (CL-STA-1015), Earth Lamia, and Jackpot Panda, alongside opportunistic cybercriminals, began mass scanning and targeting exposed systems. The threat actors successfully deployed malware (notably Snowlight and Vshell), established persistent access, conducted credential theft, and attempted to extract Amazon Web Services configuration and credential files. Over 30 organizations across industries suffered breaches, including documented impact on customer cloud environments.
This campaign demonstrates the increasing speed and coordination of attackers exploiting newly public vulnerabilities, especially in widely deployed frameworks like React and Next.js. The incident underscores the necessity of rapid patching, improved east-west traffic security, and continuous threat detection, as adversaries quickly weaponize disclosures for initial access and persistent footholds.
Why This Matters Now
This incident highlights how fast-moving threat actors now exploit widely publicized vulnerabilities, achieving compromise within hours. With public proof-of-concept code available for CVE-2025-55182, urgent patching and proactive security controls are critical to contain rapidly developing campaigns targeting a broad enterprise and cloud ecosystem.
Attack Path Analysis
Attackers exploited the unauthenticated deserialization vulnerability (CVE-2025-55182) in exposed React Server Components, leading to remote code execution on cloud workloads. After initial compromise, adversaries sought and at times gained elevated access by extracting cloud credentials and config files. Some attackers leveraged deployed webshells and malware to move laterally within the compromised environment, targeting additional workloads or services. Command and control was established through deployed remote tools and pull of further payloads from external attacker infrastructure. Data and credential theft, as well as attempted outbound connections for exfiltration, were observed. Ultimately, impacts included cryptojacking, ransomware deployment potential, and business disruption to affected cloud environments.
Kill Chain Progression
Initial Compromise
Description
Attackers exploited the publicly exposed React Server Components vulnerability (CVE-2025-55182) to gain initial access via unauthenticated remote code execution.
Related CVEs
CVE-2025-55182
CVSS 10An unsafe deserialization vulnerability in React Server Components allows unauthenticated remote code execution via crafted HTTP requests.
Affected Products:
Meta React Server Components – 19.0.0, 19.1.0, 19.1.1, 19.2.0
Vercel Next.js – 15.x, 16.x
Meta react-server-dom-webpack – 19.0.0, 19.1.0, 19.1.1, 19.2.0
Meta react-server-dom-parcel – 19.0.0, 19.1.0, 19.1.1, 19.2.0
Meta react-server-dom-turbopack – 19.0.0, 19.1.0, 19.1.1, 19.2.0
Exploit Status:
exploited in the wildReferences:
https://nvd.nist.gov/vuln/detail/CVE-2025-55182https://www.cisa.gov/known-exploited-vulnerabilities-cataloghttps://www.microsoft.com/en-us/security/blog/2025/12/15/defending-against-the-cve-2025-55182-react2shell-vulnerability-in-react-server-components/https://aws.amazon.com/blogs/security/china-nexus-cyber-threat-groups-rapidly-exploit-react2shell-vulnerability-cve-2025-55182/https://www.cybereason.com/blog/cve-2025-55182-rce-vulnerability
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Command and Scripting Interpreter
Valid Accounts
Ingress Tool Transfer
Brute Force
OS Credential Dumping
Credentials from Password Stores
System Services
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Security of Public-Facing Applications
Control ID: 6.3.3
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA (Digital Operational Resilience Act) – ICT Risk Management
Control ID: Art. 9
CISA Zero Trust Maturity Model (ZTMM) 2.0 – Asset and Application Inventory
Control ID: 6.1.1
NIS2 Directive – Vulnerability Handling and Disclosure
Control ID: Art. 21(2)(d)
ISO/IEC 27001:2022 – Management of Technical Vulnerabilities
Control ID: A.12.6.1
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Critical React Server Components vulnerability enables remote code execution across software applications, requiring immediate patching and zero trust segmentation implementation.
Financial Services
React2Shell exploits threaten banking applications and trading platforms, demanding enhanced egress security controls and encrypted traffic monitoring per compliance requirements.
Health Care / Life Sciences
Healthcare web applications face remote code execution risks via React vulnerability, necessitating HIPAA-compliant threat detection and secure hybrid connectivity measures.
Internet
Web service providers experience widespread exploitation attempts from China-linked groups, requiring cloud firewall deployment and Kubernetes security enhancements for protection.
Sources
- Attackers hit React defect as researchers quibble over proofhttps://cyberscoop.com/attackers-exploit-react-server-vulnerability/Verified
- Defending against the CVE-2025-55182 (React2Shell) vulnerability in React Server Componentshttps://www.microsoft.com/en-us/security/blog/2025/12/15/defending-against-the-cve-2025-55182-react2shell-vulnerability-in-react-server-components/Verified
- China-nexus cyber threat groups rapidly exploit React2Shell vulnerability (CVE-2025-55182)https://aws.amazon.com/blogs/security/china-nexus-cyber-threat-groups-rapidly-exploit-react2shell-vulnerability-cve-2025-55182/Verified
- CVE-2025-55182: Critical Vulnerability, React2Shell, Allows for Unauthenticated RCEhttps://www.cybereason.com/blog/cve-2025-55182-rce-vulnerabilityVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Applying Zero Trust segmentation, east-west controls, inline threat detection, and strict egress enforcement would have limited adversary movement, reduced the attack surface, and alerted on or blocked suspicious activities at multiple points in the attack chain. Enabling distributed policy and granular workload isolation helps prevent initial exploitation from resulting in widespread compromise.
Control: Cloud Firewall (ACF)
Mitigation: Blocked unsolicited or malformed inbound exploit traffic to application workloads.
Control: Multicloud Visibility & Control
Mitigation: Alerted on and detected anomalous access to sensitive config assets.
Control: Zero Trust Segmentation
Mitigation: Prevented unauthorized workload-to-workload communication and lateral pivoting.
Control: Inline IPS (Suricata)
Mitigation: Detected and blocked command and control traffic and known malicious payloads.
Control: Egress Security & Policy Enforcement
Mitigation: Prevented unauthorized data exfiltration through strict outbound filtering.
Enabled rapid detection and response to anomalous or destructive workload behavior.
Impact at a Glance
Affected Business Functions
- Web Applications
- E-commerce Platforms
- Content Management Systems
Estimated downtime: 5 days
Estimated loss: $500,000
Potential exposure of sensitive customer data, including personal information and payment details, due to unauthorized access and code execution on affected servers.
Recommended Actions
Key Takeaways & Next Steps
- • Immediately enforce Zero Trust segmentation and workload isolation to minimize blast radius from exploited vulnerabilities.
- • Deploy and tune cloud-native firewalls and inline IPS for real-time inspection and blocking of exploit and C2 traffic.
- • Implement robust egress controls and monitoring to prevent exfiltration and remote payload retrieval from compromised workloads.
- • Increase visibility and anomaly detection across cloud and container platforms for rapid incident response to suspicious credential or configuration access.
- • Continuously inventory internet-facing assets and prioritize patching of critical vulnerabilities such as those in heavily adopted frameworks like React.



