Water
Sector targeted
Mekorot
Israel's national water utility
3
OT protocols scanned
3rd
ICS/OT post in 10 days
WHAT DARKTRACE FOUND
ZionSiphon identifies itself explicitly. Darktrace's analysts recovered a function named ZionSiphon() in the binary, along with strings referencing the Israeli city of Dimona and the handle 0xICS. The malware's political intent is overt. Its technical intent is the part that matters for defenders.
On execution, the malware checks whether its host IP falls within Israeli address ranges. If the check passes, it scans the local system for water and OT-related software or configuration files. If the system matches the target profile, the malware establishes persistence through registry keys and USB propagation, scans the local subnet for industrial control system services, and attempts to modify configuration files to alter physical processes. The target list includes Mekorot, Israel's national water company, along with the Sorek, Hadera, Ashdod, and Palmachim desalination plants and the Shafdan wastewater treatment facility.
The sabotage logic is specific and dangerous. ZionSiphon targets chlorine dosage levels (potentially raising them to toxic concentrations or eliminating them entirely to allow pathogens through), containment valve positions, and reverse osmosis pressure. These are not abstract ICS parameters. These are the controls that determine whether the water coming out of a municipal tap is safe to drink.
THE ARCHITECTURE DETAIL THAT MATTERS
ZionSiphon scans for three OT protocols on the local subnet: Modbus on TCP port 502, DNP3 on port 20000, and S7comm on port 102. These are the protocols that run industrial processes. Modbus is used by programmable logic controllers across manufacturing and utilities. DNP3 is the protocol of record for electric utilities and water systems in North America. S7comm is the Siemens S7 PLC protocol. Any OT environment running any of these protocols on routable networks is reachable by malware with this architecture.
The USB propagation logic is equally notable. ZionSiphon scans for removable drives, copies itself to each one using the filename svchost.exe with hidden and system file attributes, and creates shortcut files that appear as regular documents. This is classic air-gap bridging. Water treatment facilities that maintain air-gapped OT networks, which is still common practice, can be infected through technician laptops and maintenance USB drives. The propagation method is not new. Its inclusion in a sample targeting water utilities in 2026 tells you the attacker expected air gaps and planned for them.
The sample has bugs. Darktrace identified an XOR mismatch in the country verification logic that causes the targeting check to fail and the self-destruct mechanism to trigger before the payload executes. The protocol scripts for Modbus and S7comm contain protocol-accurate prefix sequences but the code fragments are too short to form valid commands. This is not a finished weapon. It is a blueprint in the early stages of development.
THE SKILL FLOOR JUST DROPPED
Nathaniel Jones, Darktrace's VP of Security and AI Strategy, stated the finding plainly: "ZionSiphon shows a shift in the OT threat landscape: malware capable of targeting industrial processes is no longer exclusive to highly resourced nation-state programs we have seen in the past such as Stuxnet or Industroyer."
That sentence is the story. For fifteen years, the threat model for industrial control systems assumed that OT-capable malware was a nation-state capability. Stuxnet required the resources of the US and Israeli governments. Industroyer was attributed to the GRU. Triton required a team of highly skilled engineers working for a state program. The barrier to entry was so high that most OT environments could rely on it as a defensive assumption.
ZionSiphon was built by what Darktrace describes as a "low-maturity threat actor." The implementation has bugs. The code is incomplete. The attacker made mistakes a more sophisticated team would not have made. And yet the sample includes hardcoded targeting of named water utilities, ICS protocol scanning across three major OT protocols, USB propagation designed to bridge air gaps, and sabotage logic aimed at the physical parameters that determine whether drinking water is safe.
The next version will not have the bugs. The version after that will not be built by a low-maturity actor. The tooling, the techniques, and the target reconnaissance data are circulating. This is the pattern we covered on April 14 with Anthropic's Claude Mythos: AI-driven capability that was previously restricted to the most sophisticated attackers is now reaching actors at every level of the skill ladder. OT malware is following the same curve.
THE CRITICAL INFRASTRUCTURE ARC
This is the third critical infrastructure story we have published in ten days. Here is the pattern:
April 9: Iran hacking Rockwell PLCs across U.S. water systems, power grids, and government facilities. CISA, FBI, NSA, EPA, and DOE joint advisory. State-sponsored actor targeting American critical infrastructure with documented intent to disrupt.
April 15: Sweden disclosed a pro-Russian cyberattack on a thermal power plant. Poland, Norway, Denmark, and Latvia reporting the same pattern. Russian-linked groups shifting from DDoS to destructive attacks on European energy infrastructure.
April 19: ZionSiphon. Ideologically motivated actor targeting Israeli water utilities with OT-specific sabotage malware. Darktrace confirms the capability has moved beyond nation-state exclusivity.
Three different threat actors. Three different target countries. Three different utility sectors. One unmistakable trend: OT-focused attacks on water, energy, and critical infrastructure are no longer rare, and the tooling is no longer exclusive. Every operator of critical infrastructure is now in the same threat environment that was previously reserved for high-value nation-state targets.
INDICATORS OF COMPROMISE
ZIONSIPHON TARGETING
-
Geographic scope //
Israeli IP ranges (hardcoded) -
Target entities //
Mekorot, Sorek, Hadera, Ashdod, Palmachim, Shafdan -
OT protocols scanned //
Modbus (502), DNP3 (20000), S7comm (102) -
Sabotage targets //
Chlorine dosage, containment valves, reverse osmosis pressure -
Propagation //
USB via svchost.exe masquerade with shortcut files -
Persistence //
Registry keys, removable media -
Attribution signals //
Dimona references, "0xICS" handle, political strings -
Status //
Development build, XOR bug triggers self-destruct, Modbus/S7 payloads incomplete
WHAT THIS MEANS FOR OT OPERATORS
- 1
Audit what is reachable on your local subnets. ZionSiphon's core capability is subnet scanning for Modbus, DNP3, and S7comm services. If your IT and OT networks are flat or poorly segmented, every compromised endpoint on your network can enumerate your ICS assets. Network segmentation between enterprise IT and operational technology environments is not a best practice. It is a survival requirement.
- 2
Treat USB media as an active threat vector. The air gap assumption still drives a lot of OT security thinking. ZionSiphon's USB propagation with svchost.exe masquerade and shortcut lures is specifically designed to bridge air gaps through technician and maintenance workflows. USB policies, media sanitization, and trained technician procedures matter more, not less, when the OT network is physically separated from the internet.
- 3
Monitor your ICS configuration files for unauthorized changes. ZionSiphon attempts to sabotage by modifying configuration files that control chlorine dosing, valve positions, and pressure setpoints. File integrity monitoring on ICS configuration files, combined with alerting on any change that is not tied to an authorized work order, catches this class of attack before it reaches the physical process.
- 4
For water utilities specifically, understand that you are now in the same target category as Israeli desalination plants, Swedish thermal plants, and American PLCs. The fact that the first ZionSiphon sample targets Israel does not mean the next variant will. OT malware architectures are portable. Swap the hardcoded IP ranges and the target list, and the same tooling targets the next country. If you are a U.S. water district, the question is not whether your sector is a target. It is whether you have visibility into what is running on your OT network.
- 5
Engage outside help for OT security assessments. Most critical infrastructure operators do not have internal teams with OT-specific pen testing expertise. The talent is expensive and rare. Specialist firms can assess your OT environment against the exact threat patterns ZionSiphon, the Iran Rockwell targeting, and the Russian campaigns represent. Do this before a finished weapon arrives at your facility.