BitLocker Feature Installation via ServerManagerCmd or PowerShell (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-08-02
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 on-demand installation of the BitLocker Windows feature through ServerManagerCmd or Install-WindowsFeature, the enabling step ShrinkLocker performs on systems where BitLocker is absent before hijacking it to encrypt drives. Adversaries leverage the native BitLocker feature to lock victim data without dropping a custom encryptor, so this behavior warrants review on hosts where BitLocker deployment is unexpected.

Related detections9 linkedT1486 — drag to rearrange
Malicious Ransomware Encryption Extension x2anylock
Malicious Fivehands Go Encryptor Execution via Command Line Flags
Malicious SafePay Ransomware Encryptor Command-Line Execution
Malicious The Gentlemen Ransomware Encryptor via Distinctive CLI Flags
Malicious GigaWiper Ransomware File Extension .candy
Malicious Forced BitLocker Encryption for Extortion (via process_creation)
Malicious Volume Shadow Copy Deletion via Vssadmin
Malicious CACTUS Ransomware Note and Encrypted File Artifacts (via file_event)
Malicious Macaw Ransom Note or Encrypted File Written (via file_event)
BitLocker Feature Installation via ServerManagerCmd or PowerShell (via process_creation)
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.