Skip to content
Qubole Supply Chain Attack Compromises AWS Customer Accounts

Qubole Supply Chain Attack Compromises AWS Customer Accounts

First seen 9 Nov 2026, 17:38 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 10, 2026 at 13:43 UTC
  • •Attackers exploited AWS IAM roles linked to Qubole to access customer data.
  • •Sensitive information, including AWS and Okta credentials, was stolen during the attack.
  • •Organizations are urged to audit their CloudTrail logs for suspicious activity.

Between October 14 and October 26, 2026, a threat actor exploited AWS cross-account IAM roles linked to Qubole, a data lake platform, to access multiple customer environments and steal sensitive data. The attacker used IAM credentials from Qubole's AWS account to assume roles in customer accounts, allowing them to enumerate resources, extract secrets, and download data from S3 buckets. The attack was identified by Wiz, in collaboration with Sentra and Mandiant, who reported that the compromised roles were often unused but still trusted Qubole's account. The attacker also employed tools like TruffleHog to validate stolen credentials, including AWS access keys and Okta client secrets. Organizations that had connected Qubole to AWS are advised to review CloudTrail logs for suspicious AssumeRole requests and take immediate action to secure their environments. As of now, neither Qubole nor Idera has issued a public statement regarding the incident.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-10-14
Initial suspicious activity detected
Wiz observed the first signs of unauthorized AssumeRole requests from Qubole's AWS account.
Wiz
2026-10-18
Increased attack activity
The attacker began using a second IAM user associated with Qubole's AWS account for further role assumptions.
Wiz
2026-11-09
Attack details disclosed
Wiz published findings detailing the supply chain attack and its impact on Qubole customers.
The Hacker News

More articles in this cluster (12)

Following this threat?

Track Idera in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

How can I check if my organization is affected?
Review your CloudTrail logs for AssumeRole requests from Qubole's AWS account ID, 805246085872, especially from non-AWS IP addresses.
What immediate actions should I take?
Rotate all exposed secrets, revoke active sessions, and implement stricter source IP conditions for cross-account roles.
Has Qubole issued a statement regarding the breach?
As of now, neither Qubole nor Idera has publicly commented on the incident.