Hackers exploit React2Shell in automated credential theft campaign
What happened
Hackers are running a large-scale campaign to steal credentials in an automated way after exploiting React2Shell (CVE-2025-55182) in vulnerable Next. At least 766 hosts across various cloud providers and geographies have been compromised to collect database and AWS credentials, SSH private keys, API keys, cloud tokens, and environment secrets. This matters for IT, Telecom & Cyber because fresh price movement and input-cost detail should reset bid assumptions, breach response slas, and negotiation guardrails with 2025-55182, 766, 10608 as the clearest commercial anchors; expect renewal uplift asks
Buyer takeaway
For IT, Telecom & Cyber, this is a staffing-shape signal: remote operating models can shift work offsite and change which suppliers, systems, and service levels matter most
Cost / money
The cost angle is directional, not quantified: moving work offsite can cut travel, rotation, and accommodation exposure, but only if the remote setup stays reliable
Supplier / commercial
Expect scope to move toward software support, communications uptime, cyber obligations, and clearer downtime liability instead of only offshore headcount or hardware supply
Safety / operations
Fewer people offshore can reduce exposure and emergency-response load, but the operating model becomes more dependent on connectivity resilience, remote support readiness, and cyber hygiene
What to watch
Watch bandwidth resilience, latency tolerance, cyber obligations, and who carries downtime cost if the remote link drops
Key facts
- Hackers are running a large-scale campaign to steal credentials in an automated way after exp
- At least 766 hosts across various cloud providers and geographies have been compromised to co
- The operation uses a framework named NEXUS Listener and leverages automated scripts to extrac
- The researchers gained access to an exposed NEXUS Listener instance, allowing them to analyze
