AWS CloudTrail SQL: Anomalous Cross-Account STS AssumeRole from Compromised AI Containers — Threat Hunting Query
Hunting Telemetry & Platform Metadata
Section titled “Hunting Telemetry & Platform Metadata”| Evaluation Dimension | Observed Telemetry / Attribute | Epistemic Status |
|---|---|---|
| Hunting Query Identifier | HUNT-CLOUDTRAIL-IAM-ROLE-PIVOT | Canonical Hunt Node |
| Target SIEM / Analytics Platform | AWS CloudTrail Lake / Athena | Telemetry Ingestion Engine |
| Platform Syntax Dialect | cloudtrail_sql | Query Language Standard |
| Telemetry & Log Sources | AWS CloudTrail Event Logs, VPC Flow Logs | Data Sensor Sources |
| Targeted Adversary Syndicates | ShinyHunters | Threat Attribution |
| Associated Weaponized CVEs | CVE-2026-101861 | Vulnerabilities Targeted |
| Associated Intrusion Campaigns | Operation PeopleSoft Infiltration 2026 | Monitored Campaign |
| Analytical Confidence | 96% | Hypothesis Validity Score |
| Primary Evidence Sources | SRC-MANDIANT-GOOGLE, SRC-CISA-KEV | Intelligence Attestation |
Threat Hunting Hypothesis
Section titled “Threat Hunting Hypothesis”Following host escape on cloud worker nodes, threat actors assume high-privilege IAM roles to persist across multiple cloud subscriptions and exfiltrate proprietary model weights.
Adversary operations frequently slip through standard alerting thresholds by leveraging legitimate binaries or abusing valid service configurations. Proactive threat hunting formulates precise hypotheses based on known architectural chokepoints and queries historical telemetry to unearth stealthy intrusion footholds.
Production Hunting Query
Section titled “Production Hunting Query”SELECT eventTime, userIdentity.arn as caller_arn, eventSource, eventName, requestParameters, responseElements, sourceIPAddressFROM aws_cloudtrail_lakeWHERE eventName = 'AssumeRole' AND sourceIPAddress NOT IN ('10.0.0.0/8', '172.16.0.0/12', '192.168.0.0/16') AND userIdentity.principalId LIKE '%langflow%'ORDER BY eventTime DESCLIMIT 50;Triage Guidance & Investigation Protocol
Section titled “Triage Guidance & Investigation Protocol”Validate the external IP initiating AssumeRole. If unauthorized, immediately revoke the assumed role session tokens and attach an explicit Deny policy to the target IAM role.
- Verify Timeline Baseline: Review the first seen and last seen timestamps of returned events to distinguish chronic benign traffic from sudden operational spikes.
- Examine Parent-Child Lineage: Ensure that all parent processes match authorized deployment manifests and do not conceal unexpected interactive utilities.
- Inspect Network Pivots: Cross-reference communicating source and destination IP addresses against Hermes Adversary Infrastructure endpoints.