Detecting React and Next.js Server-Side RCE Activity

Hunt for shell, reconnaissance, and download commands executing from React, Next.js, Node modules, and application directories.

Detecting React and Next.js Server-Side RCE Activity
Detection queriesVulnerability Hunting Dec 21, 2023#React#Next.js#Node.js#RCE#CVE-2025-55182

Server-side JavaScript frameworks can expose a distinct post-exploitation context when a vulnerable application begins executing operating-system commands. The source defines a Linux audit hunt for React Server Components, Next.js, and similar server-side deserialization RCE scenarios.

Coverage includes CVE-2025-55182 and similar unauthenticated web deserialization vulnerabilities.

Behavioral Detection Query

The hunt looks for commands executing from directories related to Node.js, Next.js, React, or application code.

rule.groups:audit and data.audit.cwd:(*node_modules* or */next* or */react* or */app*) and data.audit.command:(sh or bash or dash or curl or wget or nc or ncat or python or python3 or whoami or id or uname or cat or chmod)

The command list includes:

  • shells;

  • download utilities;

  • Netcat variants;

  • Python;

  • identity and system discovery;

  • file permission changes.

The source recorded zero matches during the previous 30 days.

Vulnerability Exposure Query

The source also includes a direct vulnerability-index check:

vulnerability.id:"CVE-2025-55182"

This query also returned zero results.

Why Both Queries Are Useful

The vulnerability-index query answers whether a monitored package or host is associated with the specific CVE.

The behavioral query answers a different question: did a relevant application context execute commands that could indicate exploitation?

Using both helps avoid relying only on vulnerability inventory or only on behavior.

Investigation Workflow

If the behavioral query matches, review:

  • current working directory;

  • executable;

  • effective user;

  • parent process;

  • application logs;

  • HTTP requests around the same time;

  • network connections;

  • files created or modified.

A command such as whoami followed by curl or a shell from a Next.js application directory deserves further investigation.

Tuning

Build a baseline of legitimate application deployment and build activity. Node.js environments can legitimately execute shell commands during installation or build processes.

Production runtime hosts should generally have a narrower expected command profile than development or CI systems.

Operational Value

The source recorded no matches for either exposure or behavior, but the detection remains useful because it combines application context with command execution.

For Linux-hosted React and Next.js applications, that context can help identify the transition from server-side application exploitation to operating-system activity.

Cloud image

30 Days of Enterprise-Grade Cyber Defense

Step into the future of cybersecurity with full access to a unified, intelligent platform — free for 30 days. Empower your security team with:

  • Advanced SIEM for real-time visibility, smart alerting, and deep forensics across cloud, on-prem, and hybrid environments

  • Continuous Vulnerability Management to identify, prioritize, and remediate risk across all assets

  • Live Cyber Threat Intelligence integrated directly into your workflows, with global insights and attacker profiling

  • AI-Powered Threat Detection that learns from your environment, explains alerts in plain language, and suggests next steps

  • Built-in Compliance Readiness for NIS2, GDPR, ISO 27001, and more, with automated reporting and audit tools

Whether you're managing a lean SOC or a full-scale enterprise security team, this platform gives you the tools to detect faster, respond smarter, and stay ahead of evolving threats — all without the complexity.

Experience enterprise-grade protection, streamlined workflows, and total control.

Your 30-day head start begins now.

Unlock Your 30 Days Free Trial