Malicious NGINX Configurations Enable Large-Scale Web Traffic Hijacking Campaign
A large-scale web traffic hijacking campaign exploits malicious NGINX configurations injected via shell scripts targeting NGINX installations and Baota (BT) management panels. The attackers leverage the React2Shell vulnerability (CVE-2025-55182) to gain initial access and then deploy a multi-stage toolkit to persistently redirect legitimate web traffic through attacker-controlled servers. The campaign primarily targets Asian TLDs and Chinese hosting infrastructure but also affects government and educational domains globally. The attack enables interception and manipulation of web traffic, potentially leading to data theft, unauthorized access, and further compromise. The toolkit includes scripts for discovery, persistence, and configuration injection, with some payloads delivering cryptomining malware or reverse shells. The threat is medium severity due to its impact on confidentiality and integrity, the complexity of exploitation, and the scope of affected systems. European organizations using NGINX and Baota panels, especially those with government or educational domains, face risks from this campaign. Mitigation requires targeted patching, configuration audits, and enhanced monitoring of NGINX environments. Countries with significant NGINX usage and geopolitical interest in Asia-related cyber activities are most at risk.
AI Analysis
Technical Summary
This threat involves an active campaign exploiting the React2Shell vulnerability (CVE-2025-55182, CVSS 10.0) to inject malicious configurations into NGINX web servers and Baota (BT) management panels. Attackers use a multi-stage shell script toolkit to gain persistence and redirect legitimate web traffic through attacker-controlled backend servers via the NGINX "proxy_pass" directive. The toolkit includes zx.sh (orchestrator), bt.sh (targets Baota panel), 4zdh.sh (enumerates NGINX config locations), zdh.sh (targets Linux/containerized NGINX and specific TLDs), and ok.sh (generates reports on hijacking rules). The campaign primarily targets Asian TLDs (.in, .id, .pe, .bd, .th), Chinese hosting infrastructure, and government/educational TLDs (.edu, .gov), enabling attackers to intercept and manipulate web traffic. Observed post-exploitation payloads include cryptomining binaries and reverse shells, indicating both automated resource extraction and interactive access attempts. The campaign is linked to a broader reconnaissance effort targeting Citrix ADC and Netscaler gateways using residential proxies and cloud IPs to discover vulnerable login panels. The attack leverages legitimate utilities (curl, wget) or raw TCP connections for payload delivery, complicating detection. Despite no direct CVSS for the NGINX config injection, the underlying React2Shell vulnerability is critical, and the combined exploitation allows significant compromise of web infrastructure.
Potential Impact
For European organizations, this threat poses substantial risks to confidentiality and integrity by enabling attackers to intercept, manipulate, or redirect web traffic. Organizations running NGINX servers, especially those using Baota panels or hosting government and educational domains, could experience data leakage, session hijacking, or unauthorized access. The redirection of traffic through attacker-controlled servers may facilitate credential theft, malware distribution, or espionage. The presence of cryptomining payloads also indicates potential resource abuse, leading to degraded system performance and increased operational costs. The campaign's targeting of specific TLDs and hosting infrastructures suggests potential spillover into European entities with business or academic ties to Asia or those using similar infrastructure. Additionally, the use of reverse shells implies attackers may gain persistent interactive access, enabling lateral movement and further compromise within networks. The threat complicates incident response due to the use of legitimate tools and configuration files, increasing the risk of prolonged undetected presence.
Mitigation Recommendations
European organizations should conduct immediate audits of all NGINX configurations, focusing on unauthorized or suspicious 'proxy_pass' directives and unusual location blocks. Patch all systems to remediate the React2Shell vulnerability (CVE-2025-55182) promptly. Restrict access to management panels like Baota (BT) through network segmentation, strong authentication, and IP whitelisting. Implement file integrity monitoring on NGINX configuration directories to detect unauthorized changes. Employ enhanced logging and monitoring to identify anomalous traffic redirection or unexpected outbound connections from web servers. Use endpoint detection and response (EDR) tools to detect and block execution of suspicious shell scripts and post-exploitation payloads. Limit the use of curl, wget, and similar utilities on production servers or monitor their usage closely. Establish incident response playbooks specific to web traffic hijacking and conduct regular penetration testing to identify configuration weaknesses. Collaborate with threat intelligence providers to stay updated on indicators of compromise related to this campaign.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden, Belgium, Austria
Malicious NGINX Configurations Enable Large-Scale Web Traffic Hijacking Campaign
Description
A large-scale web traffic hijacking campaign exploits malicious NGINX configurations injected via shell scripts targeting NGINX installations and Baota (BT) management panels. The attackers leverage the React2Shell vulnerability (CVE-2025-55182) to gain initial access and then deploy a multi-stage toolkit to persistently redirect legitimate web traffic through attacker-controlled servers. The campaign primarily targets Asian TLDs and Chinese hosting infrastructure but also affects government and educational domains globally. The attack enables interception and manipulation of web traffic, potentially leading to data theft, unauthorized access, and further compromise. The toolkit includes scripts for discovery, persistence, and configuration injection, with some payloads delivering cryptomining malware or reverse shells. The threat is medium severity due to its impact on confidentiality and integrity, the complexity of exploitation, and the scope of affected systems. European organizations using NGINX and Baota panels, especially those with government or educational domains, face risks from this campaign. Mitigation requires targeted patching, configuration audits, and enhanced monitoring of NGINX environments. Countries with significant NGINX usage and geopolitical interest in Asia-related cyber activities are most at risk.
AI-Powered Analysis
Technical Analysis
This threat involves an active campaign exploiting the React2Shell vulnerability (CVE-2025-55182, CVSS 10.0) to inject malicious configurations into NGINX web servers and Baota (BT) management panels. Attackers use a multi-stage shell script toolkit to gain persistence and redirect legitimate web traffic through attacker-controlled backend servers via the NGINX "proxy_pass" directive. The toolkit includes zx.sh (orchestrator), bt.sh (targets Baota panel), 4zdh.sh (enumerates NGINX config locations), zdh.sh (targets Linux/containerized NGINX and specific TLDs), and ok.sh (generates reports on hijacking rules). The campaign primarily targets Asian TLDs (.in, .id, .pe, .bd, .th), Chinese hosting infrastructure, and government/educational TLDs (.edu, .gov), enabling attackers to intercept and manipulate web traffic. Observed post-exploitation payloads include cryptomining binaries and reverse shells, indicating both automated resource extraction and interactive access attempts. The campaign is linked to a broader reconnaissance effort targeting Citrix ADC and Netscaler gateways using residential proxies and cloud IPs to discover vulnerable login panels. The attack leverages legitimate utilities (curl, wget) or raw TCP connections for payload delivery, complicating detection. Despite no direct CVSS for the NGINX config injection, the underlying React2Shell vulnerability is critical, and the combined exploitation allows significant compromise of web infrastructure.
Potential Impact
For European organizations, this threat poses substantial risks to confidentiality and integrity by enabling attackers to intercept, manipulate, or redirect web traffic. Organizations running NGINX servers, especially those using Baota panels or hosting government and educational domains, could experience data leakage, session hijacking, or unauthorized access. The redirection of traffic through attacker-controlled servers may facilitate credential theft, malware distribution, or espionage. The presence of cryptomining payloads also indicates potential resource abuse, leading to degraded system performance and increased operational costs. The campaign's targeting of specific TLDs and hosting infrastructures suggests potential spillover into European entities with business or academic ties to Asia or those using similar infrastructure. Additionally, the use of reverse shells implies attackers may gain persistent interactive access, enabling lateral movement and further compromise within networks. The threat complicates incident response due to the use of legitimate tools and configuration files, increasing the risk of prolonged undetected presence.
Mitigation Recommendations
European organizations should conduct immediate audits of all NGINX configurations, focusing on unauthorized or suspicious 'proxy_pass' directives and unusual location blocks. Patch all systems to remediate the React2Shell vulnerability (CVE-2025-55182) promptly. Restrict access to management panels like Baota (BT) through network segmentation, strong authentication, and IP whitelisting. Implement file integrity monitoring on NGINX configuration directories to detect unauthorized changes. Employ enhanced logging and monitoring to identify anomalous traffic redirection or unexpected outbound connections from web servers. Use endpoint detection and response (EDR) tools to detect and block execution of suspicious shell scripts and post-exploitation payloads. Limit the use of curl, wget, and similar utilities on production servers or monitor their usage closely. Establish incident response playbooks specific to web traffic hijacking and conduct regular penetration testing to identify configuration weaknesses. Collaborate with threat intelligence providers to stay updated on indicators of compromise related to this campaign.
Technical Details
- Article Source
- {"url":"https://thehackernews.com/2026/02/hackers-exploit-react2shell-to-hijack.html","fetched":true,"fetchedAt":"2026-02-05T09:10:52.360Z","wordCount":1083}
Threat ID: 69845e9ff9fa50a62f0ff3a9
Added to database: 2/5/2026, 9:10:55 AM
Last enriched: 2/5/2026, 9:11:21 AM
Last updated: 2/5/2026, 8:26:59 PM
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
SIEM Rules for detecting exploitation of vulnerabilities in FortiCloud SSO
MediumResearchers Expose Network of 150 Cloned Law Firm Websites in AI-Powered Scam Campaign
MediumItaly Averted Russian-Linked Cyberattacks Targeting Winter Olympics Websites, Foreign Minister Says
MediumChina-Linked Amaranth-Dragon Exploits WinRAR Flaw in Espionage Campaigns
MediumDocker Desktop 4.44.3 - Unauthenticated API Exposure
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.