AI-Enabled Cloud and ML Pipeline Attacks via Exposed Credentials and Data Poisoning

Security research and incident response reporting highlighted how AI-enabled tactics are accelerating cloud compromise and expanding the blast radius into ML systems. Sysdig described an incident in which attackers used exposed credentials in public AWS S3 buckets to escalate from initial access to full administrative privileges in under 10 minutes, then moved laterally across identities, exfiltrated data from multiple AWS services, and injected malicious code into AWS Lambda. The activity also included attempts to monetize access by running AI workloads through Amazon Bedrock and attempting GPU hijacking in EC2, creating potential for significant cloud cost impact; AWS characterized the root cause as S3 misconfiguration/credential exposure rather than an AWS infrastructure flaw.

Mitiga reported a separate real-world investigation where a threat actor exploited a path traversal flaw in an AI-enabled file upload/summarization web application to overwrite production training data in an S3 bucket feeding an automated SageMaker retraining pipeline. The poisoned dataset introduced subtle label inconsistencies and a trigger pattern that, after retraining and deployment, enabled the attacker to reliably induce anomalous model behavior with crafted inputs—effectively a persistent training data poisoning compromise of a production AI endpoint. In contrast, Kiuwan’s post is primarily a general advisory on AI development supply-chain visibility risks (e.g., unvetted dependencies introduced by LLM coding assistants) and does not describe the same specific incidents or provide incident-specific indicators.