Your Cloud Vendor Has Access. What Happens When Its Credentials Are Compromised?
An attack involving Qubole's AWS integration credentials exposed a weakness in how organisations manage trusted third-party access. The incident shows why cloud security reviews must include the identities and permissions connecting external platforms to internal environments.
.png)
On 9 November 2026, security researchers published findings about a supply-chain attack involving Qubole, a cloud data-processing platform. Attackers used compromised IAM credentials associated with the platform's AWS account to access multiple customer AWS environments. The investigation found that the activity took place between 14 and 26 October. [1]
The attackers exploited cross-account IAM roles that customers had configured to allow Qubole's platform to access their cloud resources. Once inside, they enumerated cloud infrastructure, searched for credentials and accessed data stored in Amazon S3 buckets. Some buckets were reportedly downloaded in their entirety. [1][2]
The activity went beyond one cloud service. Investigators found attempts to retrieve secrets from AWS Secrets Manager, Systems Manager Parameter Store and Lambda environment variables. Discovered credentials were then tested against AWS, Microsoft Entra ID and Okta services. This created opportunities to reach additional resources beyond the original cloud integration. [1]
The most revealing detail was that some customer environments still trusted Qubole's AWS account despite no longer actively using the integration. The trust relationships remained in place, allowing the attackers' role-assumption requests to succeed.
The incident illustrates a common cloud security problem: an integration that was approved for a legitimate business purpose can become an entry point when the identity operating it is compromised.
The Risk Behind Cross-Account Trust
Cross-account IAM access is a standard way to let an external platform work with customer resources without sharing long-term AWS access keys.
A customer creates an IAM role and allows a specified external AWS account to assume it. The vendor then uses the AWS Security Token Service (STS) AssumeRole operation to obtain temporary credentials with the permissions defined by that role.
The arrangement is practical, but its security depends on how the trust relationship is configured and maintained.
An External ID can help address the confused deputy problem, but AWS explicitly states that it should not be treated as a secret. It also cannot compensate for an overly broad trust policy or excessive permissions. [3]
If an external identity is compromised, the attacker may inherit whatever access the customer has granted to it.
This makes third-party access a business risk as much as an identity-management issue. A vendor may need permission to read a specific dataset, but that should not automatically mean it can retrieve unrelated application secrets or access every storage bucket.
What Organisations Should Review
The incident offers several practical checks for cloud and security teams:
-
Inventory external trust relationships. Identify every IAM role that permits access from an external account, including integrations that are no longer in use.
-
Apply least privilege. Restrict each role to the resources and actions required by its business purpose.
-
Narrow trusted identities. Where supported, trust specific vendor principals rather than an entire external account. Apply appropriate source-network conditions.
-
Monitor role assumptions. Review CloudTrail for unexpected AssumeRole activity, unfamiliar source networks and access from dormant integrations.
-
Protect downstream credentials. Limit permissions to Secrets Manager, Lambda configuration, Parameter Store and sensitive S3 data.
-
Review session exposure. Revoking an access key does not necessarily invalidate temporary credentials already issued. Investigate and revoke active sessions where necessary.
AWS recommends temporary credentials for workloads, least-privilege permissions and regular removal of unused roles and credentials. Its IAM Access Analyzer can also help identify unexpected public and cross-account access. [3][4]
Testing the Digital Attack Surface
Cloud security reviews need to consider how exposed applications, APIs, identities and network services interact. A vulnerability in one digital asset can provide a route toward resources that were never intended to be publicly reachable.
Authorised penetration testing can help organisations assess supported digital environments, identify reachable weaknesses and validate whether exposed services create additional attack paths.
Bronyx AI, ITSEC's AI-assisted autonomous penetration testing platform, supports authorised assessment of web applications, APIs and defined network environments. It can help security teams examine exposed digital assets and validate technical weaknesses within an approved testing scope.
It does not replace AWS IAM policy reviews, CloudTrail monitoring or cloud-native access analysis. Those controls remain necessary to identify excessive permissions and suspicious cross-account activity.
The question organisations should ask is straightforward: if a trusted vendor identity were compromised today, how much of the company's cloud environment could it reach?
Learn more about Bronyx AI at https://bronyx.ai/.
References
-
Wiz Research, Trusted by Default: Qubole Cross-Account Access Abused in the Wild, 9 November 2026. https://www.wiz.io/blog/qubole-cross-account-access-abused-in-the-wild
-
The Register, Attackers backdoor trusted AWS integrations to steal secrets, 9 November 2026. https://www.theregister.com/security/2026/11/09/attackers_backdoor_trusted_aws_integrations_to_steal_secrets/
-
Amazon Web Services, Access to AWS accounts owned by third parties, AWS IAM documentation. https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html
-
Amazon Web Services, Security best practices in IAM, AWS IAM documentation. https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html
.png)


