Attack encyclopedia
FrostyGoop - the first malware to use Modbus TCP for sabotaging district heating systems
FrostyGoop - analysis of ICS malware that used Modbus TCP to attack heating in Lviv (January 2024). Timeline, mechanism, MITRE ATT&CK ICS T0855.
Józef SulwińskiPublished 6 min read

Contents
Lviv, January 22, 2024. The outside temperature drops below minus twenty degrees Celsius. In over 600 residential buildings served by the municipal heating company Lvivteploenerho, radiators are slowly going cold. Heating system operators see on their screens that the circulating water is hot - except it is not. The ENCO controllers that manage the heating process are reporting false readings. In reality, cold water is being pumped to the buildings. Residents call the hotline, but nobody understands what is happening - because all indicators look normal.
This was not a technical failure. This was FrostyGoop - the ninth malware in history designed specifically to attack industrial control systems. And the first to use the Modbus TCP protocol to carry out sabotage.
Context - Modbus without security
The Modbus protocol was created in 1979. It was designed for communication between PLC controllers in isolated industrial networks. No authentication or encryption mechanisms were included - any device that sends a correctly formatted command to port 502 will be served without being asked for identity. For decades this was not a problem, because industrial networks were physically separated from the outside world. But over the years, more and more controllers gained IP connectivity - and with it became accessible from the internet.
FrostyGoop took advantage of this fundamental weakness. It did not need any software vulnerability exploit. It sent valid Modbus TCP commands - commands that controllers executed obediently, because that is how they were designed.
Attack timeline
| Date | Event |
|---|---|
| April 2023 | Attackers gain access to the network through a compromised internet-facing Mikrotik router |
| April 2023 - January 2024 | Attackers establish an L2 tunnel and move laterally across a poorly segmented network |
| January 22, 2024 | The actual attack - FrostyGoop sends Modbus TCP commands to ENCO controllers, causing false readings and disrupting heating |
| January 22-23, 2024 | Nearly two-day heating outage affecting over 600 residential buildings |
| April 2024 | Dragos identifies FrostyGoop samples and begins analysis |
| July 2024 | Dragos publishes report at the S4 conference - the first public disclosure of the malware |
Anatomy of the malware - simplicity as a weapon
FrostyGoop is a binary written in Go, compiled for Windows. At the time of discovery, it was not detected by any commercial antivirus software - which itself was a warning about the limits of signature-based detection methods in OT environments.
The malware operated with surgical precision. Its configuration contained the IP addresses of ENCO controllers and sequences of Modbus commands to execute. The attackers did not need to write a complex exploit - they only needed to know the device addresses and Modbus function codes.
A key element of the attack was firmware manipulation on the controllers. Before the main strike, the attackers downgraded the software on ENCO controllers to a version lacking monitoring capabilities. In practice, this meant that operators lost the ability to remotely view the actual state of the devices. Only then did FrostyGoop start sending commands that caused false temperature readings - the system reported hot water while cold water was actually flowing to the buildings.
MITRE ATT&CK - technique mapping
| Tactic | ID | Description in the context of FrostyGoop |
|---|---|---|
| Impair Process Control | T0855 (Unauthorized Command Message) | Sending unauthorized Modbus TCP commands to ENCO controllers |
| Impair Process Control | T0831 (Manipulation of Control) | Changing heating system operating parameters - false temperature readings |
| Inhibit Response Function | T0857 (System Firmware) | Downgrading controller firmware to a version without monitoring |
| Initial Access | T0886 (Remote Services) | Access through a compromised internet-facing Mikrotik router |
| Lateral Movement | T0867 (Lateral Tool Transfer) | L2 tunnel enabling movement across the internal network |
Significance - why FrostyGoop changes the rules
FrostyGoop is the ninth known malware targeting ICS systems - after Stuxnet, Havex, BlackEnergy, Industroyer, Triton, Industroyer2, COSMICENERGY, and PIPEDREAM. But one feature sets it apart: using the Modbus TCP protocol as an attack vector.
Modbus is one of the most widely used protocols in industrial automation. According to Dragos data, over 46,000 devices with an open port 502 are accessible from the internet. FrostyGoop showed that attackers do not need advanced zero-days or elaborate exploit chains. Knowing the publicly available Modbus documentation and the IP address of a controller is enough.
How to protect yourself
TIP
Never expose Modbus TCP devices directly to the internet. Every controller should sit behind a firewall with deep packet inspection (DPI) capable of filtering Modbus traffic. We describe the principles of OT network segmentation in more detail in our article on OT network segmentation.
TIP
Monitor Modbus TCP traffic for anomalies - unknown source addresses, unusual function codes, write commands to configuration registers. Passive anomaly detection systems (e.g. Nozomi Networks, Dragos Platform) can identify such events without interfering with the process.
TIP
Update controller firmware and deploy software integrity verification mechanisms. The Lviv attack showed that firmware downgrading was a key preparatory step - it blinded operators before the actual strike.
TIP
Conduct an ICS asset inventory - you cannot protect devices you do not know exist. Pay special attention to devices with an open port 502 and verify that they are accessible only from authorized network segments.
TIP
Secure edge devices (routers, firewalls) in the OT network. In the Lviv case, initial access was gained through a compromised Mikrotik router. Regular updates and changing default passwords are the absolute minimum. We discuss the topic of secure remote access to ICS systems in our article on ICS remote access.
Summary
FrostyGoop is a warning for every organization operating control systems with the Modbus TCP protocol. The Lviv attack showed that advanced malware is not needed to deprive hundreds of thousands of people of heating in the middle of winter. Knowing the publicly available protocol documentation and having access to a network where controllers are not protected by segmentation or monitoring is enough.
For operators of heating, water, and energy infrastructure - where Modbus TCP is widely used - this incident should be a signal to immediately verify the exposure of ICS devices to external networks.
Sources
- How to Protect Against FrostyGoop: ICS Malware Targeting Operational Technology - Dragos
- FrostyGoop malware left 600 Ukrainian households without heat this winter - The Record
- What's the Scoop on FrostyGoop: The Latest ICS Malware and ICS Controls Considerations - SANS Institute
- FrostyGoop's Zoom-In: A Closer Look into the Malware Artifacts, Behaviors and Network Communications - Palo Alto Unit 42
- FrostyGoop ICS Malware Left Ukrainian City's Residents Without Heating - SecurityWeek
- New ICS Malware FrostyGoop Targeting Critical Infrastructure - The Hacker News
Need help in this area?
Our experts will help you assess the risk and plan next steps.