Metro4Shell RCE Vulnerability in React Native CLI Puts Developers at Risk

Metro4Shell RCE Vulnerability in React Native CLI Puts Developers at Risk

A critical flaw in the Metro Development Server of the "@react-native-community/cli" npm package, scored 9.8 on the CVSS, allows remote command execution, raising urgent security concerns.

NeboAI I summarize the news with data, figures and context
IN 30 SECONDS

IN 1 SENTENCE

SENTIMENT
Neutral

𒀭
NeboAI is working, please wait...
Preparing detailed analysis
Quick summary completed
Extracting data, figures and quotes...
Identifying key players and context
DETAILED ANALYSIS
SHARE

NeboAI produces automated editions of journalistic texts in the form of summaries and analyses. Its experimental results are based on artificial intelligence. As an AI edition, texts may occasionally contain errors, omissions, incorrect data relationships and other unforeseen inaccuracies. We recommend verifying the content.

A critical vulnerability identified as CVE-2025-11953, also known as Metro4Shell, has been exploited by threat actors targeting the Metro Development Server within the @react-native-community/cli npm package. Cybersecurity firm VulnCheck reported that the exploit was first detected on December 21, 2025, with a severity rating of 9.8 on the CVSS scale.

The security flaw enables remote attackers to execute arbitrary commands on affected systems without authentication. Despite its discovery in November 2025 by JFrog, the exploitation has not received widespread attention in the public domain. Evidence from VulnCheck's honeypot network indicates that attackers have utilized the vulnerability to deploy a Base64-encoded PowerShell script designed to perform various malicious actions, including establishing a connection to an external server.

This server, designated as 8.218.43[.]248:60124, is used to receive commands and execute downloaded binaries, which are crafted in Rust and include anti-analysis measures. The origins of these attacks have been traced back to multiple IP addresses, including 5.109.182[.]231 and 223.6.249[.]141. VulnCheck emphasized that the consistent nature of the payloads over several weeks indicates a sustained operational approach rather than mere testing of the vulnerability.

Want to read the full article? Access the original article with all the details.
Read Original Article
TL;DR

This article is an original summary for informational purposes. Image credits and full coverage at the original source. · View Content Policy

Editorial
Editorial Staff

Our editorial team works around the clock to bring you the latest tech news, trends, and insights from the industry. We cover everything from artificial intelligence breakthroughs to startup funding rounds, gadget launches, and cybersecurity threats. Our mission is to keep you informed with accurate, timely, and relevant technology coverage.

Press Enter to search or ESC to close