Threat feed

React2STEAL Actions campaign

React2STEAL hijacked GitHub Actions exploitation campaign

Posted · Spectrum Delta Research Team

Summary

React2STEAL, run by an unattributed operator, uses 45 repositories named ci-wk-<number> on hijacked GitHub accounts to mass-scan and exploit unpatched React and Next.js servers from GitHub-hosted Actions runners. Cyber threat intelligence lead Karina Reano found the first 38 repositories and OpenSourceMalware confirmed and expanded the count on 18 November 2026, with Chainguard publishing detection guidance the next day. The workflows try React2Shell pre-authentication code execution in React Server Components (CVE-2025-55182), the Next.js middleware authorization bypass via the x-middleware-subrequest header (CVE-2025-29927) and SSRF through the /_next/image endpoint to the AWS metadata service. On success a payload collects environment variables, .env and config files, database URLs, Stripe keys, AWS role credentials and AI provider keys, tests the AI keys against OpenAI, Anthropic and Gemini from the victim server, and commits everything in plaintext to the public repos. At publication the repos held at least 1,281 victim hostnames across 1,100 domains and were still committing new results every 11 minutes; the same accounts also appear in the wfx-loot CI secret theft campaign.

Breakdown

Targets

  • Industry: Opportunistic

Technical exposure

  • React Server Components 19.0.0-19.2.0 unpatched (CVE-2025-55182 RCE)
  • Next.js middleware bypass via x-middleware-subrequest header (CVE-2025-29927)
  • /_next/image optimizer allowed to fetch arbitrary hosts, reaching cloud metadata
  • GitHub accounts with stored tokens usable to run Actions workflows

Adversary

React2STEAL operator, unattributed; one lead points to GitHub account dascxzcw

Procedures (4)

  1. GitHub Actions runners mass-scan and exploit Next.js servers

    • T1595.002Active Scanning: Vulnerability Scanning
    • T1190Exploit Public-Facing Application

    Logs

    • Web server access log · POST with Next-Action header carrying multipart RSC payload in seven variations incl. chunked encoding; requests with x-middleware-subrequest header; /_next/image requests to 169.254.169.254

    Detectors

    • Microsoft Defender for Cloud · Potential React2Shell command injection detected on a Kubernetes cluster / Azure App Service
  2. Payload harvests secrets and tests AI provider keys

    • T1552.001Unsecured Credentials: Credentials In Files
    • T1552.005Unsecured Credentials: Cloud Instance Metadata API

    Logs

    • EDR process events · Outbound calls from a Node.js next-server process to api.openai.com, api.anthropic.com or generativelanguage.googleapis.com; process environment dump and config file reads

    Detectors

    • Microsoft Defender Antivirus · Trojan:JS/CVE-2025-55182.A and SuspNodeActivity detections for React2Shell exploitation
  3. Stolen loot committed to public ci-wk repositories

    • T1567.002Exfiltration Over Web Service: Exfiltration to Cloud Storage

    Logs

    • GitHub audit log · workflow_dispatch API events on ci-wk-<number> repos; commits of ZIP and JSON result files; new repos named ci-wk-<number> on previously quiet accounts
  4. Hijacked GitHub accounts reused from wfx-loot campaign

    Logs

    • GitHub audit log · Actions workflow runs on accounts carrying wfx-loot probe pull requests; tokens used from new IPs or locations

Indicators of compromise

CVEs (2)

  • CVE-2025-55182React2Shell pre-auth RCE in React Server Components 19.0.0-19.2.0
  • CVE-2025-29927Next.js middleware authorization bypass via x-middleware-subrequest header

Sources

Questions, detections or sightings of React2STEAL Actions campaign? Bring them to the community.