Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

Wiper Campaign

← Back to Glossary
By NHI Mgmt Group Updated October 12, 2026 Domain: Threats, Abuse & Incident Response

A wiper campaign is a destructive intrusion designed to delete or corrupt data, disrupt operations, and make systems difficult to restore. Unlike financially motivated ransomware, the attacker’s objective is damage and denial of service, so recovery assurance and containment become primary controls.

What a wiper campaign means in practice

A wiper campaign is not just “destructive malware.” It is a deliberate intrusion pattern built to erase, corrupt, or render data unusable, often while weakening recovery paths so the outage lasts longer than the compromise itself.

The practical distinction is intent. In ransomware, the attacker usually wants leverage for payment; in a wiper campaign, the objective is denial of service, business disruption, and loss of confidence in the organisation’s ability to restore systems cleanly.

How a wiper campaign works

Wiper activity often starts like other intrusions, with stolen credentials, remote access, or trusted administrative channels, then pivots into destructive actions once the attacker has enough reach. The destructive step may target files, databases, backups, boot records, virtual machines, or endpoint management systems.

Because the campaign is designed to be disruptive rather than discreet, the attacker may combine rapid propagation with aggressive deletion or corruption. In many cases, speed matters more than stealth, although initial access, privilege abuse, and lateral movement still determine how widely the wipe can spread.

Why recovery is the central challenge

The hardest part of a wiper campaign is often not the initial blast radius, but whether recovery can be trusted. If backups are reachable, management planes are compromised, or restoration tooling is also affected, the organisation may have data copies but no safe path to bring them back.

This is why the Stryker Microsoft Intune wiper attack case study is so relevant: once privileged cloud management access is abused, destructive actions can scale quickly across many managed endpoints. Recovery planning must therefore include isolation, control-plane resilience, and confidence that restoration points were not tampered with.

Defensive priorities for destructive intrusion campaigns

Defence against wiping is mainly about limiting blast radius and preserving trustworthy recovery options. Segmented administration, protected backup paths, immutable or offline copies, and tightly controlled privileged access all matter because they reduce the attacker’s ability to convert access into irreversible damage.

Detection also matters, but mostly as a way to shorten the time between compromise and containment. If destructive activity is already underway, every minute affects the amount of data, infrastructure, and operational state that can still be preserved.

Risk and Threat Considerations

Wiper campaigns create outsized operational risk because the harm is immediate, visible, and often difficult to undo. They are especially dangerous when they target management infrastructure, backup systems, or shared credentials, because a single compromise can cascade into enterprise-wide destruction.

Failure mechanism: Attackers gain enough privileged access to issue deletion, corruption, or mass-disable actions before defenders can isolate systems or protect recovery assets.

Impact: Organisations may lose data, endpoints, service availability, and restoration confidence at the same time, turning a security incident into a prolonged business interruption.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0RC.RP-01 — Recovery PlanningWiper campaigns directly stress recovery planning after destructive impact.
PR.AA-05 — Access Permissions and AuthorizationsWiper campaigns often depend on abused privileged access to execute destructive actions.
Recommendation — Validate restoration assumptions and rehearse recovery from destructive compromise. Enforce least-privilege access to reduce blast radius from compromised accounts.
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeDestructive intrusion severity depends on whether attackers can reach powerful functions.
CP-9 — System BackupBackup integrity and recoverability are central when attackers delete or corrupt production data.
Recommendation — Restrict administrative privileges so compromise cannot trigger mass destruction. Protect backups with isolation and restoration testing against destructive attacks.
CIS Controls v8CIS-11 — Data RecoveryWiper campaigns are fundamentally a recovery and restoration problem.
Recommendation — Maintain recoverable backups and test restoration against destructive incidents.

Practitioner Guidance

What to watch for: Treat any sign of bulk deletion, backup tampering, abnormal admin activity, or sudden management-plane changes as a potential precursor to destructive action. In wiper scenarios, the difference between “contained” and “catastrophic” is often whether the destructive path is interrupted before it reaches core systems.

Practitioner takeaway: Recovery assurance is not a post-incident luxury, it is part of the control plane you must protect before a wiper campaign ever starts.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 12, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org