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.
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.
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.
T1078.004 - Cloud Accounts).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.
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.
No specific Indicators of Compromise (IOCs) were mentioned in the source articles.
Detecting this type of LotL attack requires monitoring the administrative control plane:
Microsoft Entra ID Audit LogsPOST /deviceManagement/managedDevices/wipeWipe (in Intune Audit Logs)Implement just-in-time (JIT) access using tools like PIM to drastically limit the number of standing privileged accounts.
Enforce phishing-resistant MFA (e.g., FIDO2 keys) for all administrative accounts to prevent credential compromise.
Mapped D3FEND Techniques:
The Handala Hack Team claims responsibility for the cyberattack against Stryker.

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.
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.
Help others stay informed about cybersecurity threats
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.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
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 detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.