Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

DynoWiper update: Technical analysis

0
Medium
Published: Fri Jan 30 2026 (01/30/2026, 18:42:13 UTC)
Source: AlienVault OTX General

Description

ESET researchers provide technical details on a recent data destruction incident affecting a Polish energy company. They identified new data-wiping malware named DynoWiper, attributed to the Russia-aligned threat group Sandworm with medium confidence. The tactics, techniques, and procedures observed during the DynoWiper incident resemble those seen earlier in an incident involving the ZOV wiper in Ukraine. Sandworm has a history of destructive cyberattacks, targeting various entities including energy providers. The DynoWiper samples focus on the IT environment, with no observed functionality targeting OT industrial components. The attackers deployed additional tools and attempted to use a SOCKS5 proxy. The incident represents a rare case of a Russia-aligned threat actor deploying destructive malware against an energy company in Poland.

AI-Powered Analysis

AILast updated: 02/02/2026, 11:15:50 UTC

Technical Analysis

DynoWiper is a sophisticated data-wiping malware recently analyzed by ESET researchers following an incident targeting a Polish energy company. The malware is attributed with medium confidence to Sandworm, a Russia-aligned threat actor known for destructive cyber operations against critical infrastructure, including energy providers. DynoWiper’s tactics, techniques, and procedures (TTPs) closely resemble those used in the earlier ZOV wiper attacks in Ukraine, suggesting a shared development lineage or operational strategy. Unlike some previous attacks that targeted OT environments, DynoWiper focuses exclusively on the IT environment, aiming to destroy data and disrupt business continuity. The attackers also deployed auxiliary tools and leveraged SOCKS5 proxies to mask command and control communications, complicating detection and attribution. The malware’s destructive payload irreversibly deletes data, undermining system integrity and availability. No CVEs or known exploits are associated with DynoWiper, indicating it may rely on prior access or compromised credentials for deployment. This attack represents a rare but significant escalation of destructive cyberattacks against European energy infrastructure by state-aligned actors. The incident underscores the importance of robust cyber defenses and incident response capabilities tailored to wiper malware and advanced persistent threat (APT) tactics.

Potential Impact

For European organizations, especially in the energy sector, DynoWiper poses a critical threat to data integrity and operational continuity. The malware’s destructive nature can lead to irreversible data loss, prolonged downtime, and significant recovery costs. Disruption of IT systems in energy companies can cascade into broader service interruptions affecting supply and national security. Given Sandworm’s history, there is a risk of further attacks targeting other critical infrastructure sectors across Europe. The use of proxies and additional tools by attackers complicates detection and response, increasing the likelihood of successful infiltration and damage. The psychological and reputational impact on affected organizations can also be substantial. For Poland, the direct victim, the attack highlights vulnerabilities in critical infrastructure cybersecurity. Neighboring countries with similar energy infrastructure and geopolitical tensions with Russia may face elevated risks. The incident may also prompt regulatory scrutiny and increased investment in cybersecurity resilience across European energy providers.

Mitigation Recommendations

European energy organizations should implement advanced endpoint detection and response (EDR) solutions capable of identifying wiper malware behaviors such as mass file deletion and unauthorized disk access. Network monitoring should include detection of anomalous SOCKS5 proxy usage and unusual outbound connections to suspicious IPs or domains like those identified (e.g., 31.172.71.5, progamevl.ru). Segmentation between IT and OT networks must be enforced to limit lateral movement and contain potential damage. Regular, immutable backups stored offline or in air-gapped environments are critical to enable recovery from destructive attacks. Incident response plans should be updated to include wiper malware scenarios, emphasizing rapid containment and forensic analysis. Threat intelligence sharing within European energy sector Information Sharing and Analysis Centers (ISACs) should be enhanced to disseminate indicators of compromise (IOCs) and TTPs related to DynoWiper and Sandworm. Multi-factor authentication (MFA) and strict access controls can reduce the risk of initial compromise. Finally, organizations should conduct regular red team exercises simulating destructive malware attacks to test detection and response capabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Author
AlienVault
Tlp
white
References
["https://www.welivesecurity.com/en/eset-research/dynowiper-update-technical-analysis-attribution"]
Adversary
Sandworm
Pulse Id
697cfb85ac8b88be3162c26c
Threat Score
null

Indicators of Compromise

Ip

ValueDescriptionCopy
ip31.172.71.5

Domain

ValueDescriptionCopy
domainprogamevl.ru

Hash

ValueDescriptionCopy
hash5249503900c735425130477649872dfb
MD5 of 410c8a57fe6e09edbfebaba7d5d3e4797ca80a19
hash75fec5afb2deebab6dd9c16d9de35032
MD5 of 86596a5c5b05a8bfbd14876de7404702f7d0d61b
hash9d896e0e3e369c2edf1c8fb070f49c22
MD5 of 472ca448f82a7ff6f373a32fdb9586fd7c38b631
hasha727362416834fa63672b87820ff7f27
MD5 of 4ec3c90846af6b79ee1a5188eefa3fd21f6d4cf6
hashc4379da51e8b9e86ec3de934f9373f4a
MD5 of 69ede7e341fd26fa0577692b601d80cb44778d93
hashf5271a6d909091527ed9f30eafa0ded6
MD5 of 9ec4c38394ea2048ca81d48b1bd66de48d8bd4e8
hash410c8a57fe6e09edbfebaba7d5d3e4797ca80a19
hash472ca448f82a7ff6f373a32fdb9586fd7c38b631
hash4ec3c90846af6b79ee1a5188eefa3fd21f6d4cf6
hash4f8e9336a784a196353023133e0f8fa54f6a92e2
hash69ede7e341fd26fa0577692b601d80cb44778d93
hash86596a5c5b05a8bfbd14876de7404702f7d0d61b
hash9ec4c38394ea2048ca81d48b1bd66de48d8bd4e8
hash40a4b5e54fecce52c9d8ef5b2fa3973a3dd748c5bcedd7bde1154aa4a936c2e1
SHA256 of 410c8a57fe6e09edbfebaba7d5d3e4797ca80a19
hash60c70cdcb1e998bffed2e6e7298e1ab6bb3d90df04e437486c04e77c411cae4b
SHA256 of 86596a5c5b05a8bfbd14876de7404702f7d0d61b
hash648c2067ef3d59eb94b54c43e798707b030e0383b3651bcc6840dae41808d3a9
SHA256 of 9ec4c38394ea2048ca81d48b1bd66de48d8bd4e8
hash835b0d87ed2d49899ab6f9479cddb8b4e03f5aeb2365c50a51f9088dcede68d5
SHA256 of 4ec3c90846af6b79ee1a5188eefa3fd21f6d4cf6
hashbfda142bc5c44913eed9ef1cf2a8ad07b7a71312a26e4c7c519bf1a3fedeb6a0
SHA256 of 472ca448f82a7ff6f373a32fdb9586fd7c38b631
hashd1389a1ff652f8ca5576f10e9fa2bf8e8398699ddfc87ddd3e26adb201242160
SHA256 of 69ede7e341fd26fa0577692b601d80cb44778d93

Threat ID: 698083b8f9fa50a62f370564

Added to database: 2/2/2026, 11:00:08 AM

Last enriched: 2/2/2026, 11:15:50 AM

Last updated: 2/3/2026, 11:12:03 AM

Views: 38

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

External Links

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats