{"id":10387,"date":"2026-02-04T10:03:54","date_gmt":"2026-02-04T10:03:54","guid":{"rendered":"https:\/\/serisec.com\/index.php\/2026\/02\/04\/hackers-exploiting-react-server-components-vulnerability-in-the-wild-to-deploy-malicious-payloads\/"},"modified":"2026-02-04T10:03:54","modified_gmt":"2026-02-04T10:03:54","slug":"hackers-exploiting-react-server-components-vulnerability-in-the-wild-to-deploy-malicious-payloads","status":"publish","type":"post","link":"https:\/\/serisec.com\/index.php\/2026\/02\/04\/hackers-exploiting-react-server-components-vulnerability-in-the-wild-to-deploy-malicious-payloads\/","title":{"rendered":"Hackers Exploiting React Server Components Vulnerability in the Wild to Deploy Malicious Payloads"},"content":{"rendered":"<p>    Hackers Exploiting React Server Components Vulnerability in the Wild to Deploy Malicious Payloads<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n    <!-- no image --><br \/>\n \t<BR><br \/>\n<BR><\/BR><\/p>\n<div>\n<p>Two months following the disclosure of <a href=\"https:\/\/cybersecuritynews.com\/react2shell-cve-2025-55182-attacks-rsc-enabled-services\/\" type=\"post\" id=\"136009\" target=\"_blank\" rel=\"noreferrer noopener\">CVE-2025-55182<\/a>, exploitation activity targeting React Server Components has evolved from broad scanning into consolidated, high-volume attack campaigns.<\/p>\n<p>According to telemetry from GreyNoise collected between January 26 and February 2, 2026, threat actors are actively leveraging this critical vulnerability to deploy cryptominers and establish persistent remote access.<\/p>\n<p>While the total number of unique sources attempting exploitation reached 1,083, traffic has heavily consolidated. Two specific IP addresses generated 56% of all observed malicious sessions, indicating automated, large-scale infrastructure rather than manual testing.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-threat-landscape-and-dominant-actors\"><strong>Threat Landscape and Dominant Actors<\/strong><\/h2>\n<p>The <a href=\"https:\/\/www.greynoise.io\/blog\/react2shell-exploitation-consolidates\" type=\"link\" id=\"https:\/\/www.greynoise.io\/blog\/react2shell-exploitation-consolidates\" target=\"_blank\" rel=\"noreferrer noopener\">observed attacks<\/a> utilize the public Metasploit module for <a href=\"https:\/\/cybersecuritynews.com\/poc-exploit-react-next-js\/\" type=\"post\" id=\"135184\" target=\"_blank\" rel=\"noreferrer noopener\">CVE-2025-55182<\/a>, which allows for pre-authentication remote code execution (RCE) via a single malicious HTTP POST request. The dominant threat actors have bifurcated their operational objectives:<\/p>\n<ol class=\"wp-block-list\">\n<li>\n<strong>The Cryptomining Campaign (87.121.84[.]24):<\/strong> Responsible for 22% of traffic (311,484 sessions), this actor executes a retrieval script to download an XMRig binary from staging servers. This campaign relies on external infrastructure to host payloads.<\/li>\n<li>\n<strong>The Interactive Access Campaign (193.142.147[.]209):<\/strong> Responsible for 34% of traffic (488,342 sessions), this actor bypasses staging servers entirely. Instead, the payload opens a reverse shell directly back to the scanner IP on port 12323, suggesting an intent for interactive network pivots rather than automated resource theft.<\/li>\n<\/ol>\n<p>Deep analysis of the cryptomining infrastructure reveals a history of malicious activity. The primary staging server, 205.185.127[.]97, has hosted attacker-controlled domains such as <code>mased[.]top<\/code> and <code>mercarios[.]buzz<\/code> since 2020.<\/p>\n<p>Furthermore, adjacent IP addresses in the same subnet (87.121.84[.]25 and 87.121.84[.]45) are currently distributing Mirai and Gafgyt variants, suggesting this subnet is a haven for botnet operators targeting both enterprise servers and consumer IoT devices.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-vulnerability-details\"><strong>Vulnerability Details<\/strong><\/h2>\n<p><a href=\"https:\/\/cybersecuritynews.com\/scanner-tool-reactjs-and-next-js\/\" type=\"post\" id=\"135070\" target=\"_blank\" rel=\"noreferrer noopener\">CVE-2025-55182<\/a> is a deserialization flaw in React Server Components that carries a CVSS score of 10.0. It allows unauthenticated attackers to execute arbitrary code by manipulating serialized data processed by the server.<\/p>\n<figure class=\"wp-block-table\">\n<table class=\"has-fixed-layout\">\n<thead>\n<tr>\n<th class=\"has-text-align-left\" data-align=\"left\">CVE ID<\/th>\n<th class=\"has-text-align-left\" data-align=\"left\">CVSS Score<\/th>\n<th class=\"has-text-align-left\" data-align=\"left\">Affected Software<\/th>\n<th class=\"has-text-align-left\" data-align=\"left\">Vulnerability Type<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td class=\"has-text-align-left\" data-align=\"left\"><strong>CVE-2025-55182<\/strong><\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">10.0 (Critical)<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">React Server Components<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">Insecure Deserialization<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n<p><strong>Affected Versions:<\/strong><\/p>\n<ul class=\"wp-block-list\">\n<li>React 19.0.0<\/li>\n<li>React 19.1.0 through 19.1.1<\/li>\n<li>React 19.2.0<\/li>\n<\/ul>\n<p><strong>Patched Versions:<\/strong><\/p>\n<ul class=\"wp-block-list\">\n<li>React 19.0.1, 19.1.2, 19.2.1<\/li>\n<\/ul>\n<p>Attackers are specifically targeting development ports, likely looking for misconfigured instances where developers have used the <code>--host 0.0.0.0<\/code> flag, inadvertently exposing the server to the public internet. The most targeted ports include 443, 80, 3000, 3001, and 3002.<\/p>\n<p>Security teams are urged to patch immediately to the latest React versions. If patching is not feasible, restrict network access to development ports and block the indicators listed below.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-indicators-of-compromise-iocs\"><strong>Indicators of Compromise (IOCs)<\/strong><\/h2>\n<p><strong>Network Indicators (IPv4)<\/strong><\/p>\n<figure class=\"wp-block-table\">\n<table class=\"has-fixed-layout\">\n<thead>\n<tr>\n<th class=\"has-text-align-left\" data-align=\"left\">IP Address<\/th>\n<th class=\"has-text-align-left\" data-align=\"left\">Type<\/th>\n<th class=\"has-text-align-left\" data-align=\"left\">Association<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td class=\"has-text-align-left\" data-align=\"left\">193.142.147[.]209<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">Attacker Source<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">Reverse Shell \/ Interactive Access<\/td>\n<\/tr>\n<tr>\n<td class=\"has-text-align-left\" data-align=\"left\">87.121.84[.]24<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">Attacker Source<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">XMRig Cryptominer Dropper<\/td>\n<\/tr>\n<tr>\n<td class=\"has-text-align-left\" data-align=\"left\">205.185.127[.]97<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">Staging Server<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">Payload Hosting<\/td>\n<\/tr>\n<tr>\n<td class=\"has-text-align-left\" data-align=\"left\">176.65.132[.]224<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">Staging Server<\/td>\n<td class=\"has-text-align-left\" data-align=\"left\">Payload Hosting<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n<p><strong>Network Artifacts<\/strong><\/p>\n<ul class=\"wp-block-list\">\n<li>\n<strong>Reverse Shell Port:<\/strong> TCP\/12323<\/li>\n<li>\n<strong>Traffic Pattern:<\/strong> HTTP POST requests containing unusual <code>Next-Action<\/code> headers.<\/li>\n<\/ul>\n<p><strong>File Hash (SHA-256)<\/strong><\/p>\n<ul class=\"wp-block-list\">\n<li>\n<code>[Hash pending further analysis]<\/code> \u2013 XMRig Binary (ELF) retrieved from 205.185.127[.]97.<\/li>\n<\/ul>\n<p class=\"has-text-align-center has-background\" style=\"background:linear-gradient(180deg,rgb(238,238,238) 94%,rgb(169,184,195) 100%)\"><strong>Follow us on <a href=\"https:\/\/news.google.com\/publications\/CAAqMggKIixDQklTR3dnTWFoY0tGV041WW1WeWMyVmpkWEpwZEhsdVpYZHpMbU52YlNnQVAB?hl=en-IN&amp;gl=IN&amp;ceid=IN:en\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Google News<\/a>, <a href=\"https:\/\/www.linkedin.com\/company\/cybersecurity-news\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">LinkedIn<\/a>, and <a href=\"https:\/\/x.com\/cyber_press_org\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">X<\/a> for daily cybersecurity updates. <a href=\"https:\/\/cybersecuritynews.com\/contact-us\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Contact us<\/a> to feature your stories.<\/strong><\/p>\n<p>The post <a href=\"https:\/\/cybersecuritynews.com\/react-server-vulnerability-exploited\/\">Hackers Exploiting React Server Components Vulnerability in the Wild to Deploy Malicious Payloads<\/a> appeared first on <a href=\"https:\/\/cybersecuritynews.com\/\">Cyber Security News<\/a>.<\/p>\n<\/div>\n<p> \t<BR><br \/>\n <BR><\/BR><br \/>\n    Guru Baran<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n<a href=\"https:\/\/cybersecuritynews.com\/react-server-vulnerability-exploited\/\">Go to cyber-security-news<\/a><br \/>\n \t<BR><br \/>\n <BR><\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hackers Exploiting React Server Components Vulnerability in the Wild to Deploy Malicious Payloads Two months following the disclosure of CVE-2025-55182, exploitation activity targeting React Server Components has evolved from broad scanning into consolidated, high-volume attack campaigns. According to telemetry from GreyNoise collected between January 26 and February 2, 2026, threat actors are actively leveraging this [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[129,63,648],"tags":[130],"class_list":["post-10387","post","type-post","status-publish","format-standard","hentry","category-cyber-security","category-cyber-security-news","category-vulnerability-news","tag-cyber-security-news"],"_links":{"self":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/10387"}],"collection":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/comments?post=10387"}],"version-history":[{"count":0,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/10387\/revisions"}],"wp:attachment":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/media?parent=10387"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/categories?post=10387"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/tags?post=10387"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}