What happened
Replaying the UAT-10608 Next.js intrusion
- 1
Remote code execution
not statedA crafted serialized payload sent over HTTP to a Server Function endpoint of a vulnerable Next.js application is deserialized and runs code in the Node.js process, with no authentication.
- 2
Harvesting on the host
not statedA dropper fetches and runs the harvesting script, which reads the process environment, application secrets, registry credentials, SSH keys and shell history.
- 3
Cloud and cluster identities
not statedThe script queries the AWS, GCP and Azure metadata services, retrieves the temporary credentials of the AWS instance role and reads the default Kubernetes service account token.
- 4
Sending the harvest out
not statedAfter each phase the host reports to the command-and-control server on port 8080, and the data goes into a database behind the NEXUS Listener web application.
The harvest collected environment secrets, SSH keys, shell history, cloud metadata credentials and Kubernetes tokens from at least 766 hosts, as counted on one command-and-control dashboard that had no password; about 196 hosts held AWS credentials, about 701 database credentials, about 599 SSH private keys and about 87 live Stripe keys. Talos treats every exposed credential as compromised, and no source reports that any credential was used.
Where cloud-provider controls fit
On AWS, a service control policy that denies long-lived access key creation stops new keys from being placed in the environment, while keys that already exist stay readable. Outbound rules in AWS security groups, a Google Cloud hierarchical firewall policy or an Azure network security group refuse a connection to an address they do not allow, for the hosts behind them. That bounds the report to the server on port 8080 and the dropper's download where egress is restricted to approved destinations; the sources do not say what the hosts ran on. IMDSv2 and network conditions bound the role credentials the script fetches. The flaw, the secrets of other services, the SSH keys and the Kubernetes token belong to the application, the host and the cluster, where Talos advises patching, rotating every credential in reach and enforcing IMDSv2.
Could this have been prevented?
In hindsight, no control would have stopped it. 32 controls would have limited how far it went. 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.
- 0
- Prevented
- 32
- 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.
Replaying the UAT-10608 Next.js intrusion
1 · Remote code execution
3 Contained1 Not covered1 on other clouds2 · Harvesting on the host
14 Contained3 Not covered3 on other clouds3 · Cloud and cluster identities
11 Contained1 Not covered2 on other clouds4 · Sending the harvest out
4 Contained1 on other cloudsKey facts
- CVE-2025-55182, rated CVSS 10.0, is a pre-authentication remote code execution flaw in React Server Components; the React team published fixed versions 19.0.1, 19.1.2 and 19.2.1 on December 3, 2025
- The exploit delivered a dropper that fetched a harvesting script and ran it with nohup from /tmp under a random dot-prefixed name; the script works in phases, from the process environment and SSH keys to the cloud metadata services and the Kubernetes token
- One command-and-control dashboard without a password counted at least 766 hosts over a 24-hour period: about 196 (25.6 percent) with AWS credentials, about 701 with database credentials, about 599 with SSH private keys, about 87 with live Stripe keys and about 66 with GitHub tokens
- The cloud_meta phase queried the AWS, GCP and Azure metadata services and retrieved the temporary credentials of the AWS instance role; the k8s phase read the default service account token at its standard mount path
- After each phase the host sent an HTTP request to the command-and-control server on port 8080; most NEXUS Listener instances are password-protected and Talos reached one that was not, so its counts describe that instance only
- The post gives no campaign dates, names no victim and no actor, and no source reports that any harvested credential was validated or used
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.UAT-10608: Inside a large-scale automated credential harvesting operation targeting web applicationsCisco Talos · Apr 2, 2026 · ResearchEntry vector, harvesting phases, cloud and Kubernetes credential collection, command and control, counts, recommendations
- 2.Critical Security Vulnerability in React Server ComponentsReact team · Dec 3, 2025 · AdvisoryThe vulnerability, affected and fixed versions, severity
- 3.China-nexus cyber threat groups rapidly exploit React2Shell vulnerability (CVE-2025-55182)AWS Security Blog · Dec 4, 2025 · ResearchThe AWS WAF managed rule group and the AWS Network Firewall mitigation for the same vulnerability
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.