Malicious Azure Storage and Compute Destruction via Key Listing and Snapshot Deletion

PremiumReviewedSigma · Medium · v1
Product
azure
Service
activitylogs
Author
HuntRule
Published
2026-05-06
Updated
2026-08-28

ATT&CK techniques

Impact
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

What it detects

This rule detects Azure operations that list storage account keys and delete storage or compute snapshots. Microsoft observed Storm-0501 combining these to exfiltrate then destroy cloud data and backups for extortion. Bulk key retrieval followed by resource and snapshot deletion is destructive impact activity, so these operations should be treated as a possible cloud ransomware event.

Related detections9 linkedT1486 — drag to rearrange
RedCurl QWCrypt Ransomware Execution with Hyper-V Targeting Flags
Malicious Azure Deletion of Resource Locks and Immutability Policies
Malicious BitLocker Encryption With Shadow Copy Removal via manage-bde (via process_creation)
Windows process activity matching WannaCry executables and ransom note text
Possible Akira Ransomware Note or Encrypted Extension Creation
Malicious Storm-2603 Ransom Note File Creation
Possible Ransomware Note or Encrypted File Extension Creation
Suspicious Symbolic Link Evaluation Enabled via fsutil by RansomHub Ransomware
Suspicious Volume Shadow Copy Deletion via PowerShell WMI by Akira Ransomware
Malicious Azure Storage and Compute Destruction via Key Listing and Snapshot Deletion
Pivot detection · T1486 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.