Compromised Qubole IAM Keys Enable Attackers to Harvest Data Across Multiple AWS Clients
Security researchers have uncovered a coordinated intrusion in which threat actors leveraged stolen identity and access management (IAM) credentials belonging to a Qubole big data platform to infiltrate a range of Amazon Web Services (AWS) environments. By exploiting the trust relationship between Qubole's AWS account and its customers' cloud resources, the attackers were able to move laterally and extract data from several unrelated organizations.
The breach originated from the compromise of IAM keys associated with Qubole's own AWS account. Those keys grant privileged access to the underlying cloud infrastructure that powers the data‑processing service offered by Qubole. Because many enterprises integrate Qubole directly into their AWS environments, the stolen credentials effectively opened a backdoor into each client’s cloud tenancy.
Once inside, the intruders employed typical cloud‑native techniques: enumerating resources, assuming roles across accounts, and copying data from storage buckets and databases. The exfiltration was conducted in a stealthy manner, using legitimate API calls to avoid triggering conventional security alerts. Analysts observed that the attackers targeted a variety of data types, suggesting an interest in both proprietary business information and potentially sensitive personal data.
Industry experts note that the incident highlights a broader risk inherent in the shared‑responsibility model of cloud services. While cloud providers secure the underlying hardware and hypervisor, customers remain responsible for protecting their access credentials and the permissions they grant. When a third‑party service like Qubole is granted extensive privileges, a compromise of its own credentials can cascade into multiple downstream breaches.
In response to the findings, Qubole has issued a statement confirming that it is working with affected customers and security partners to rotate compromised keys and reinforce its credential management practices. AWS has also reminded users to employ best‑practice controls such as least‑privilege policies, regular key rotation, and the use of AWS Identity Center or external identity providers for tighter access governance.
The episode serves as a reminder for organizations to audit third‑party integrations regularly, monitor for anomalous cross‑account activity, and implement robust detection mechanisms for credential misuse. As cloud adoption continues to expand, the security community expects that similar supply‑chain style attacks will become more common, underscoring the need for vigilant, layered defenses across the entire cloud ecosystem.
Comments (0)
Be the first to comment.
Join the discussion