4,400+ Rockwell PLCs Exposed Online, with 22 Detected in Water‑Infrastructure Attack Cities

0
68

Key Takeaways

  • Forescout’s August 3 scan identified 4,407 internet‑exposed Rockwell Automation PLCs worldwide, with 2,844 located in the United States.
  • In the recent wave of cyber‑attacks against U.S. water and wastewater utilities, 22 of the exposed controllers were found in affected cities; 19 of those shared the same mobile‑carrier network.
  • Attackers achieved disruptive effects without exploiting a known vulnerability by simply re‑configuring reachable PLCs—changing IP addresses and setting passwords—to knock operators off‑line or seize partial control.
  • The FBI and EPA have not disclosed how the threat actors initially located or accessed the targets, highlighting a gap in threat‑intelligence sharing.
  • Immediate defensive steps include removing PLCs from the public internet, enforcing strong authentication on cellular modems, isolating remote access via private APNs or VPNs, and maintaining verified offline copies of controller logic for recovery.
  • A significant portion of the exposed devices run older MicroLogix families (MicroLogix 1400 ≈ 50 %, MicroLogix 1100 ≈ 8 %) that are susceptible to CVE‑2017‑16740, a Modbus TCP buffer overflow patched in firmware 21.003.
  • Rockwell’s recovery advisory (SD1790) provides a factory‑reset procedure but stresses that firmware patches do not justify leaving PLCs openly reachable; a current offline project file is essential for restoration.
  • The trend shows a gradual decline in exposed Rockwell controllers from a peak of 7,814 in March 2020 to 4,407 in August 2026, yet thousands remain vulnerable, underscoring the need for sustained OT hardening across critical‑infrastructure sectors.

Overview of Forescout’s Scan Findings
Forescout researchers performed an internet‑wide scan on August 3, 2026, targeting Rockwell Automation programmable logic controllers (PLCs) that are reachable via the public internet. The scan uncovered 4,407 distinct EtherNet/IP hosts listening on TCP port 44818, the default port for Rockwell’s EtherNet/IP protocol. Of these, 2,844 were situated within the United States, representing roughly 65 % of the global exposure. While the scan quantified the number of exposed controllers, it did not attempt to verify whether any of the devices had already been compromised; the figure reflects potential attack surface rather than confirmed victims. The data provide a snapshot of how pervasive the practice of exposing industrial control equipment to the open internet remains, despite repeated warnings from government agencies and industry groups.

Scale of Exposure in the Recent Water‑Utility Incidents
In the weeks following July 27, 2026, a series of cyber‑incidents struck water and wastewater utilities across at least seven U.S. states, as reported by the FBI and the Environmental Protection Agency (EPA) in a joint public service announcement issued July 30. Forescout’s follow‑up analysis linked 22 of the exposed Rockwell PLCs to the geographic areas where those incidents occurred. Notably, nineteen of those twenty‑two controllers were observed to be operating on the same mobile‑carrier network, suggesting a common vector or shared infrastructure that attackers may have leveraged. The discrepancy between the FBI’s count of seven affected states and the Hacker News interpretation of Forescout’s post (which cited at least twelve states) illustrates the challenges in correlating open‑source intelligence with official agency reporting, especially when attribution remains pending.

How Attackers Disrupted Operations Without Exploiting a Known Vulnerability
Forescout emphasized that the disruptive effects described in the government alerts could be realized without needing to exploit a software flaw. Because the PLCs were already reachable from the internet, attackers could simply alter configurable parameters—such as the device’s IP address or login credentials—to impede legitimate operators. Changing the IP address effectively isolates the controller from its supervisory control and data acquisition (SCADA) system, causing a loss of visibility. Setting or changing passwords can lock out authorized personnel, thereby granting the attacker a degree of control over the connected physical processes (e.g., pumps, valves). This “configuration‑only” attack vector underscores that merely exposing a PLC to the internet creates a powerful foothold, even when the device’s firmware is free of known exploitable bugs.

Uncertainties Surrounding Initial Access and Target Selection
Despite the detailed forensic observations, neither the FBI/EPA announcement nor Forescout’s technical analysis explains how the threat actors initially discovered, selected, or gained entry to the targeted PLCs. Critical questions remain: Did attackers conduct mass internet scanning to identify exposed EtherNet/IP services? Did they leverage leaked credentials, compromised third‑party vendors, or supply‑chain compromises? The lack of clarity hampers defenders’ ability to prioritize mitigations beyond simply removing devices from the public net. It also points to a broader need for improved information sharing between private‑sector security researchers, telecom carriers, and government agencies to close the intelligence gap on early‑stage reconnaissance activities.

Immediate Defensive Recommendations from Authorities
In response to the ongoing campaign, the FBI and EPA issued concrete guidance for water‑utility operators and other critical‑infrastructure owners. Their recommendations include: enforcing strong, multi‑factor authentication on any cellular modem or router that provides remote access to PLCs; isolating remote‑access traffic through a private Access Point Name (APN), virtual private network (VPN), or equivalent segmented architecture; disabling unnecessary services such as Modbus TCP when not required; and maintaining comprehensive logging and monitoring to detect anomalous configuration changes. Most importantly, the agencies urge organizations to take controllers off the public internet entirely, thereby eliminating the unauthenticated attack surface that facilitated the observed incidents.

Technical Details: EtherNet/IP Exposure and Port 44818 Risks
The core technical vulnerability exploited in these incidents stems from the exposure of the EtherNet/IP service on TCP port 44818. When a Rockwell PLC makes this service reachable without authentication, an unauthenticated remote user can issue Common Industrial Protocol (CIP) requests to read device identity, enumerate available objects, or, depending on the device’s configuration, write to configuration registers. Forescout noted that, in many default configurations, an attacker can modify network settings (e.g., IP address, subnet mask) or set administrative passwords without needing any credentials. This capability turns a simple misconfiguration into a potent denial‑of‑service or semi‑active control vector, especially when combined with the ability to reset passwords and lock out legitimate operators.

Mobile‑Carrier Network Concentration of Exposed Devices
Forescout’s analysis revealed that more than 70 % of the U.S.-based exposed Rockwell controllers resided on large mobile‑carrier networks. A complementary Censys snapshot taken on July 30, 2026, identified 4,148 exposed EtherNet/IP hosts, with Verizon Business, AT&T Mobility, and T‑Mobile USA collectively accounting for 59 % of those findings. Although the absolute numbers differ slightly due to variations in scanning methodology, query criteria, and timing, both datasets converge on the observation that a substantial portion of exposed PLCs are reachable via cellular‑backhaul links. This concentration suggests that attackers may have exploited common misconfigurations in carrier‑provided routing or NAT devices, or that utilities frequently rely on cellular modems for remote site connectivity without adequately segmenting the traffic.

Firmware Specifics: MicroLogix Models and CVE‑2017‑16740
Among the exposed controllers, MicroLogix 1400 units constituted roughly 50 % of Forescout’s detections, while MicroLogix 1100 units made up about 8 %. Both families were explicitly named in the FBI/EPA advisory. Of the twenty‑two controllers located in the affected cities, nineteen were running firmware versions susceptible to CVE‑2017‑16740, a Modbus TCP buffer overflow affecting MicroLogix 1400 Series B and C devices with firmware 21.002 or earlier. Rockwell patched the flaw in firmware revision 21.003 (CVSS score 8.6). Exploitation of this vulnerability requires that Modbus TCP be enabled on the controller—a condition Forescout could not verify for the observed hosts. Even when patched, the researchers stressed that fixing the bug does not render public exposure acceptable; the underlying risk remains the unauthenticated reachability of the device itself.

Rockwell’s Discontinuation, Recovery Guidance, and the Need for Offline Backups
Rockwell Automation discontinued the MicroLogix 1100 product line on April 30, 2022, meaning many of the exposed devices are now legacy hardware without ongoing feature updates. To assist operators who may be locked out by an attacker‑changed password, Rockwell issued advisory SD1790, which outlines a factory‑reset procedure for the MicroLogix 1400 and 1100 models and instructions for re‑loading a known‑good project file. Notably, SD1790 carries no CVE identifier because it constitutes recovery guidance rather than a vulnerability disclosure. The advisory explicitly requires that the operator possess a current, verified offline copy of the controller’s logic (ladder logic, data tables, etc.). The FBI noted that at least one victim discovered altered PLC project files after detecting inconsistencies in ladder‑logic across multiple sites, underscoring the importance of maintaining immutable backups to facilitate rapid restoration and to detect tampering.

Broader Implications for OT Security and Future Outlook
The incident series highlights a persistent gap between awareness of OT risks and the actual hardening of field devices. While the total number of exposed Rockwell controllers has declined from a peak of 7,814 in March 2020 to 4,407 in August 2026—a reduction of roughly 44 %—the remaining exposure still represents a sizable attack surface for nation‑state or criminal actors targeting essential services. The reliance on cellular modems for remote connectivity, combined with insufficient network segmentation, creates a repeatable pathway that threat actors can exploit across multiple customers sharing similar configurations. Moving forward, defenders should adopt a defense‑in‑depth strategy: eliminate direct internet exposure, enforce zero‑trust principles for remote access, maintain rigorous patch and firmware management (while recognizing that patches alone are insufficient), and invest in continuous monitoring and anomaly detection tailored to industrial protocols. Only through such comprehensive measures can critical‑infrastructure operators reduce the likelihood that a simple configuration change leads to widespread operational disruption.

SignUpSignUp form

LEAVE A REPLY

Please enter your comment!
Please enter your name here