Skip to content
whoAMI Attack Exploits AWS AMI Name Confusion

whoAMI Attack Exploits AWS AMI Name Confusion

First seen 17 Nov 2026, 17:13 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 17, 2026 at 17:14 UTC
  • •The whoAMI attack exploits AMI name confusion, affecting around 1% of AWS users.
  • •AWS internal systems were found vulnerable, prompting immediate fixes and the introduction of Allowed AMIs.
  • •Organizations must validate AMI sources and monitor deployments to mitigate risks.

The whoAMI attack, identified by Datadog Security Labs, exploits a naming pattern in Amazon Machine Images (AMIs) that allows attackers to execute code within vulnerable AWS accounts. This vulnerability affects approximately 1% of organizations using AWS, enabling attackers to potentially access thousands of accounts. AWS confirmed that even internal non-production systems were vulnerable, which led to a prompt fix. The attack leverages misconfigurations in how AMIs are retrieved, particularly in CI/CD pipelines that do not verify image owners. AWS introduced Allowed AMIs as a defense mechanism to mitigate this risk, allowing users to create a whitelist of trusted AMI providers. Organizations are urged to validate image provenance and monitor workloads to prevent exploitation. The vulnerability is classified under the shared responsibility model, placing the onus on customers to secure their configurations. Datadog has also released a tool, whoAMI-scanner, to help identify vulnerable patterns in code.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2024-08-01
whoAMI attack pattern identified
Datadog Security Labs discovered a naming pattern in AMIs that could be exploited for code execution in AWS accounts.
securitylabs.datadoghq.com
2024-12-01
AWS announces Allowed AMIs
AWS introduced Allowed AMIs to help users create a whitelist of trusted AMI providers, mitigating the whoAMI attack risk.
securitylabs.datadoghq.com

More articles in this cluster (4)

Following this threat?

Track AWS in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

How can I check if my organization is affected?
Review your CI/CD pipelines for AMI retrieval patterns that do not verify image owners.
What steps should I take to mitigate this risk?
Implement Allowed AMIs and regularly validate the provenance of your AMIs.
Is there a tool to help identify vulnerabilities?
Yes, Datadog has released the whoAMI-scanner to detect untrusted AMI usage in code.