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

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.


