Security Intel · Cloud

Qubole access abused to steal data from customers’ AWS accounts

9 Nov 2026INTEL

An attacker used credentials belonging to data platform vendor Qubole to sign in to customers’ AWS accounts through the trust they had granted Qubole, then stole data and secrets. Here is how to check your own cloud vendor access.

Many cloud services ask customers to create an AWS role that the vendor’s own AWS account is allowed to use. It is a standard and convenient way to give a vendor access. Between 14 and 26 October, an attacker used IAM credentials from an AWS account associated with data platform vendor Qubole to use those roles in several customers’ environments. The activity was investigated by Wiz, Sentra and Mandiant, and Wiz published details on 9 November.

What the attacker did

  • Assumed the trusted Qubole roles in multiple customer AWS accounts. In most cases, nobody else had used those roles that month.
  • Listed storage, compute, databases and security settings.
  • Downloaded data from any S3 bucket the roles could reach, in some cases entire buckets.
  • Collected secrets from Lambda environment variables, Secrets Manager and Parameter Store, then tested them against AWS, Microsoft Entra ID and Okta.

Separately, from 8 October, customer-owned access keys created for Qubole integrations were also tested, and a small number of customer environments were compromised that way. How the attacker obtained the Qubole credentials has not been disclosed.

Why it matters

Vendor roles are often created during a trial or project, given wide permissions and then forgotten. They carry the vendor’s trust long after anyone remembers why they exist. If the vendor is compromised, so are you.

What to do

  • List every IAM role that trusts an external account, and delete the ones you no longer use.
  • Cut permissions to the minimum, especially broad S3 read, Secrets Manager and Parameter Store access.
  • Restrict where roles can be used from, with source IP or VPC endpoint conditions where the vendor supports them.
  • Alert on vendor role use from new networks, VPNs or hosting providers, and keep CloudTrail enabled across the organisation.
  • If you used Qubole, review CloudTrail from 1 October for the indicators Wiz published, and rotate every secret the roles could read. Revoke active sessions too, because rotating credentials does not end sessions already issued.
NetWitz noteThe same pattern applies to Microsoft Entra ID app consents and Google Cloud service accounts. A quarterly review of “who outside our company can get in, and with what rights” is one of the highest-value cloud security tasks you can schedule.

Sources: Wiz: Qubole cross-account access abused in the wild; SecurityWeek: over a dozen organisations hit in Qubole supply chain attack.

More from Security Intel
Malaysia

Health Ministry file-sharing breach: lessons for every Malaysian organisation

Malaysia’s Ministry of Health has confirmed unauthorised access to a file storage and sharing platform at one of its facilities. Patient services were not affected, but the incident is a reminder of how exposed shared file platforms can be.

14 Nov 2026
Vulnerability

PHP2Shell: patch PHP now, then check your firewalls

Two critical PHP flaws disclosed on 21 October are now being used to take over web servers and, in at least two campaigns, firewalls and VPN gateways. Here is what is affected, what has happened so far and what to do this week.

13 Nov 2026

Discuss how this applies to your environment.

Talk to us about the area this article covers and what we would do in your environment.

NetWitz