ZeroHour
Infosecurity Magazinepublished ()ingested Kevin Poireault

React2Shell Exploit Campaigns Tied to North Korean Cyber Tactics

highThreat actor exploited in the wildimportance 60CVE-2025-55182

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2025-55182
Unauthenticated RCE in React Server Components (React2Shell)

CVE-2025-55182 is a critical (CVSS 10.0) pre-authentication remote code execution flaw (CWE-502, deserialization of untrusted data) in React Server Components, specifically the react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack packages in versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0. It is triggered when the vulnerable code unsafely deserializes payloads from HTTP requests sent to Server Function endpoints, requiring no authentication or user interaction. An attacker gains arbitrary code execution on the affected server (CVSS scope changed, with high impact to confidentiality, integrity, and availability), and reporting notes a campaign in which hackers used the flaw to breach 766 Next.js hosts and steal credentials. Any React/Next.js application exposing Server Functions with the affected React versions is in scope, which given the ubiquity of React and Next.js is a very large deployed base. Exploitation is confirmed in the wild: the flaw was added to CISA's Known Exploited Vulnerabilities catalog on 2025-12-05 with known ransomware use, EPSS puts the 30-day exploitation probability at 99.8%, multiple public PoC/scanner repositories are available, and coverage has dubbed the flaw React2Shell.

Do: Upgrade the react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack packages to the vendor-patched releases (any version later than the vulnerable 19.0.0, 19.1.0, 19.1.1, and 19.2.0 line) and update Next.js per Vercel's advisory; as a KEV entry, U.S. federal agencies must apply vendor mitigations per BOD 22-01 or discontinue use. Audit internet-exposed Server Function endpoints for the vulnerable React versions and review logs for exploitation activity, including the reported campaign that breached 766 Next.js hosts and stole credentials, then rotate any exposed credentials.

10.0100% KEV ransomware PoC ×7
  • Meta (Facebook) React Server Components (react-server-dom-parcel, react-server-dom-turbopack, react-server-dom-webpack) 19.0.0, 19.1.0, 19.1.1, 19.2.0
  • Vercel Next.js (deployments using React Server Components/Server Functions via the affected react-server-dom-* packages) Applications bundling the affected React versions (19.0.0, 19.1.0, 19.1.1, 19.2.0); Next.js-specific fixed version numbers were not provided in the data
mass≈1M+ internet-facing Next.js/React Server Components deployments (order-of-magnitude estimate)

Indicators of compromiseAll →

TypeIndicatorContext
domainnodejs.orgtence mechanisms and downloads its own Node.js runtime from nodejs.org. “Rather than hardcoding a C2 server address, which can be
Full article693 words · extracted from infosecurity-magazine.com · click to collapse

Security researchers at Sysdig have observed new campaigns exploiting React2Shell which appear to have the hallmarks of North Korean hackers.

React2Shell is a remote code execution vulnerability in React Server Components (RSCs). Tracked as CVE-2025-55182, the flaw has a maximum severity rating with a CVSS score of 10.0.

Publicly disclosed on December 3, the vulnerability impacts version 19 of the React open source library for creating application user interfaces as well as many other related frameworks, including Next.js, Waku, React Router and RedwoodSDK.

Quickly after it was made public, Amazon Web Services (AWS) confirmed that threat groups including Earth Lamia and Jackpot Panda, both linked to Chinese state interests, were among those launching exploitation attempts.

Other threat actors were also observed exploiting React2Shell, including opportunistic actors installing cryptocurrency miners (primarily XMRig) and credential harvesters targeting AWS configuration files and environment variables.

Now, the Sysdig Threat Research Team (TRT) said they have discovered a novel implant from a compromised Next.js application that delivers EtherRAT.

The Sysdig TRT’s analysis, published on December 8, reveals significant overlap with tooling from North Korea-linked campaign cluster dubbed ‘Contagious Interview.’ This suggests either North Korean actors have pivoted to exploiting React2Shell or that sophisticated tool-sharing is occurring between nation-state groups.

React2Shell-EtherRAT Attack Chain Explained

EtherRAT is a remote access trojan (RAT) that leverages Ethereum smart contracts for command-and-control (C2) resolution, deploys five independent Linux persistence mechanisms and downloads its own Node.js runtime from nodejs.org.

“Rather than hardcoding a C2 server address, which can be blocked or seized, the malware queries an on-chain contract to retrieve the current C2 URL,” explained the Sysdig report.

The attack chain of the malicious campaign leveraging the React2Shell exploit follows four stages, each designed to establish persistent, evasive control over the compromised system:

  1. Initial Access: A base64-encoded shell command executes via React2Shell, deploying a persistent downloader that fetches a malicious script (s.sh) using curl/wget/python3 fallbacks and a 300-second retry loop
  2. Deployment: The downloaded script (s.sh) installs Node.js from nodejs.org (to avoid detection), creates hidden directories, and drops an encrypted payload and an obfuscated JavaScript dropper, then self-deletes
  3. Dropper: The JavaScript dropper (.kxnzl4mtez.js) decrypts the main payload using AES-256-CBC with hardcoded keys, writes the decrypted implant to disk, and executes it via the downloaded Node.js runtime
  4. Implant: The final payload establishes a persistent backdoor with blockchain-based C2, five redundancy mechanisms for persistence, and automatic payload updates, ensuring long-term access

Signs of Nation-State Groups’ Sophistication or Cooperation

These campaigns show similarities from multiple documented campaigns, including North Korean-linked campaigns.

For instance, the encrypted loader pattern used in these EtherRAT campaigns closely matches the North Korean-affiliated BeaverTail malware used in the Contagious Interview campaigns.

Sysdig noted that Google Threat Intelligence Group (GTIG) recently attributed the use of BeaverTail malware and blockchain-based C2 techniques to the North Korean-associated threat actor UNC5342.

“However, without direct code overlap, we cannot confirm the threat actor behind EtherRAT is the same. Given some of the significant differences listed above, this may represent shared techniques across multiple Democratic People's Republic of Korea-affiliated (DPRK) threat groups,” the Sysdig researchers wrote.

“Alternatively, while DPRK actors may have adopted React2Shell as a new initial access vector, it’s possible another sophisticated actor may be combining techniques from multiple documented campaigns to complicate attribution,” they added.

Summary of the novel capabilities in React2Shell-EtherRAT campaigns observed by Sysdig and how they compare to capabilities of relevant malicious campaigns. Source Sysdig
Summary of the novel capabilities in React2Shell-EtherRAT campaigns observed by Sysdig and how they compare to capabilities of relevant malicious campaigns. Source Sysdig

If the attribution is confirmed, these new campaigns represent a significant evolution in tradecraft, where North Korean actors trade a smaller payload size for reduced detection risk.

“While Lazarus Group and other North Korean-linked threat actors historically bundle Node.js with their payloads, the sample we identified downloads Node.js from the official nodejs.org distribution,” the researchers explained.

According to Sysdig researchers, EtherRAT marks a "significant evolution in React2Shell exploitation," shifting away from the typical opportunistic cryptomining and credential theft toward "persistent, stealthy access designed for long-term operations."

The team highlighted that the malware’s "combination of blockchain-based C2, aggressive multi-vector persistence, and a payload update mechanism" reflects a level of sophistication "not previously observed in React2Shell payloads." This suggests a more calculated and resilient threat model, they noted.

Text extracted automatically; images, tables and formatting may be missing. Original: https://www.infosecurity-magazine.com/news/react2shell-exploit-campaigns/