Loading story…
A GitHub repository masquerading as a vulnerability scanner for CVE-2025-55182, also known as React2Shell, was discovered to be distributing malware instead of providing legitimate security functionality. The tool, named React2shell-scanner and hosted by the user niha0wa, embedded a hidden payload within its code that executed a PowerShell command via mshta.exe to download additional malicious scripts from a remote server. This attack specifically targeted security professionals and researchers investigating the React2Shell vulnerability, leveraging their trust in open-source platforms to compromise Windows devices. GitHub responded by removing the repository after community reports and warnings from cybersecurity researchers.
Simultaneously, attackers have been actively exploiting the React2Shell vulnerability in the wild, particularly targeting Japanese organizations. Initial exploitation campaigns deployed cryptocurrency miners, but more recent attacks have introduced a sophisticated remote access trojan named ZnDoor. This malware is delivered through shell commands executed after successful exploitation of CVE-2025-55182, establishing persistent backdoor access and encrypted command and control communications. The emergence of ZnDoor marks a significant escalation in the threat landscape for organizations using vulnerable React/Next.js applications, highlighting the dual risks of both malicious "security" tools and direct exploitation by advanced malware.
See which actors are running it and whether you're in range.
6 events from the most recent confirmed update back to the earliest known activity.
After the repository was identified as malicious, GitHub removed it from the platform. Reports noted that cached copies or forks could still remain accessible despite the takedown.
A GitHub repository named React2shell-scanner, presented as a scanner for CVE-2025-55182, was found to contain a hidden malicious payload in react2shellpy.py. The script used mshta.exe and base64-encoded PowerShell to fetch and execute a remote file, targeting Windows systems.
NTT Security analysts uncovered and described the infection chain in which React2Shell exploitation was used to install ZnDoor, along with details on the malware's command structure and behavior. Their findings highlighted the campaign's persistence, evasion, and network tunneling capabilities.
Attackers escalated the React2Shell campaign by using the vulnerability to execute shell commands that downloaded and launched ZnDoor on affected devices. This marked a shift from miner deployment to a more advanced persistent backdoor capability.
Since December 2025, Japanese organizations have faced a surge of attacks exploiting the critical React/Next.js remote code execution flaw CVE-2025-55182, also called React2Shell. Early observed exploitation primarily deployed cryptocurrency miners on compromised systems.
ZnDoor, a remote access trojan later linked to React2Shell exploitation, had been active since at least December 2023. The malware was designed to provide persistent backdoor access with encrypted command-and-control communications and evasion features.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Correlate live exploitation activity against the software you actually run, and see where you're exposed.
2 references tracked. Mallory keeps watching after this page renders.
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.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A severe remote code execution vulnerability tracked as **`CVE-2025-55182`** was disclosed in **React Server Components** and quickly became known as **React2Shell**, with reporting indicating that exploitation spread soon after public disclosure. Security coverage from eSentire, BitSight, and Computer Weekly described the flaw as affecting React and Next.js environments, warned defenders to assess internet-exposed applications, and noted that attackers were moving from proof-of-concept activity toward broader exploitation. Public GitHub repositories rapidly appeared with exploit code, scanners, and remediation-focused projects, including tools explicitly labeled for **`CVE-2025-55182`** and **React2Shell** detection or exploitation. Repositories such as **`React2Shell-PoC`**, multiple **PoC scanners**, auto-exploit projects, and checkers lowered the barrier to weaponization, while at least one repository advertised fixes for React 19 users. The volume and speed of public tooling indicate that organizations running React Server Components or Next.js services faced immediate pressure to identify exposed systems, apply vendor fixes, and monitor for signs of remote code execution attempts.
Jul 12, 2026
Threat actors are actively exploiting **React2Shell** (**CVE-2025-55182**), a critical remote code execution flaw in the Flight protocol used for client-server communication in **React Server Components**. The issue is attributed to **insecure deserialization** that can allow unauthorized code execution on vulnerable servers, with observed targeting across insurance, e-commerce, and IT organizations. Reported payloads include the **XMRig** cryptocurrency miner as well as multiple botnets and remote access tooling; campaigns observed against Russian entities deployed **RustoBot** and **Kaiji**, while other activity distributed malware such as **CrossC2**, **Tactical RMM**, **VShell**, and **EtherRAT**. Affected packages include `react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` in versions **19.0**, **19.1.0**, **19.1.1**, and **19.2.0**, with fixes available in **19.0.1**, **19.1.2**, and **19.2.1**. Separate reporting highlighted that attackers leveraged a **public proof-of-concept (PoC)** for React2Shell and began targeting organizations within hours, reinforcing that rapid weaponization is now common; defenders are advised to patch and also perform post-patch validation, including checking for indicators of compromise, verifying *Next.js* and dependency versions, rebuilding projects after updates, and confirming lockfiles no longer reference vulnerable package versions.
Jun 29, 2026
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.
Aug 15, 2026