Skip to main content
Back
IntrusionAWS · Azure · Google Cloud · Kubernetes
6 min read

React2Shell exploitation reaching cloud workloads and metadata credentials

Victim
Unnamed organizations running vulnerable React Server Components and Next.js applications
When
Within hours of the Dec 3, 2025 disclosure, per AWSDisclosed Dec 4, 2025
Entry
A single unauthenticated HTTP POST to an internet-facing React Server Components endpoint (CVE-2025-55182) ran code in the Node.js process; the attackers then went for secrets and cloud identity tokens on the host.

From December 3, 2025, within hours of the public disclosure of CVE-2025-55182, attackers sent crafted POST requests to internet-facing React and Next.js applications and ran code in the Node.js runtime. Microsoft saw them hunt for secrets, target the Azure, AWS and Google Cloud metadata endpoints for identity tokens and open reverse shells, and Wiz and Google saw miners and backdoors installed. No source says that a stolen cloud token was used against a cloud API.

What happened

External Parties
Attacker Infrastructure
Internet
Instance MetadataAWS, Azure, Google Cloud
Internet-Facing App Tier
Kubernetes Cluster
+ instance roles
+ managed identities
+ service accounts
Cloud Resources
React or Next.js App
Environment and Files
Service-Account Tokens
Pod Network

Replaying the React2Shell December 2025 intrusion

  1. 1

    Exposed server components

    Dec 3–4, 2025

    Applications on React Server Components 19.0 to 19.2.0 accept one crafted POST from the internet and run attacker code.

  2. 2

    Code on the host, secrets hunted

    Date not stated

    Injected code runs in the Node.js runtime and searches environment variables, files and mounted credentials for secrets.

  3. 3

    Cloud identity tokens

    Date not stated; token use not stated

    Attackers target the Azure, AWS and Google Cloud metadata endpoints for identity tokens; no source says a token was returned or used.

  4. 4

    Remote access and mining

    From Dec 5, 2025

    Compromised hosts open reverse shells, download payloads through tunnels, add users and run cryptominers.

Impact

Several hundred machines across diverse organizations were compromised, per Microsoft, with miners, backdoors, tunnelers and remote access tools installed and secrets and cloud identity tokens hunted. No source names a victim, and no source confirms that a stolen cloud credential was used against a cloud API.

Outcome

Where cloud-provider controls fit

The flaw sat in application code, so a cloud control could refuse the crafted request at the edge, cap what the host held, or limit where it could connect. You patch the packages first. Metadata access, egress and token reach then decide what a compromised host gives away. No source says that a stolen cloud token was used.

Could this have been prevented?

In hindsight, not as a whole. 2 controls would have refused a step outright, and 18 controls would have limited one. 5 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.

2
Prevented
18
Contained
5
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

External Parties
Attacker Infrastructure
Internet
Instance MetadataAWS, Azure, Google Cloud
Internet-Facing App Tier
Kubernetes Cluster
+ instance roles
+ managed identities
+ service accounts
Cloud Resources
React or Next.js App
Environment and Files
Service-Account Tokens
Pod Network

Replaying the React2Shell December 2025 intrusion

1 · Exposed server components

2 Prevented1 Contained1 Not covered1 on other clouds

2 · Code on the host, secrets hunted

4 Contained2 Not covered1 on other clouds

3 · Cloud identity tokens

8 Contained1 Not covered2 on other clouds

4 · Remote access and mining

5 Contained1 Not covered1 on other clouds

Key facts

  • The flaw was reported through the Meta Bug Bounty on November 29, 2025 and disclosed on December 3, 2025 with fixed versions 19.0.1, 19.1.2 and 19.2.1, at CVSS 10.0
  • AWS saw exploitation attempts within hours of the disclosure; one unattributed cluster sent 116 requests over 52 minutes on December 4, 2025 while it refined its payloads
  • CISA added CVE-2025-55182 to its Known Exploited Vulnerabilities catalog, citing evidence of active exploitation
  • Wiz counted at least six cryptomining incidents, each with several customers, and put vulnerable versions in 39% of the cloud environments it monitors
  • Microsoft reported several hundred machines across diverse organizations compromised
  • Microsoft saw the Azure, AWS and Google Cloud metadata endpoints targeted for identity tokens; AWS and Google report no metadata access, and no source says a token was returned

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    Critical Security Vulnerability in React Server ComponentsReact · Dec 3, 2025 · Advisoryvulnerability, affected versions, fixed versions, disclosure timeline
  2. 2.
    China-nexus cyber threat groups rapidly exploit React2Shell vulnerability (CVE-2025-55182)AWS Security Blog · Dec 4, 2025 · Vendor reportfirst exploitation attempts, named groups, attempted commands, AWS mitigations, indicators
  3. 3.
    CVE-2025-66478: RCE in React Server Components (AWS-2025-030)AWS Security Bulletins · Dec 4, 2025 · AdvisoryAWS service impact, WAF managed rule, customer actions
  4. 4.
    CISA Adds One Known Exploited Vulnerability to CatalogCISA · Dec 9, 2025 · Advisoryactive exploitation listing, catalog date
  5. 5.
    Critical RCE Vulnerabilities Discovered in React Server Components (React2Shell)Wiz Research · Dec 3, 2025 · Researchexploitation in the wild, credential hunting, container exposure, cloud environment shares, mitigations
  6. 6.
    Multiple Threat Actors Exploit React2Shell (CVE-2025-55182)Google Threat Intelligence Group · Dec 13, 2025 · Researchthreat actor clusters, malware, targeting, mitigations
  7. 7.
    Defending against the CVE-2025-55182 (React2Shell) vulnerability in React Server ComponentsMicrosoft Security Blog · Dec 15, 2025 · Researchpost-exploitation behavior, cloud metadata targeting, secret discovery, scale, persistence, detection and mitigation

The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.

More cloud attack breakdowns

All breakdowns