Suspicious AWS SES CreateEmailIdentity Following Key Compromise (Cloud Email Abuse)

PremiumReviewedSigma · Medium · v1
Product
aws
Service
cloudtrail
Author
HuntRule
Published
2026-11-04
Updated
2026-11-04

ATT&CK techniques

Initial Access → Collection
  1. Recon

  2. Resource Dev

  3. Execution

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. C2

  8. Exfiltration

  9. Impact

What it detects

This rule detects SES CreateEmailIdentity CloudTrail events that register new sending identities, an action the cloud email takeover campaign performed to stand up its phishing infrastructure. It matters because attackers with leaked keys create fresh verified identities to send mail that appears to originate from the victim tenant.

Related detections9 linkedT1078.004 — drag to rearrange
Suspicious AWS SES Production Access Request via PutAccountDetails (Cloud Email Abuse)
Suspicious ECS ExecuteCommand Lateral Movement via SSM in AWS CloudTrail (via cloudtrail)
Malicious Bapak AWS EKS CreateCluster With Known Cluster Name via CloudTrail
Malicious AWS IAM User Creation With Known Threat Actor Names
Suspicious AWS API Activity From S3 Browser Client User-Agent
Suspicious AWS API Activity From WinSCP Client User-Agent
Suspicious EKS Access Entry Creation via CloudTrail
Suspicious Azure CLI Service Principal Login with Inline Secret
Suspicious AWS Console Login Without MFA
Suspicious AWS SES CreateEmailIdentity Following Key Compromise (Cloud Email Abuse)
Pivot detection · T1078.004 · 9 related

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