[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f4M3GASCgvxC9qx-Q1XB0i8giQdgYGwQWfv-OBoJQQRE":3},{"article":4,"iocs":54},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"full_text":11,"url":12,"image_url":13,"published_at":14,"ingested_at":15,"relevance_score":16,"entities":17,"category_id":33,"category":34,"article_tags":38},"2953c44d-9d2a-4913-87d3-83d4d32e95af","The Sub-10-Minute Cloud Takeover: How Exposed IAM Keys, Misconfiguration and AI Are Rewriting the Rules of Cloud Breaches","the-sub-10-minute-cloud-takeover-how-exposed-iam-keys-misconfiguration-and-ai-ar-893985","Key Takeaways Two real-world cloud attacks reached meaningful impact in less than ten minutes despite pursuing entirely different objectives. Both attackers treated the environment as a connected system, using existing permissions and relationships to expand their reach. Reconnaissance increasingly focuses on understanding access and capability rather than discovering vulnerable assets. AI is compressing the gap […]","Two real-world cloud attacks demonstrated rapid compromise timelines: one crypto-mining attack reached meaningful impact in 10 minutes using compromised AWS credentials, while an AI-assisted attack exploited an exposed access key in an S3 bucket to escalate privileges across 19 AWS principals and abuse Amazon Bedrock in under 8 minutes. Both attacks leveraged the cloud's inherent efficiency and accumulated permissions, with reconnaissance focused on understanding access capabilities rather than discovering vulnerabilities. AI is accelerating the attack timeline by compressing the gap between discovery, decision-making, and execution.","Attackers exploit exposed IAM keys to compromise AWS in under 10 minutes using AI-assisted techniques.","Table of ContentsTwo Real-World Attacks. One Emerging PatternCloud Services Were Designed to Accelerate Work. They Also Accelerate AuthorityThe 10-Minute Crypto Mining AttackThe 8-Minute AI-Assisted AttackWhat Modern Cloud Reconnaissance Looks LikeWhy AI Attacks Happen So FastHow Both Attacks Share the Same Systemic FailuresUnderstanding Risk Before It Moves: From Exposure to ActivityConclusionFrequently Asked Questions (FAQs) Key Takeaways Two real-world cloud attacks reached meaningful impact in less than ten minutes despite pursuing entirely different objectives. Both attackers treated the environment as a connected system, using existing permissions and relationships to expand their reach. Reconnaissance increasingly focuses on understanding access and capability rather than discovering vulnerable assets. AI is compressing the gap between discovery, decision-making, and execution for cloud attackers. The interval between initial access and operational impact is shrinking, placing greater emphasis on visibility before activity begins. Two Real-World Attacks. One Emerging Pattern Cloud environments were built to make useful work easier. Increasingly, they are doing the same for attackers. Recent incidents illustrate this point. In one attack, compromised AWS credentials enabled attackers to deploy cryptocurrency mining infrastructure across EC2 and ECS resources within ten minutes of gaining access. In another attack, an exposed AWS access key discovered in a publicly accessible S3 bucket enabled privilege escalation, movement across nineteen AWS principals, unauthorized use of Amazon Bedrock models, and broader cloud resource abuse in less than eight minutes. One attacker wanted compute. The other wanted AI. The objectives were different, but the timelines were not. Both progressed with remarkable efficiency once access had been established. The similarity suggests that the story is not about cryptocurrency or AI. It’s about the environment itself and how modern cloud systems translate access into capability. Cloud Services Were Designed to Accelerate Work. They Also Accelerate Authority The cloud’s greatest strength has always been its ability to remove friction. Infrastructure can be provisioned in minutes rather than weeks. New applications can be deployed through APIs rather than procurement cycles. AI became consumable through APIs. Capabilities that once required weeks of coordination can now be accessed in seconds. Organizations benefit from speed because cloud platforms make capabilities easier to access. That same efficiency applies to permissions. A modern cloud identity often serves as a gateway to dozens of interconnected services, workloads, repositories, and automation workflows. A single role can provision infrastructure, access sensitive data, invoke AI models, modify serverless functions, retrieve secrets, and establish additional trust relationships. Few objects inside a cloud environment carry comparable influence. This characteristic does not make cloud platforms inherently less secure, but it does change how risk manifests. Operational authority accumulates over time through application integrations, business requirements, temporary exceptions, inherited permissions, and expanding cloud adoption. By the time an identity becomes compromised, it may already represent years of accumulated access decisions. The resulting exposure reflects the gradual concentration of authority across an increasingly interconnected environment. The 10-Minute Crypto Mining Attack In early November 2025, Amazon observed a crypto-mining campaign targeting AWS environments using compromised IAM credentials. The attackers authenticated using valid credentials and immediately began evaluating the resources available to them. Shortly after gaining access, they used APIs such as GetServiceQuota to understand the operational limits of the environment before provisioning resources. The activity resembled planning more than exploitation. Resource enumeration revealed available infrastructure, while existing permissions exposed opportunities to provision and expand. Within ten minutes, mining workloads were operational. The technical progression itself was not especially novel. IAM permissions enabled visibility into resources and quotas. EC2 and ECS provided compute capacity. Lambda-related permissions supported persistence. Each service contributed a specific capability. The speed of the attack emerged from how easily those capabilities could be reached through a single compromised identity. The diagram below shows how Qualys visualizes an attack path, mapping the progression from an initial credential exposure through reconnaissance and resource enumeration to the point where critical assets are impacted. This visualization helps security teams understand how an attacker advances through the environment and where intervention is most effective. Qualys CDR detects suspicious activity at the earliest stages of the attack path, providing the visibility needed to identify and investigate threats before they escalate. When malicious activity is detected, Qualys QFlow can automatically initiate response actions such as revoking compromised credentials and blocking access to affected resources. By disrupting the attack before it reaches its objective, Qualys enables organizations to move from reactive incident response to proactively breaking the attack chain. Viewed individually, none of these services represents unusual risk. Organizations rely on them every day to operate cloud environments at scale. Viewed collectively, they reveal how operational authority is distributed across cloud-native services and how quickly it can be exercised once access is obtained. The incident offers a useful reminder that cloud attacks increasingly succeed not because individual services fail, but because the relationships between those services create pathways to broader control. The 8-Minute AI-Assisted Attack A second intrusion compressed the timeline even further. An AWS access key exposed within a publicly readable S3 bucket provided an entry point into a cloud environment. Within eight minutes, access was followed by movement across 19 AWS principals, Lambda code manipulation, Secrets Manager enumeration, Bedrock abuse, and the suppression of model invocation logging. The sequence reveals how quickly attackers can expand visibility, access, and operational control once an initial foothold has been established. How Authority Expanded The attack unfolded through a sequence of interconnected capabilities: The exposed credential revealed available roles and access paths Lambda permissions enabled additional control and privilege escalation Secrets Manager exposed further credentials and operational context Amazon Bedrock provided access to foundation model services Model invocation logging was disabled, reducing visibility into subsequent activity Each step expanded the attacker’s understanding of the environment while simultaneously increasing the authority available to them. What began as a single exposed credential evolved into access across identities, services, and AI resources because each permission revealed additional opportunities for expansion. The introduction of AI services adds another layer to that system. Foundation models become resources that can be consumed, manipulated, or monetized once access has been established. As organizations expand their adoption of generative AI, identity governance extends beyond infrastructure, workloads, and data into the capabilities of the models themselves. The credential provided access, the environment provided context, and the permissions provided momentum. What Modern Cloud Reconnaissance Looks Like Cloud reconnaissance has evolved alongside cloud architecture. Traditional attackers focused on discovering hosts, ports, applications, and vulnerabilities. Modern cloud attackers often begin by understanding authority. The in","https:\u002F\u002Fblog.qualys.com\u002Fproduct-tech\u002F2026\u002F07\u002F27\u002Fthe-sub-10-minute-cloud-takeover-how-exposed-iam-keys-misconfiguration-and-ai-are-rewriting-the-rules-of-cloud-breaches","https:\u002F\u002Fik.imagekit.io\u002Fqualys\u002Fwp-content\u002Fuploads\u002F2026\u002F07\u002FBlog-Images-1080x1080.Cloud_.Agent_.2025.Updates-13-2.png","2026-07-27T15:00:00+00:00","2026-07-27T16:00:25.849552+00:00",9,[18,21,24,26,28,30],{"name":19,"type":20},"Amazon","vendor",{"name":22,"type":23},"AWS","product",{"name":25,"type":23},"Amazon Bedrock",{"name":27,"type":23},"EC2",{"name":29,"type":23},"ECS",{"name":31,"type":32},"IAM","technology","c70f3a41-2f0c-4608-870d-b8cbcd8be076",{"id":33,"icon":35,"name":36,"slug":37},null,"Cloud Security","cloud-security",[39,44,49],{"category":40},{"id":41,"icon":35,"name":42,"slug":43},"2c8f44d4-b56e-47cf-9677-04f22c9ee78d","Identity & Access","identity-access",{"category":45},{"id":46,"icon":35,"name":47,"slug":48},"839da5c1-3c34-47e2-9499-f7201640e3ac","AI Security","ai-security",{"category":50},{"id":51,"icon":35,"name":52,"slug":53},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[55],{"type":56,"value":57,"context":58},"malware","Crypto-mining infrastructure","Deployed across AWS EC2 and ECS resources in November 2025 attack"]