Skip to main content
Mallory
← Back to News
actively-exploited-vulnerabilityinternet-exposed-serviceproof-of-concept-releaseinitial-access-method

In-the-wild exploitation of React Native Metro4Shell (CVE-2025-11953) for remote code execution

Active Exploitation · 12 sources · Updated 5mo ago · First seen Feb 3, 2026

In-the-wild exploitation of React Native Metro4Shell (CVE-2025-11953) for remote code execution

Threat actors have been observed exploiting CVE-2025-11953 (aka Metro4Shell), a critical RCE flaw (CVSS 9.8) in the React Native Metro Development Server exposed via the @react-native-community/cli / @react-native-community/cli-server-api npm packages. The issue stems from Metro’s development-only /open-url HTTP endpoint accepting attacker-controlled input that can be passed unsanitized to an open() call; under default configurations Metro may bind to external interfaces, making developer systems reachable from the internet. JFrog disclosed the vulnerability in November 2025, and multiple proof-of-concept exploits emerged after public disclosure; affected versions were reported as @react-native-community/cli-server-api 4.8.0 through 20.0.0-alpha.2, with a fix in 20.0.0+.

VulnCheck telemetry and honeypot/canary observations indicate operational exploitation beginning Dec 21, 2025, with repeat activity on Jan 4 and Jan 21, 2026, delivering consistent payloads rather than one-off probing. Observed attacks used Base64-encoded PowerShell delivered in HTTP POST bodies to exposed endpoints; the script added Microsoft Defender exclusions (including the current working directory and C:\Users\<Username>\AppData\Local\Temp), established a raw TCP connection to 8.218.43[.]248:60124, downloaded an additional payload to the temp directory, and executed it. The downloaded binary was described as Rust-based with anti-analysis checks, and exploitation attempts were reported as originating from 5.109.182[.]231, 223.6.249[.]141, and 134.209.69[.]155, underscoring the risk of internet-exposed development infrastructure being used as an initial access vector.

This is being exploited nowSee which actors are running it and whether you're in range.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

6 events · Dec 21, 2025 – Feb 6, 2026
  1. Feb 6, 202610mo ago

    CISA warns about exploited React Native command injection flaw

    CISA issued a warning about the React Native Community command injection vulnerability being exploited in attacks, further elevating the issue's visibility for defenders. This marked a U.S. government alert following earlier private-sector reporting of active exploitation.

  2. Feb 3, 202610mo ago

    Public reporting highlights active exploitation and available mitigations

    Multiple security news outlets amplified VulnCheck's findings, describing Metro4Shell as a critical unauthenticated command injection flaw in React Native's Metro server and recommending upgrades to fixed @react-native-community/cli versions and restricting network exposure. Coverage also noted that proof-of-concept exploit code had appeared publicly, increasing exploitation risk.

  3. Jan 28, 202610mo ago

    VulnCheck publicly reports in-the-wild Metro4Shell exploitation

    VulnCheck published research disclosing that CVE-2025-11953, dubbed Metro4Shell, had been exploited in the wild since December 2025. The report detailed the observed payload chain, emphasized the risk from internet-exposed developer tooling, and noted the disconnect between confirmed exploitation and low public recognition.

  4. Jan 21, 202610mo ago

    Another exploitation wave delivers multi-stage Rust malware payload

    A further round of attacks was observed in late January, again using cmd.exe to launch a base64-encoded PowerShell loader that added Microsoft Defender exclusions, contacted attacker infrastructure, and downloaded a UPX-packed Rust payload. Related infrastructure also hosted a Linux payload, suggesting multi-OS targeting.

  5. Jan 4, 202611mo ago

    Attackers continue Metro4Shell campaign with repeat exploitation

    VulnCheck observed additional exploitation activity on a later wave in early January, indicating the activity was sustained and operational rather than one-off scanning or testing. The intrusion chain remained consistent across observed attacks.

  6. Dec 21, 202511mo ago

    Metro4Shell exploitation first observed against exposed Metro servers

    VulnCheck's Canary network first observed real-world exploitation of CVE-2025-11953 against internet-exposed React Native Metro Development Server instances. The attacks used the vulnerable /open-url endpoint to achieve unauthenticated command execution.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Vulnerabilities

1 linked

Affected products

1 linked
React-Native

Observables

10 linked

Indicator values are masked on this page. View all 10 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?Correlate live exploitation activity against the software you actually run, and see where you're exposed.
See Who's Exploiting This
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.