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
Possible Akira Ransomware Note or Encrypted Extension Creation
Malicious Storm-2603 Ransom Note File Creation
Possible Ransomware Note or Encrypted File Extension Creation
BitLocker Feature Activation on Multiple Hosts - Native (via bitlocker)
FunkSec Ransomware Encryption Artifacts via funksec Extension and Markdown Ransom Note (via file_event)
INC Ransomware Ransom Note INC-README Written to Disk (via file_event)
Malicious DEVMAN Ransomware Encrypted File and Note Artifacts
Malicious Akira Ransomware Encrypted File Extension via File Event
Malicious BitLocker Abuse for Ransomware via PowerShell (via ps_script)
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.