Half of the internet-facing systems vulnerable to a fast-moving React remote code execution flaw remain unpatched, even as exploitation has exploded into more than a dozen active attack clusters ranging from bargain-basement cryptominers to state-linked intrusion tooling.

That's the assessment from Alon Schindel, VP of AI and Threat Research at Wiz, who [1]says CVE-2025-55182 – the React server-side vulnerability dubbed "React2Shell" – is now being actively exploited at scale, with researchers tracking at least 15 distinct intrusion clusters in the wild over the past 24 hours alone.

According to Wiz's latest telemetry, roughly 50 percent of publicly exposed resources known to be vulnerable are still running unpatched code, giving attackers a comfortable head start.

[2]

The critical-severity flaw, first disclosed earlier this month, affects React Server Components and dependent frameworks such as [3]Next.js and stems from unsafe deserialization in React's server-side packages, allowing an unauthenticated attacker to send a crafted request to achieve remote code execution. As The Register previously reported, [4]the bug quickly proved attractive to attackers because of React's ubiquity in modern web stacks, particularly in cloud-hosted environments where a single exposed endpoint can provide a foothold into far larger estates.

[5]

[6]

What began as opportunistic scanning and cryptomining has now broadened into something messier. Wiz says it is seeing a clear split between "commodity" exploitation – dominated by familiar cryptomining operations using tools like Kinsing, C3Pool, and custom loaders – and more deliberate intrusion sets deploying post-exploitation frameworks and bespoke malware.

Among the clusters observed are Python-based campaigns masquerading as miner droppers while quietly exfiltrating secrets, Sliver command-and-control infrastructure used for hands-on-keyboard operations, and a JavaScript file injector that systematically infects every server-side *.js file it can reach. Wiz also reports the re-emergence of EtherRat backdoor variants, a family of malware that had previously fallen out of favor but appears to have been dusted off for this wave of exploitation.

[7]

The technical sophistication is also creeping upward. Multiple miscreants are actively attempting to frustrate incident response by manipulating timestamps, minimizing logs, and otherwise scrubbing evidence of compromise. Those anti-forensics techniques, Wiz warned, suggest operators who expect to be hunted and intend to linger.

[8]Cloudflare blames Friday outage on borked fix for React2shell vuln

[9]Beijing-linked hackers are hammering max-severity React bug, AWS warns

[10]'Exploitation is imminent' as 39 percent of cloud environs have max-severity React hole

[11]Meta will move React to Linux Foundation to address vendor dominance fears

Other security firms are now corroborating that assessment. Palo Alto Networks' Unit 42 team has [12]linked the exploitation of CVE-2025-55182 to North Korean and Chinese threat groups. They stopped short of pinning it on any single baddie, but said the tooling and reused infrastructure look more like long-term intrusion work than smash-and-grab cryptomining.

"Unit 42 has identified activity that reportedly shares overlap with North Korean (DPRK) Contagious Interview tooling, though no formal attribution has occurred at this time. Contagious Interview is a campaign where threat actors associated with the DPRK pose as recruiters to install malware on the devices of job seekers in the tech industry," Unit 42 said. "Additionally, we've observed instances of the Linux backdoor BPFDoor. This is a Linux implant attributed to Chinese-linked threat actor Red Menshen."

React's dominance means vulnerable code isn't confined to obscure hobby projects, but sits inside production systems at startups, enterprises, and cloud-heavy organizations alike. Many of those deployments are internet-facing by design, and patching is not always straightforward.

As with so many modern web vulnerabilities, the danger is not just the bug itself but how quickly it becomes industrialized. React2Shell has already crossed that line, and with half the vulnerable surface still exposed, attackers have little incentive to move on just yet. ®

Get our [13]Tech Resources



[1] https://www.linkedin.com/posts/activity-7404544875360108544---cY/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAC2xvMBLPggh7Z3PC8i4V4yQ0JB56a2MlM

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/cybercrime&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aTxKKHTX7jwD_MtPnvYgSgAAAIs&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] http://next.js

[4] https://www.theregister.com/2025/12/05/aws_beijing_react_bug/

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/cybercrime&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aTxKKHTX7jwD_MtPnvYgSgAAAIs&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/cybercrime&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aTxKKHTX7jwD_MtPnvYgSgAAAIs&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_security/cybercrime&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aTxKKHTX7jwD_MtPnvYgSgAAAIs&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[8] https://www.theregister.com/2025/12/05/react2shell_pocs_exploitation/

[9] https://www.theregister.com/2025/12/05/aws_beijing_react_bug/

[10] https://www.theregister.com/2025/12/03/exploitation_is_imminent_react_vulnerability/

[11] https://www.theregister.com/2025/10/09/meta_react_foundation/

[12] https://unit42.paloaltonetworks.com/cve-2025-55182-react-and-cve-2025-66478-next/

[13] https://whitepapers.theregister.com/