Malicious AWS Cross-Account AssumeRole With Suspicious Session Names via CloudTrail (via aws)

PremiumReviewedSigma · High · v1
Product
aws
Service
cloudtrail
Author
HuntRule
Published
2026-10-28
Updated
2026-10-28

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Execution

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule detects AWS STS AssumeRole calls that use session names tied to an AI assisted intrusion which escalated to administrator access. The operators assumed the organization account access role with session names such as pwned escalation and claude-session while pivoting across accounts. Role session names of this kind indicate hands on keyboard privilege escalation.

Related detections9 linkedT1078.004 — drag to rearrange
Suspicious Okta SSO Access to Many Applications in Short Window
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious M365 Password Spraying via Azure PowerShell AppId from Quad7 Botnet
Suspicious AWS Instance Access or Export via SSH Key or Export Task
Suspicious Azure OpenAI Model Enumeration and Deployment Creation (via azure)
Suspicious Azure Cognitive Services Account Key Enumeration via ListKeys (via azure)
Malicious Business Email Compromise OAuth Application Sign-In via Entra ID Service Principal (via azure)
Suspicious AWS API Call from TruffleHog Credential Scanner User Agent
Suspicious Compute Instance Metadata Modification in GCP
Malicious AWS Cross-Account AssumeRole With Suspicious Session Names via CloudTrail (via aws)
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.