Suspicious Bedrock AgentCore Runtime Invocation on Wildcard Resources (via aws)

PremiumReviewedSigma · Low · v1
Product
aws
Service
cloudtrail
Author
HuntRule
Published
2026-06-10
Updated
2026-08-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 Bedrock AgentCore code interpreter and agent runtime invocations that, in the Agent God Mode scenario, are abused through wildcard IAM permissions to execute code across agent boundaries. Invocation of these runtimes by unexpected principals can indicate exploitation of excessive privileges for arbitrary execution in the AI environment.

Related detections9 linkedT1078.004 — drag to rearrange
Possible Credential Stuffing Blocked by Conditional Access in Microsoft 365
Suspicious SES Account Sending Enablement and Identity Verification via CloudTrail
Possible Stolen AWS Credential Validation via STS GetCallerIdentity
Suspicious AWS Federated Console Login From Programmatic Credentials
Suspicious M365 Legacy Authentication via BAV2ROPC Client via m365
Suspicious STS AssumeRole With Exfil Session Name via CloudTrail (via cloudtrail)
Suspicious AWS Console Login Without MFA
Suspicious Cloud Sign-In From an Anonymizer or High-Risk Session (via signinlogs)
Suspicious Entra Sign-In to OfficeHome with axios User Agent
Suspicious Bedrock AgentCore Runtime Invocation on Wildcard Resources (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.