Malicious S3 Object Encryption for Ransom via SSE-C

PremiumReviewedSigma · High · v1
Product
aws
Service
cloudtrail
Author
HuntRule
Published
2026-06-17
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 an S3 PutObject call that supplies a customer provided encryption key using server side encryption with customer keys, the core primitive of the AWS S3 SSE-C ransom scenario emulated by Elastic. By overwriting objects with a key only the attacker holds the adversary makes bucket data unrecoverable to the owner and demands payment. SSE-C on writes is uncommon in most environments and can indicate destructive ransom activity.

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)
Malicious S3 Object Encryption for Ransom via SSE-C
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.