Collage: a woman in a fleece looks up among wind turbines, solar panels and a power plant crossed by a jagged lime intrusion line.
On this page (4)

In late December 2025, a significant coordinated cyber attack targeted multiple critical infrastructure entities across Poland, including more than thirty wind and solar farms, a private manufacturing firm, and a large combined heat and power plant (CHP) serving nearly half a million residents. The attack was attributed to a group known as Static Tundra, which is associated with Russia’s Federal Security Service (FSB). This group is also recognized under various names such as Berserk Bear, Energetic Bear, and Dragonfly, among others.

What happened on December 29

The attacks, which occurred on December 29, were intended to be purely destructive. Despite disrupting the communication between renewable energy farms and the distribution system operators, the attacks did not halt electricity production. Similarly, efforts to disrupt the heat supply from the CHP plant were ineffective.

How the intruders operated

The intruders gained access to power substations tied to renewable energy facilities, allowing them to conduct reconnaissance and disruptive activities. This included damaging controller firmware, deleting system files, and deploying a malware specifically designed for destruction, known as DynoWiper, as identified by cybersecurity firm ESET.

In the case of the CHP plant, attackers also engaged in prolonged data theft since March 2025. This facilitated further network infiltration, although attempts to employ the wiper malware went unfulfilled. For the manufacturing sector, the attack likely leveraged vulnerabilities in perimeter defense devices, specifically through unpatched Fortinet systems.

DynoWiper and LazyWiper

Various iterations of DynoWiper have been identified, installed primarily on Mikronika HMI Computers and network shares within the CHP via compromised FortiGate devices. Attackers capitalized on poorly secured infrastructure, taking advantage of accounts without two-factor authentication. Connections were made through Tor nodes and a variety of compromised IP addresses.

The functionality of the wiper malware is relatively straightforward, involving the initiation of a pseudorandom number generator, file enumeration, and corruption, followed by deletion. Notably, the malware lacks persistence mechanisms or methods to elude detection by security systems.

Another malware variant, LazyWiper, was employed against a manufacturing sector company. This PowerShell-based wiper overwrites files with pseudorandom sequences, rendering them irrecoverable. It is suspected to have been developed with the assistance of a large language model.

The malware attacks on renewable energy facilities were directly executed on HMI machines. In contrast, infections within the CHP and the manufacturing company involved domain-wide distribution via PowerShell scripts on domain controllers.

Attribution and cloud intrusion attempts

Furthermore, similarities in code between DynoWiper and other malware designed by the Sandworm group have been identified, although no conclusive evidence points to Sandworm’s direct involvement.

Notably, the adversaries attempted to penetrate cloud services using stolen credentials from the on-premises environments. They sought access to Microsoft 365 services, targeting critical technical information related to operational technology network modernization and SCADA systems within the organizations.

These findings underscore the persistent threat posed by state-sponsored cyber groups and the need for robust cybersecurity measures in safeguarding critical infrastructure.

Sources

  1. CERT Polska — Energy Sector Incident Report – 29 December 2025
  2. ESET WeLiveSecurity — DynoWiper update: Technical analysis and attribution

How we address this risk

Trusted Architecture

The design

Builds security into the design (Zero Trust, IAM/PAM, PKI), starting from the risks and the target governance.

Explore Trusted Architecture

Proof: Public transport operator

  • Critical infrastructure

    Why unmanaged network connections put critical services and customer trust at risk

    Every unmanaged network connection is a hidden doorway into your business, quietly exposing critical services and customer data to risks most organizations never see coming until it’s too late. Discover how overlooked links, forgotten devices, and unchecked access points can erode operations and undermine the trust your customers place in you, and learn where to start closing those gaps.

  • Critical infrastructure

    Why the HAProxy backdoor makes edge infrastructure a critical cyber risk

    Edge devices like load balancers and reverse proxies sit at the front door of your network, and when they’re compromised, attackers gain a privileged foothold that often goes unnoticed. This post examines how a backdoor in HAProxy-based infrastructure exposes that risk, why these systems are so attractive to attackers, and what security teams should be checking now.

Does this risk concern you?

Tell us about your context: an expert will get back to you.

Contact us

or write directly to trust@blooo.io

  • Reply within 24 hours
  • Non-disclosure agreement on request, before any exchange
  • First call of 30 minutes

Your e-mail is sent from your own mail client: blooo.io stores nothing. We only use your details to reply to you. Privacy policy.