C0063: 2025 Poland Wiper Attacks
2025 Poland Wiper Attacks is a Russian state-sponsored campaign that conducted destructive cyberattacks against Polish energy infrastructure in December 2025. Targets included more than 30 wind and photovoltaic farms, a combined heat and power (CHP) plant, and a manufacturing sector company. The attacks on the distributed energy resources (DER) disrupted communications between affected facilities and the distribution system operator, but did not impact electricity generation or heat supply. Across the campaign, threat actors deployed two previously undocumented wiper tools, DynoWiper, a Windows-based wiper and LazyWiper, a PowerShell wiper, distributed via malicious Group Policy Objects. At the CHP plant, threat actors had maintained access since at least March 2025, using that foothold to obtain credentials and move laterally before attempting wiper deployment. Some reporting has assessed the activity to be consistent with Russian Federal Security Service (FSB) threat activity group Dragonfly, also tracked as STATIC TUNDRA, while other reporting attributes the destructive wiper activities to the Russian General Staff Main Intelligence Directorate (GRU) threat activity group ELECTRUM, also tracked as Sandworm Team.[1][2][3][4]
Security context for executives and security teams
C0063: 2025 Poland Wiper Attacks describes [2025 Poland Wiper Attacks](https://attack.mitre.org/campaigns/C0063) is a Russian state-sponsored campaign that conducted destructive cyberattacks against Polish energy infrastructure in December 2025. Targets included more than 30 wind and photovoltaic farms, a combined heat and power (CHP) plant, and a manufacturing sector company. The attacks on the distributed energy resources (DER) disrupted communications between affected facilities and the distribution system operator, but did not impact electricity generat...
Executive priority
C0063: 2025 Poland Wiper Attacks is an official MITRE ATT&CK campaign. Glexia treats it as defensive behavior context for prioritizing monitoring, control validation, and response planning without using the object by itself as an attribution claim.
Technical view
Security teams should validate C0063: 2025 Poland Wiper Attacks by reviewing the official ATT&CK relationships, mapped tactics (the mapped ATT&CK tactic context), supported platforms (the platforms named in the official object), and available local telemetry before making detection or mitigation decisions.
Likely telemetry
- Official ATT&CK relationships and object metadata
Detection direction
- Validate whether C0063: 2025 Poland Wiper Attacks appears in your detection coverage and tabletop scenarios.
- Use the object to align executive risk language with SOC, incident response, and detection engineering work.
- Do not treat ATT&CK relationship context as attribution without corroborating evidence.
Mitigation priorities
- Map the object to existing controls and identify missing telemetry or response ownership.
- Prioritize mitigations that reduce exposure on the listed platforms and tactics.
- Review adjacent ATT&CK relationships before changing policy, detections, or reporting language.
Additional notes and limits
Baseline Glexia take generated from the official MITRE ATT&CK STIX object, source hash, tactics, platforms, and detection fields. It is safe to replace with a richer model-generated take for the same source hash later.
This baseline take is source-grounded and schema-validated, but it does not include environment-specific telemetry, incident evidence, or threat-intelligence corroboration.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
2025 Poland Wiper Attacks
2025 Poland Wiper Attacks is a Russian state-sponsored campaign that conducted destructive cyberattacks against Polish energy infrastructure in December 2025. Targets included more than 30 wind and photovoltaic farms, a combined heat and power (CHP) plant, and a manufacturing sector company. The attacks on the distributed energy resources (DER) disrupted communications between affected facilities and the distribution system operator, but did not impact electricity generation or heat supply. Across the campaign, threat actors deployed two previously undocumented wiper tools, DynoWiper, a Windows-based wiper and LazyWiper, a PowerShell wiper, distributed via malicious Group Policy Objects. At the CHP plant, threat actors had maintained access since at least March 2025, using that foothold to obtain credentials and move laterally before attempting wiper deployment. Some reporting has assessed the activity to be consistent with Russian Federal Security Service (FSB) threat activity group Dragonfly, also tracked as STATIC TUNDRA, while other reporting attributes the destructive wiper activities to the Russian General Staff Main Intelligence Directorate (GRU) threat activity group ELECTRUM, also tracked as Sandworm Team.[1][2][3][4]
How security teams should use this page
Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.
Techniques used
This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.
| Domain | ID | Name | Relationship / procedure |
|---|---|---|---|
| Enterprise | T1529 | System Shutdown/Reboot | During the 2025 Poland Wiper Attacks, the adversaries forced victim devices to reboot to finalize destruction of impacted systems.[3][4] |
| Enterprise | T1053 | Scheduled Task/Job | During the 2025 Poland Wiper Attacks, the adversaries set FortiGate scheduled tasks to run the adversary generated CLI scripts weekly.[1] |
| Enterprise | T1484.001 | Group Policy ModificationSub-technique | During the 2025 Poland Wiper Attacks, the adversaries had leveraged Group Policy Objects to distribute wiper malware to victim devices through a network share.[1] |
| Enterprise | T1059.008 | Network Device CLISub-technique | During the 2025 Poland Wiper Attacks, the adversaries leveraged the native CLI of the targeted FortiGate device.[1] |
| Enterprise | T1048.003 | Exfiltration Over Unencrypted Non-C2 ProtocolSub-technique | During the 2025 Poland Wiper Attacks, the adversaries exfiltrated data to an actor-controlled infrastructure using HTTP POSTs.[1] |
| Enterprise | T1006 | Direct Volume Access | During the 2025 Poland Wiper Attacks, the adversaries copied volume shadow copies through executing `vssadmin` in order to dump the `NTDS.dit` file.[1] |
| Enterprise | T1090.003 | Multi-hop ProxySub-technique | During the 2025 Poland Wiper Attacks, the adversaries utilized Tor nodes for C2.[1] |
| Enterprise | T1571 | Non-Standard Port | During the 2025 Poland Wiper Attacks, the adversaries had created a Reverse SOCKS Proxy and communicated over the non-standard port 8008.[1][4] |
| Enterprise | T1567.004 | Exfiltration Over WebhookSub-technique | During the 2025 Poland Wiper Attacks, the adversaries leveraged an attacker-controlled Slack channel to exfiltrate data.[1] |
| Enterprise | T1584.001 | DomainsSub-technique | During the 2025 Poland Wiper Attacks, the adversaries compromised infrastructure to use for C2.[4] |
| Enterprise | T1049 | System Network Connections Discovery | During the 2025 Poland Wiper Attacks, the adversaries identified network connections utilizing `netstat -nao` and `netstat -r`.[1] |
| Enterprise | T1027.013 | Encrypted/Encoded FileSub-technique | During the 2025 Poland Wiper Attacks, the adversaries utilized a Base64-encoded ZIP archive to prevent content analysis.[1] |
| Enterprise | T1602.002 | Network Device Configuration DumpSub-technique | During the 2025 Poland Wiper Attacks, the adversaries gathered and used the FortiGate bookmarks defined in the configuration file to include the statically defined credentials that facilitated RDP connections to jump hosts.[1] |
| Enterprise | T1140 | Deobfuscate/Decode Files or Information | During the 2025 Poland Wiper Attacks, the adversaries decoded a Base64-encoded ZIP archive using the built-in certutil.[1] |
| Enterprise | T1587.001 | MalwareSub-technique | During the 2025 Poland Wiper Attacks, the adversaries observed that their malware was initially detected by the victims EDR solutions, so they modified the payload and attempted to execute the new version within the same day.[1][3][4] |
| Enterprise | T1560.001 | Archive via UtilitySub-technique | During the 2025 Poland Wiper Attacks, the adversaries compressed stolen files into a zip file prior to exfiltration.[1] |
| Enterprise | T1090 | Proxy | During the 2025 Poland Wiper Attacks, the adversaries utilized the rsocx tool identified as `r.exe` and `rsocx.exe` to tunnel within the internal infrastructure using a Reverse SOCKS Proxy.[1][4] |
| Enterprise | T1530 | Data from Cloud Storage | During the 2025 Poland Wiper Attacks, the adversaries leveraged stolen credentials within cloud services to download targeted data from SharePoint, and Teams.[1] |
| Enterprise | T1555 | Credentials from Password Stores | During the 2025 Poland Wiper Attacks, the adversaries configured a native CLI to gather a targeted elevated users password using `grep`.[1] |
| Enterprise | T1570 | Lateral Tool Transfer | During the 2025 Poland Wiper Attacks, the adversaries had placed the malicious payload on an accessible network share to facilitate propagation.[1][3][4] |
| Enterprise | T1102.002 | Bidirectional CommunicationSub-technique | During the 2025 Poland Wiper Attacks, the adversaries had communicated to both Dropbox and Pastebin.[1] |
| Enterprise | T1550.002 | Pass the HashSub-technique | During the 2025 Poland Wiper Attacks, the adversaries attempted to reuse password hash values to gain access to other systems.[1] |
| Enterprise | T1584.008 | Network DevicesSub-technique | During the 2025 Poland Wiper Attacks, the adversaries used compromised Cisco routers for network communications.[1] |
| Enterprise | T1016 | System Network Configuration Discovery | During the 2025 Poland Wiper Attacks, the adversaries gathered network configuration details utilizing `arp -a` and `nslookup` commands. [1] |
| Enterprise | T1105 | Ingress Tool Transfer | During the 2025 Poland Wiper Attacks, the adversaries downloaded malicious payloads to the victim server.[1] |
| Enterprise | T1110.002 | Password CrackingSub-technique | During the 2025 Poland Wiper Attacks, the adversaries attempted to crack user passwords.[1] |
| Enterprise | T1059.004 | Unix ShellSub-technique | During the 2025 Poland Wiper Attacks, the adversaries utilized the Linux `dd` command to overwrite portions of the disks with random data.[1] |
| Enterprise | T1057 | Process Discovery | During the 2025 Poland Wiper Attacks, the adversaries enumerated current running processes using `tasklist`.[1] |
| Enterprise | T1556.006 | Multi-Factor AuthenticationSub-technique | During the 2025 Poland Wiper Attacks, the adversaries modified two-factor settings within the FortiGate solution to `unset`.[1] |
| Enterprise | T1078.002 | Domain AccountsSub-technique | During the 2025 Poland Wiper Attacks, threat actors utilized privileged accounts to access the FortiGate VPN solution and subsequent subnets.[1] |
| Enterprise | T1133 | External Remote Services | During the 2025 Poland Wiper Attacks, threat actors leveraged the FortiGate VPN interface that was exposed to the internet to gain access to the victim environment.[1][2] |
| Enterprise | T1078.004 | Cloud AccountsSub-technique | During the 2025 Poland Wiper Attacks, the adversaries leveraged stolen credentials from on-premises environments to access cloud services.[1] |
| Enterprise | T1495 | Firmware Corruption | During the 2025 Poland Wiper Attacks, adversaries performed a factory-reset on compromised devices that hampered forensic investigations.[1] |
| Enterprise | T1584.003 | Virtual Private ServerSub-technique | During the 2025 Poland Wiper Attacks, the adversaries used compromised VPS servers for C2.[1] |
| Enterprise | T1490 | Inhibit System Recovery | During the 2025 Poland Wiper Attacks, the adversaries deleted Windows Volume Shadow Copies using `vssadmin delete shadows`.[1] |
| Enterprise | T1583.006 | Web ServicesSub-technique | During the 2025 Poland Wiper Attacks, the adversaries configured the FortiGate devices to send notifications to an attacker-controlled Slack channel. During the 2025 Poland Wiper Attacks, the adversaries had also staged tools and files on services such as Dropbox and Pastebin.[1] |
| Enterprise | T1074.001 | Local Data StagingSub-technique | During the 2025 Poland Wiper Attacks, the adversaries compiled discovery data locally on the victim host in a file located within `C:\Windows\TEMP\outlog.txt`.[1] |
| Enterprise | T1003.001 | LSASS MemorySub-technique | During the 2025 Poland Wiper Attacks, the adversaries attempted to dump credentials utilizing LSASS.[1][4] |
| Enterprise | T1113 | Screen Capture | During the 2025 Poland Wiper Attacks, the adversaries captured screenshots of devices using |
| Enterprise | T1485 | Data Destruction | During the 2025 Poland Wiper Attacks, the adversaries utilized wiper malware to overwrite files using a 16-byte buffer that fully overwrites files 16 bytes or smaller or partially overwrites files greater than 16 bytes to speed up the process.[3][4] |
| Enterprise | T1114.002 | Remote Email CollectionSub-technique | During the 2025 Poland Wiper Attacks, the adversaries leveraged stolen credentials within cloud services to gather data and email messages from Exchange services related to OT topics and technical work carried out within organizations.[1] |
| Enterprise | T1046 | Network Service Discovery | During the 2025 Poland Wiper Attacks, the adversaries utilized Ping, the Advanced Port Scanner and Advanced IP Scanner to enumerate network devices.[1] |
| Enterprise | T1021.001 | Remote Desktop ProtocolSub-technique | During the 2025 Poland Wiper Attacks, adversaries utilized RDP to log into jump hosts and then moved laterally to other victim devices to include a domain controller.[1] |
| Enterprise | T1083 | File and Directory Discovery | During the 2025 Poland Wiper Attacks, the adversaries obtained the contents of users’ directories using `dir /s /b C:\Users` command.[1] |
| Enterprise | T1036.005 | Match Legitimate Resource Name or LocationSub-technique | During the 2025 Poland Wiper Attacks, the adversaries created rules that mimicked the name of an institution already present in the network device configuration to avoid detection.[1] |
| Enterprise | T1003.002 | Security Account ManagerSub-technique | During the 2025 Poland Wiper Attacks, the adversaries had stolen Security Account Manager (SAM) and SYSTEM registry hives.[1] |
| Enterprise | T1588.007 | Artificial IntelligenceSub-technique | During the 2025 Poland Wiper Attacks, the adversaries generated custom script with an LLM.[1] |
| Enterprise | T1059.003 | Windows Command ShellSub-technique | During the 2025 Poland Wiper Attacks, the adversaries leveraged PsExec to run `cmd.exe` commands on multiple victim machines.[1] |
| Enterprise | T1608.002 | Upload ToolSub-technique | During the 2025 Poland Wiper Attacks, the adversaries had staged tools and files for use on Dropbox and Pastebin.[1] |
| Enterprise | T1590.006 | Network Security AppliancesSub-technique | During the 2025 Poland Wiper Attacks, the adversaries obtained details on the configuration of the victim Fortinet perimeter device to include publicly disclosed details on an online forum used by criminal communities.[1] |
| Enterprise | T1003.003 | NTDSSub-technique | During the 2025 Poland Wiper Attacks, the adversaries dumped the entire Active Directory database by extracting the contents of the ntds.dit file.[1] |
| Enterprise | T1686.002 | Network Device FirewallSub-technique | During the 2025 Poland Wiper Attacks, the adversaries modified security settings within the victims Fortigate device, utilizing the native CLI. During the 2025 Poland Wiper Attacks, the adversaries also disabled network traffic logging.[1] |
| Enterprise | T1558 | Steal or Forge Kerberos Tickets | During the 2025 Poland Wiper Attacks, the adversaries used the Rubeus tool to forge a Diamond Ticket that is a modified legitimate Kerberos ticket.[1] |
Groups, software, and campaigns
S0160: certutil
S1071: Rubeus
S0029: PsExec
S0183: Tor
Tor is a software suite and network that provides increased anonymity on the Internet. It creates a multi-hop proxy network and utilizes multilayer encryption to protect both the message and routing information. Tor utilizes "Onion Routing," in which messages are encrypted with multiple layers of encryption; at each step in the proxy network, the topmost layer is decrypted and the contents forwarded on to the next node until it reaches its destination. [1]
S0099: Arp
S0097: Ping
S9039: LazyWiper
LazyWiper is a destructive malware observed targeting a manufacturing sector company during the 2025 Poland Wiper Attacks. LazyWiper is a native Windows PowerShell script that is believed to have been generated by a large language model (LLM). LazyWiper overwrites files on the system using the C# function `WriteRandomBytes()` and can target multiple specific file types by their extensions.[1]
S0057: Tasklist
S9038: DynoWiper
DynoWiper is a destructive malware associated with the 2025 Poland Wiper Attacks in December of 2025. DynoWiper is a native Windows binary that is distributed by a PowerShell script and overwrites files using data generated by the Mersenne Twister algorithm before they are deleted from the system. Multiple variants of DynoWiper have been identified, with the primary differences being that one variant shuts down the system after completing its destructive operations, and another introduces a time delay between file overwriting and deletion.[1][2]
S0104: netstat
S0357: Impacket
All related ATT&CK context
Object version and sync metadata
The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates.
Imported snapshots across ATT&CK releases(2)
| Release | Bundle imported | Object version | Modified | Status | Raw hash |
|---|---|---|---|---|---|
| 19.2 | 1.0 | Current bundle | b3bb78d6762e… | ||
| 19.1 | 1.0 | Older bundle | 2a158d9fde1d… |
Mirrored ATT&CK source object
The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.
External references and citations
MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.
- [1]CERT Polska
CERT Polska. (2026, January 30). Energy Sector Incident Report – 29 December. Retrieved April 22, 2026.
Open source URL - [2]Dragos ELECTRUM JAN 2026
https://5943619.hs-sites.com/hubfs/Reports/dragos-2025-poland-attack-report.pdf. (2026, January). ELECTRUM: CYBER ATTACK ON POLAND’S ELECTRIC SYSTEM 2025. Retrieved April 22, 2026.
Open source URL - [3]ESET DynoWiper JAN 2026
ESET. (2026, January 30). Russian Sandworm group attacks energy company in Poland with DynoWiper, ESET Research discovers. Retrieved April 22, 2026.
Open source URL - [4]ESET DynoWiper Update JAN 2026
ESET. (2026, January 30). DynoWiper update: Technical analysis and attribution. Retrieved April 22, 2026.
Open source URL - [5]mitre-attackC0063Open source URL
Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.
