Internet-Scale Measurement of React2Shell Exploitation Using an Active Network Telescope

summary

The gist

The paper presents the first Internet-scale measurement study of React2Shell exploitation activity using traffic collected from an Active Network Telescope…

In short

The study measured Internet-scale React2Shell exploitation activity using an Active Network Telescope. It found rapid post-disclosure exploitation patterns, showing automated scanning and geographically distributed scanners targeting a concentrated set of backend servers. This highlights the asymmetry between broad scanning sources and centralized exploitation infrastructure.

Key concepts

React2Shell
A critical remote code execution vulnerability (CVE-2025-55182) in React Server Components that allows attackers to execute arbitrary code by exploiting insecure deserialization of component data exchanged via the React Flight Protocol.
Active Network Telescope (ANT)
A monitoring system that actively probes the internet by responding to TCP SYN requests. This method captures application-layer data, unlike passive telescopes, allowing researchers to observe real exploitation attempts rather than just network flows.
Conjunctive Signature
A detection rule requiring three specific indicators in a payload simultaneously: an explicit reference to __proto__, the string 'constructor', and a React Flight reference token. Only payloads meeting all three criteria are classified as React2Shell-related exploitation attempts.
Infrastructure Asymmetry
The finding that while scanning sources are globally distributed, the backend infrastructure targeted in exploit payloads is highly concentrated in a small subset of countries. This reveals a structural imbalance between the attackers' probing methods and their actual exploitation targets.

Terminology used across episodes

This episode discusses

The paper

Internet-Scale Measurement of React2Shell Exploitation Using an Active Network Telescope · Read on arXiv

Aakash Singh, Kuldeep Singh Yadav, Md Talib Hasan Ansari, V. Anil Kumar

CSIR Fourth Paradigm Institute (CSIR-4PI) in Bengaluru, India

The increasing adoption of server-side component-based web frameworks has introduced new application-layer attack surfaces that remain insufficiently understood at Internet scale. On 3 December 2025, a critical remote code execution vulnerability (CVE-2025-55182) in React Server Components, referred to as React2Shell, was publicly disclosed and subsequently observed being exploited in the wild. Despite its critical severity and a CVSS base score of 10.0, there is limited empirical understanding of how this vulnerability is exploited across the Internet. This paper presents the first Internet-scale measurement study of React2Shell exploitation activity using traffic collected from an Active Network Telescope. We developed a deterministic detection methodology that identifies exploitation attempts targeting endpoints implementing React Server components. It helped analyze exploitation traffic to characterize its temporal evolution, geographic and autonomous system-level distribution, and behavioral properties of the observed scanning activity. In addition, exploit payloads are examined to understand the attacker infrastructure and delivery mechanisms. The analysis reported rapid post-disclosure exploitation activity exhibiting patterns consistent with automated scanning campaigns, geographically distributed scanners, and concentrated backend infrastructure. To the best of our knowledge, this work provides the first quantitative characterization of React2Shell-triggered scanning activity, including the number of distinct scanners, their geographic and autonomous system distribution, and the scale of backend infrastructure involved in exploitation attempts.

Transcript

Introduction to the show: ident: Security Radio. Generated commentary on the latest security and cryptography papers.

Nadia: We're looking at the paper: "Internet-Scale Measurement of React2Shell Exploitation Using an Active Network Telescope".

Elias: Here's the gist of the paper. The paper presents the first Internet-scale measurement study of React2Shell exploitation activity using traffic collected from an Active Network Telescope, which provides a quantitative characterization of scanning activity across geographic and autonomous system levels Vulnerability Context React2Shell is a critical remote code execution vulnerability (CVE-2025-55182) affecting React Server Components implementations, where insecure deserialization of component data exchanged through the React Flight Protocol enables remote code execution The flaw affects React Server Components implementations in versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0, including the packages react-server-dom-webpack, react-server-domparcel, and react-server-dom-turbopack The maximum severity rating reflects the vulnerability’s potential to compromise application infrastructure and its suitability for large-scale Internet exploitation Exploitation activity has been observed shortly after public disclosure Measurement Methodology The study utilizes an Active Network Telescope (ANT) to gain insights into Internet security dynamics by monitoring unsolicited traffic directed toward unused IP address space A typical passive network telescope, though proven to be a powerful cyberspace observatory mechanism for inferring Internet-wide security dynamics, has a major limitation: it often does not receive application-layer data The authors augmented the conventional passive network telescope framework with active capabilities, responding to TCP SYN requests with appropriate SYN/ACK packets to capture the initial payload The proposed framework consists of four logical stages: capturing inbound traffic, reconstructing connection-level flows, decoding and normalizing payloads, and evaluating them using a protocol-aware detection signature Exploitation Detection Signature A conjunctive signature is adopted requiring the simultaneous presence of multiple exploitation intrinsic indicators within a decoded payload to classify it as React2Shell-related A payload is classified as React2Shell-related only if it satisfies all of the following conditions: first, the payload must contain an explicit reference to proto, reflecting an attempt to traverse inherited object properties during deserialization; second, the payload must include the string constructor: constructor, corresponding to chained access of the JavaScript constructor property; and third, the payload must contain a React Flight reference token matching the pattern +d+:.

Nadia: Only payloads exhibiting all three indicators concurrently are classified as React2Shell exploitation attempts Activity Characterization The analysis revealed rapid post-disclosure exploitation activity exhibiting patterns consistent with automated scanning campaigns, geographically distributed scanners, and concentrated backend infrastructure The first React2Shell exploit-bearing packet originated from Kerkrade, the Netherlands, at approximately 05:55:49 IST on 5 December 2025 and was recorded by VP1 Over the course of the month, it established 169,301 connections at VP1 and 43,108 connections at VP2 The campaign reached its peak on 19 December 2025, when VP1 recorded 88,197 React2Shell-related connections in a single day Infrastructure Asymmetry The analysis showed a clear separation between widely distributed scanning sources and a more concentrated set of backend server locations Approximately 37.1% of all observed traffic originated in the Netherlands and spanned multiple autonomous systems, indicating a non-centralized scanner infrastructure Backend server countries are identified by extracting IP addresses embedded within decoded payloads, which we interpret as server endpoints used for redirection or secondary-stage interactions during exploitation Collectively, approximately 90% of backend traffic was directed toward servers hosted within a small subset of countries, indicating a strong concentration of backend infrastructure supporting the observed exploitation activity Scanning Dynamics The study quantified the number of unique destination IPs contacted by each source IP at both vantage points A total of 735 distinct scanner IPs were observed at VP1, with a median number of destinations contacted per scanner being 32 The two time series exhibit strong temporal alignment, with a Pearson correlation coefficient of r = 0.87 (p < 0.01), indicating a statistically significant positive correlation This suggests that both vantage points captured consistent temporal dynamics of the campaign The proposed study reveals that exploitation activity emerged rapidly following public disclosure, with scanning behaviour exhibiting characteristics consistent with automated and coordinated probing Across the observation period, exploitation traffic showed clear temporal escalation after the vulnerability announcement, geographically distributed scanning infrastructure spanning multiple autonomous systems, and repeated payload structures indicative of scripted exploitation campaigns Despite the global distribution of scanners, the backend infrastructure referenced in exploit payloads was notably concentrated within a small set of server locations We further observe that exploit payloads overwhelmingly embed direct server IP addresses rather than domain names, indicating that the observed campaigns rely primarily on IP-based backend infrastructure Collectively, these observations highlight the rapid weaponization of critical application-layer vulnerabilities and the structural asymmetry between distributed scanning sources and comparatively centralized exploitation infrastructure Future work may extend this analysis by incorporating additional vantage points, correlating telescope observations with interactive honeypot deployments, and conducting longitudinal measurements to evaluate the persistence of React2Shell exploitation following patch adoption The results improve situational awareness of emerging web application vulnerabilities and underscore the importance of Internet-scale measurement for understanding the operational dynamics of exploitation campaigns targeting modern web frameworks Acknowledgments We acknowledge the Ministry of Electronics and Information Technology (MeitY), Government of India, and the CSIR Fourth Paradigm Institute (CSIR-4PI) for providing funding and scalable computational resources to support this research References

1: M.

Elias: F.

Nadia: S.

Paper summary: Nadia: We’ve seen how they measured the activity and what their methodology was. Now let’s talk about why this study matters in the bigger picture.

Elias: This paper, "Internet-Scale Measurement of React2Shell Exploitation Using an Active Network Telescope," is essentially providing the first internet scale measurement study of React2Shell exploitation activity >

Priya: It claims that this measurement helps characterize how fast the exploitation activity escalates after public disclosure, and it reveals patterns consistent with automated scanning campaigns and coordinated botnet activity >

Nadia: So, when we look at what they did, it wasn't just watching traffic; they used an Active Network Telescope to gain insights into Internet security dynamics by monitoring unsolicited traffic directed toward unused IP address space >

Elias: They augmented the conventional passive telescope framework with active capabilities by responding to TCP SYN requests with appropriate SYN/ACK packets to capture the initial payload >

Priya: The core of their finding is that they developed a conjunctive signature requiring the simultaneous presence of multiple exploitation intrinsic indicators within a decoded payload to classify it as React2Shell-related >

Nadia: Specifically, a payload is only classified as React2Shell-related if it contains an explicit reference to proto, which reflects an attempt to traverse inherited object properties during deserialization >

Elias: And it also has the string constructor, constructor, which corresponds to chained access of the JavaScript constructor property >

Priya: Plus, it must contain a React Flight reference token matching the pattern +d+:. Only payloads exhibiting all three indicators concurrently are classified as React2Shell exploitation attempts >

Nadia: It’s interesting how they tie together those specific indicators to define what an exploit looks like in this framework >

Elias: And they used synchronised measurements from two independent vantage points to demonstrate a strong temporal correlation in observed React2Shell activity, validating both their detection methodology and the exploit signature >

Priya: That temporal correlation is key because it confirms the absence of exploit-bearing traffic prior to public disclosure and captures the subsequent escalation and fluctuations in exploitation intensity >

Nadia: It helps fill those gaps regarding temporal evolution, geographic and autonomous system level distribution of attackers, and whether exploitation is driven by opportunistic scanning versus coordinated botnet activity >

Elias: So, this study is critical because it gives us empirical data on how this vulnerability actually behaves in the wild across the entire internet >

Conclusion: Nadia: Looking at the title of "Internet-Scale Measurement of React2Shell Exploitation Using an Active Network Telescope," what’s really going on with this work?

Elias: It boils down to using an active network telescope to measure exploitation activity for a specific vulnerability, React2Shell >

Priya: And the implication is that it moves us from limited anecdotal evidence to having a quantitative characterization of scanning activity across geographic and autonomous system levels >

Nadia: The paper shows that exploitation emerged rapidly following public disclosure with patterns consistent with automated and coordinated probing across multiple sources >

Elias: But the key structural asymmetry they found is between widely distributed scanning sources and a more concentrated set of backend server locations embedded in the exploit payloads >

Priya: It really highlights how these critical application layer vulnerabilities can be weaponized quickly, and it shows that while attackers might scan globally, their actual infrastructure for exploitation is often much more centralized >

Nadia: So, this study underscores the rapid weaponization of vulnerabilities and the structural difference between the distributed scanning sources and the concentrated exploitation infrastructure >

Elias: And it points toward a need to improve situational awareness regarding emerging web application vulnerabilities by measuring them at an internet scale >

More episodes

← Home