Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Wiper malware exists to destroy. There is no key, no negotiation, and no decryptor, which means the only thing standing between an organisation and the loss is its backups.

What Is Wiper Malware?
Wiper malware is written to destroy data irrecoverably. It overwrites files, corrupts the master boot record, damages partition tables, or encrypts with a key that is discarded immediately. The distinguishing feature is the absence of a recovery path: no key is retained, no payment restores anything, and in several notable cases the ransom note was pure theatre, added to delay the victim’s understanding of what had happened.
Because there is no revenue model, wipers are almost always deployed for sabotage or disruption, by state-aligned groups or by attackers whose objective is damage rather than profit.
Several of these spread far beyond their intended targets. NotPetya reached organisations with no Ukrainian operations through corporate networks and shared infrastructure, which is the reason it belongs in every UK board discussion about geopolitical risk.
The techniques are deliberately simple, because destruction is easy and reliability matters more than elegance. Wipers overwrite file contents with random or fixed data, destroy boot records and partition tables so the system cannot start, delete volume shadow copies and backup catalogues, and corrupt the master file table so that the data remains on disk but is no longer addressable. Many use legitimate signed drivers for raw disk access, which bypasses file system protections and lends the activity a trusted signature.
Distribution is usually internal rather than external. Attackers obtain domain administrator rights first, then push the payload through Group Policy, a software deployment tool, or a remote execution utility, so the destruction happens everywhere at once. That dependency is also the opportunity: the privilege escalation and lateral movement that precede it take days and are detectable.
Ransomware planning quietly assumes a decision point. There is a counterparty, a negotiation, perhaps a decryptor. A wiper removes all of that, and with it several assumptions worth testing before the day they fail:
Set recovery objectives against total loss rather than partial failure, and know which processes must run during the rebuild. The planning overlaps with recovery objectives generally, but the scale assumption is different. At Privia Security, our emergency action plan services test these assumptions against a destructive scenario rather than a conventional outage.
Ransomware encrypts data and retains the key so it can be sold back; a wiper destroys data with no recovery path. Some wipers display ransom notes deliberately, so the two are indistinguishable at first sight. The practical difference is that payment cannot help, which makes offline backups and tested restoration the only route back to operation.
Usually not. Overwritten sectors are gone, and forensic recovery cannot retrieve data that no longer exists physically. Partial recovery is occasionally possible where the wiper only destroyed file system metadata or overwrote the first portion of each file, leaving remnants that carving tools can reassemble. Plan for total loss, and treat any partial recovery as a bonus.
Directly targeted attacks concentrate on specific geopolitical conflicts, but collateral damage is the real exposure. NotPetya reached organisations with no connection to its intended target through shared networks and suppliers, costing several of them hundreds of millions. Any organisation with operations, subsidiaries, or suppliers in an affected region should treat destructive attack as a scenario worth planning for.
Backups that an attacker holding domain administrator rights cannot reach or delete, meaning offline, immutable, or in a separate security domain with independent credentials. Everything else follows from having data to restore. Pair it with a rehearsed restoration process at full scale, because backups nobody has tested at that scale regularly fail when they are finally needed.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.