analiza aiqbench
This automated campaign targets servers running patched React and Next.js frameworks to exfiltrate API keys and cloud credentials via GitHub Actions runners. Developers must verify their framework versions, inspect request logs for specific indicators, and immediately rotate any exposed secrets found in public repositories.
React2STEAL: What it is and what to check

De la Chainguard
FragmentReact2STEAL exploits patched React and Next.js vulnerabilities to steal credentials. Learn how the attack works and how to protect your applications.
React2STEAL is an automated exploitation campaign, reported by OpenSourceMalware on November 18, 2026, that uses GitHub Actions runners on hijacked GitHub accounts to scan the internet for React and Next.js servers and exploit two known, patched vulnerabilities: React2Shell (CVE-2025-55182) and the Next.js middleware authorization bypass (CVE-2025-29927).
It is not a supply chain attack. No npm package, GitHub Action or maintainer account was tampered with.
When an exploit lands, a script runs inside the victim's Node.js process, dumps environment variables, .env and config files, cloud credentials and API keys, tests any AI provider keys it finds, and commits all of it to a public GitHub repository.
At publication, the repos held at least 1,281 victim hostnames across about 1,100 domains, and were still committing new results about every 11 minutes.
If you run React Server Components or Next.js: confirm you are on a fixed version, check your request logs for the three indicators below, and rotate every secret a matching server could reach.
If you own a GitHub account: check for repos, branches and workflow runs you did not create. Most of the accounts running React2STEAL were also hit by the wfx-loot credential stealer.
Extras afișat conform termenilor RSS ai publicației · 193 cuvinte · textul integral și figurile sunt pe site-ul publicației
