New 'ZionSiphon' Malware Specifically Targets Israeli Water Infrastructure for Sabotage

ZionSiphon: New OT Malware Discovered Targeting Israeli Water Treatment and Desalination Facilities

HIGH
April 18, 2026
7m read
MalwareIndustrial Control SystemsCyberattack

Related Entities

Organizations

DarktraceCheck Point

Other

ZionSiphonMekorotIsrael

Full Report

Executive Summary

Security researchers from Darktrace and Check Point have uncovered and analyzed a new, highly targeted malware strain named ZionSiphon. This malware is specifically designed to conduct espionage and sabotage against Israeli critical water infrastructure. The malware's code contains hardcoded strings referencing key entities like "Mekorot" (Israel's national water company) and major desalination plants, indicating a deliberate and focused development effort. ZionSiphon is a dangerous hybrid, combining traditional malware features like persistence and propagation via USB with Operational Technology (OT)-specific functions aimed at manipulating Industrial Control Systems (ICS). Its discovery underscores the growing threat of politically motivated cyberattacks capable of causing physical disruption to critical national infrastructure.

Threat Overview

ZionSiphon represents a significant escalation in targeted OT malware. Unlike generic ransomware that might incidentally hit an OT network, ZionSiphon was built with a clear purpose: to infiltrate and disrupt Israeli water systems. The malware's name and the specific targets embedded in its code (Sorek, Hadera, Ashdod, Palmachim desalination plants) point to a politically motivated actor.

The malware exhibits a multi-stage attack methodology:

  1. Infiltration: The initial vector is not confirmed but is likely phishing or a compromised IT asset. The malware's ability to propagate via removable media (USB drives) is a key feature, designed to bridge the air gap between IT and isolated OT networks.
  2. Espionage: Once on a system, it performs reconnaissance. It scans the local network for services and devices common in ICS environments and exfiltrates data.
  3. Sabotage: The most alarming feature is its built-in logic for sabotage. The code contains functions designed to tamper with local configuration files and manipulate control parameters for physical processes, such as chlorine levels and water pressure.

Even if the analyzed sample is a prototype, it demonstrates a clear intent and capability to develop weapons for causing tangible, physical harm through cyber means.

Technical Analysis

The malware's capabilities bridge the IT and OT worlds.

  • Propagation (T0867 - ICS ATT&CK): The use of USB drives for propagation is a classic technique for crossing air gaps and infecting isolated OT networks, famously used by Stuxnet.
  • Privilege Escalation (T1068): The malware includes functions to escalate its privileges on the infected host to gain deeper system access.
  • Discovery (T1592): ZionSiphon actively scans the local subnet to identify other devices and services, mapping out the OT network for further attack.
  • Manipulation of Control (T0831 - ICS ATT&CK): This is the ultimate goal. The malware contains specific logic to interact with and alter the settings of PLCs or other control systems, directly impacting the physical process.
  • Inhibit Response Function (T0826 - ICS ATT&CK): By tampering with configuration files or HMI displays, the malware could mislead operators, preventing them from understanding the true state of the system and responding correctly.

The specificity of ZionSiphon is its most alarming characteristic. This is not a tool of opportunity; it is a custom-built weapon aimed at a specific target set with the intent to cause physical consequences.

Impact Assessment

A successful attack using ZionSiphon could have catastrophic consequences. The malicious manipulation of a water treatment facility could lead to:

  • Public Health Crisis: Releasing untreated water or water with dangerous levels of chemicals (like chlorine) into the public supply.
  • Equipment Damage: Altering pressure or flow rates beyond safe operational limits could destroy pumps, pipes, and other expensive, hard-to-replace equipment, leading to long-term outages.
  • Economic Disruption: Shutting down major desalination plants, which are critical to Israel's water supply, would have significant economic and societal effects.

The discovery of the malware, even if it hasn't been used in a successful destructive attack, forces asset owners to undertake costly incident response, network hardening, and threat hunting activities. It also has a chilling effect, demonstrating that adversaries are actively developing and testing such capabilities.

IOCs

No specific file hashes or C2 domains were provided in the source articles.

Type
Malware
Value
ZionSiphon
Description
Name of the OT-focused malware strain.
Type
String
Value
Mekorot
Description
Hardcoded string found in the malware.
Type
String
Value
Sorek
Description
Hardcoded string referencing a desalination plant.

Cyber Observables for Detection

Type
event_id
Value
4663
Description
Monitor for file access events on critical PLC configuration files from unexpected processes.
Context
Windows Security Event Log on Engineering Workstations.
Type
process_name
Value
autorun.inf
Description
The use of USB propagation often involves autorun.inf files or LNK files on the root of the drive.
Context
EDR, disabling AutoRun feature via GPO.
Type
network_traffic_pattern
Value
Unusual subnet scanning
Description
A workstation suddenly scanning the OT network on ICS-related ports (e.g., 502, 44818) is highly suspicious.
Context
OT network monitoring solution.
Type
command_line_pattern
Value
tasklist /s
Description
Attackers often use reconnaissance commands to discover running processes on remote systems in the network.
Context
EDR, process creation logs.

Detection & Response

Detection Strategies:

  • OT Network Visibility: Deploy passive, OT-aware network monitoring tools that can parse industrial protocols and establish a baseline of normal communication. Alert on any new devices, new communication pathways, or use of unauthorized function codes.
  • D3FEND: Network Traffic Analysis (D3-NTA): Specifically look for IT-to-OT and OT-to-OT reconnaissance, such as a single host scanning multiple other hosts on ports like Modbus (502) or EtherNet/IP (44818).
  • Endpoint Monitoring on Workstations: EDR should be deployed on all engineering workstations and HMIs that run a Windows OS. Monitor for suspicious script execution, privilege escalation, and the presence of files dropped from USB drives.

Response Actions:

  1. If ZionSiphon is detected, immediately disconnect the affected USB drives and isolate the compromised workstations.
  2. Trigger a full threat hunt across the OT network, looking for other instances of the malware or signs of lateral movement.
  3. Preserve infected systems for forensic analysis to help identify the initial access vector and the full scope of the malware's capabilities.

Mitigation

Strategic Controls:

  • D3FEND: IO Port Restriction (D3-IOPR): Implement a strict policy for removable media. Disable USB ports on all OT assets where they are not explicitly required. For those that require them, use a solution that only allows company-issued, encrypted, and scanned USB drives.
  • Network Segmentation: Enforce strong network segmentation between the IT and OT networks. All traffic between them must be inspected through a DMZ. This helps contain an infection that starts on the IT side.
  • D3FEND: Executable Allowlisting (D3-EAL): On HMIs and engineering workstations, implement application allowlisting to ensure only known, approved software can execute. This can prevent the malware from running even if it makes it onto the system.

Timeline of Events

1
April 18, 2026
This article was published

MITRE ATT&CK Mitigations

Use a data historian to independently record sensor and process data. This allows operators to identify discrepancies between what the HMI is showing and the actual physical state, countering T0826 (Inhibit Response Function).

Implement strict IT/OT segmentation to prevent malware from easily moving from the corporate network into the process control network.

Physically or logically disable USB ports on all OT assets where they are not essential. For those that are, implement strict controls on removable media usage.

Mapped D3FEND Techniques:

Use application allowlisting on Windows-based HMIs and engineering workstations to prevent unauthorized executables like ZionSiphon from running.

D3FEND Defensive Countermeasures

The ZionSiphon malware's ability to propagate via USB is a critical feature designed to bypass network segmentation and infect air-gapped systems. The most direct countermeasure is IO Port Restriction. A strict policy must be implemented across the entire OT environment. First, use Group Policy Objects (GPO) or an EDR solution to block all USB storage devices by default on every HMI, server, and engineering workstation. For specific roles or tasks where USB drives are absolutely necessary (e.g., for PLC programming by a vendor), create an exception group. However, this exception should not be a free-for-all. Implement a 'USB Kiosk' system: all external USB drives must first be inserted into a hardened, isolated kiosk that scans the drive for malware before its contents can be transferred to a clean, company-issued encrypted USB drive. This clean drive is the only device authorized for use within the OT network. This breaks the attack chain by preventing the initial introduction of the malware from an infected external device.

To counter a threat like ZionSiphon, generic IT network analysis is insufficient. Organizations must deploy an OT-specific Network Traffic Analysis platform. These platforms have deep packet inspection (DPI) capabilities for industrial protocols (Modbus, EtherNet/IP, etc.). Once deployed passively via a network TAP or SPAN port, the tool should be put into a 'learning' mode to baseline all normal communication patterns within the water facility's control network. This creates a detailed map of which devices talk to which other devices, using what protocols and function codes. After the baseline is established, the system can detect anomalies that indicate a ZionSiphon infection. For example, it would alert on: 1) A workstation suddenly scanning the network for other PLCs. 2) An HMI attempting to communicate with a PLC it never talks to. 3) The use of dangerous or unusual function codes, such as a 'write configuration' command sent from an unauthorized source. This provides the visibility needed to detect the malware's lateral movement and sabotage attempts before physical damage occurs.

Sources & References

20th April – Threat Intelligence Report
Check Point Research (research.checkpoint.com) April 18, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

MalwareICSOTSCADAIsraelWater InfrastructureSabotage

📢 Share This Article

Help others stay informed about cybersecurity threats