Rise of Data-Wiping Attacks Using LoTL

Data-Wiping Attacks on the Rise, Abusing Legitimate Admin Tools

CRITICAL
July 22, 2026
5m read
CyberattackThreat ActorCloud Security

Impact Scope

Affected Companies

Stryker

Industries Affected

HealthcareManufacturingTechnology

Related Entities

Threat Actors

Handala Hack Team

Products & Tech

Microsoft Intune

Other

StrykerSource LogisticsOutpost24Iran

Full Report

Executive Summary

A dangerous trend is emerging in the threat landscape: data-wiping attacks where the primary goal is destruction, not financial extortion. A July 22, 2026 warning from Source Logistics highlighted this threat, citing the March 2026 cyberattack against medical technology company Stryker as a prime example. In that incident, the Iranian hacktivist group Handala Hack Team claimed to have gained Global Administrator access to Stryker's Microsoft environment and used the legitimate Microsoft Intune mobile device management (MDM) platform to wipe an estimated 80,000 devices. This attack demonstrates a potent 'living off the land' (LotL) strategy, leveraging trusted enterprise tools to cause catastrophic damage, bypassing traditional malware-based defenses entirely.

Threat Overview

The Stryker incident, which the company confirmed was not a ransomware attack, represents a tactical shift. Instead of encrypting data and demanding a ransom, the attackers aimed for maximum disruption and data destruction. The Handala Hack Team, a hacktivist group, claimed responsibility on March 11, 2026. Their alleged method was to abuse Global Administrator privileges to issue remote wipe commands via Microsoft Intune over a three-hour period.

This LotL approach is highly effective because it uses the organization's own management tools against it. The malicious commands are signed, authenticated, and delivered through trusted channels, making them extremely difficult to block with conventional security measures. Research from Outpost24 supports the initial access vector, revealing that 278 credentials linked to the stryker.com domain had been compromised in the months prior, suggesting the attackers gained their initial foothold through stolen credentials rather than malware.

Technical Analysis

This attack is a textbook case of T1485 - Data Destruction. The novelty lies in the execution method, which is a sophisticated abuse of legitimate functionality.

  1. Initial Access: The attackers likely gained initial access by using one of the 278 previously compromised credentials, possibly through password spraying or credential stuffing attacks.
  2. Privilege Escalation: They escalated their privileges within the Microsoft environment to achieve Global Administrator status, the highest level of administrative rights. This likely involved further credential theft or exploitation of misconfigurations (T1078.004 - Cloud Accounts).
  3. Destructive Action: With Global Admin rights, the attackers accessed the Microsoft Intune portal and used its built-in functionality to issue a mass remote wipe command to all enrolled devices. This is an abuse of the DeviceManagementManagedDevices API and falls under the broader technique of T1562.001 - Disable or Modify Tools, where the 'tool' is the operating system on the endpoint.

Because the wipe command is a legitimate function of Intune, endpoint protection platforms (EPP) would not flag it as malicious. The only way to detect it is by monitoring the administrative plane itself.

Impact Assessment

The impact of a mass data-wiping attack is catastrophic and potentially more damaging than a ransomware attack. There is no option for recovery by paying a ransom; the data is permanently gone. For a company like Stryker, this could mean the loss of critical corporate data, intellectual property, and operational capabilities across 80,000 endpoints. The recovery process would be immensely costly and time-consuming, requiring the re-imaging and re-provisioning of every affected device. For the supply chain industry, such an attack could halt logistics, manufacturing, and distribution, with far-reaching economic consequences.

IOCs — Directly from Articles

No specific Indicators of Compromise (IOCs) were mentioned in the source articles.

Cyber Observables — Hunting Hints

Detecting this type of LotL attack requires monitoring the administrative control plane:

Type
log_source
Value
Microsoft Entra ID Audit Logs
Description
The source for all administrative activity in the Microsoft cloud environment.
Context
Ingest into a SIEM.
Type
api_endpoint
Value
POST /deviceManagement/managedDevices/wipe
Description
The Graph API call to remotely wipe a device. A large number of these calls in a short period is a critical indicator.
Context
Microsoft 365 audit logs, CASB logs.
Type
event_id
Value
Wipe (in Intune Audit Logs)
Description
The specific event name for a remote wipe action initiated from Intune.
Context
Intune audit logs.
Type
user_account_pattern
Value
A new Global Administrator account is created and used almost immediately
Description
A common attacker TTP is to create a new admin account for their activities.
Context
Microsoft Entra ID audit logs.

Detection & Response

  • Admin Activity Monitoring: Implement stringent monitoring and alerting on all Global Administrator activity within Microsoft 365/Entra ID. Any sensitive action, such as issuing a mass wipe command, should require a multi-person approval workflow or trigger a high-priority, automated response (D3-DAM: Domain Account Monitoring).
  • Behavioral Analytics: Use UEBA (User and Entity Behavior Analytics) to detect anomalous administrative behavior, such as a Global Admin logging in from a new location and immediately performing destructive actions.
  • Threshold-Based Alerting: Configure alerts for when a certain threshold of critical actions (like device wipes) is crossed in a specific time frame.

Mitigation

  • Principle of Least Privilege (PoLP): Strictly limit the number of Global Administrator accounts. Use Privileged Identity Management (PIM) to provide just-in-time (JIT) administrative access that is time-bound and requires approval (M1026 - Privileged Account Management).
  • Break-Glass Accounts: Maintain a small number of emergency 'break-glass' accounts that are not used for daily operations and are heavily monitored.
  • Phishing-Resistant MFA: Protect all administrative accounts with phishing-resistant MFA (e.g., FIDO2 security keys) to prevent credential theft (M1032 - Multi-factor Authentication).
  • Layered Defense: As recommended by Source Logistics, implement a layered defense strategy that includes strong credential hygiene, phishing awareness, and granular access controls to prevent attackers from gaining the elevated privileges needed to launch such an attack.

Timeline of Events

1
March 11, 2026
The Handala Hack Team claims responsibility for the cyberattack against Stryker.
2
July 22, 2026
This article was published

MITRE ATT&CK Mitigations

Implement just-in-time (JIT) access using tools like PIM to drastically limit the number of standing privileged accounts.

Mapped D3FEND Techniques:

Enforce phishing-resistant MFA (e.g., FIDO2 keys) for all administrative accounts to prevent credential compromise.

Mapped D3FEND Techniques:

Implement comprehensive auditing and alerting for all administrative actions within cloud management platforms like Intune.

Mapped D3FEND Techniques:

Timeline of Events

1
March 11, 2026

The Handala Hack Team claims responsibility for the cyberattack against Stryker.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

Data WiperLiving off the LandStrykerHandala Hack TeamMicrosoft IntuneSupply Chain

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.