Trusted by Default: Qubole Cross-Account Access Abused in the Wild
Threat actor abuses Qubole's AWS account to access customer cloud environments.
A threat actor exploited IAM credentials from Qubole's AWS account to assume integration roles in multiple customer AWS environments between October 14-26, 2026. The actor enumerated resources, accessed S3 data, and harvested credentials. This supply chain attack was detected by Sentra and investigated by Wiz.
AI summary of the linked source. Not reviewed by an editor. How this works
Run Wiz?
Get an email when a new story names Wiz, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonA threat actor compromised IAM credentials within Qubole's AWS account and exploited pre-existing cross-account integration roles to gain unauthorized access to multiple customer AWS environments. This is a textbook supply chain attack: customers implicitly trusted Qubole's account, and that trust was weaponized to enumerate resources, exfiltrate S3 data, and harvest further credentials. The core failure was an overly permissive, insufficiently monitored trust relationship between Qubole and its customers. It matters because a single vendor compromise cascaded into breaches across many organizations that had no direct vulnerability of their own.
What helps against this
How we list vendors- Privileged access management (PAM)
Admin accounts stop being one stolen password away from control of everything.
- Identity threat detection and response (ITDR)
Attackers who log in with real, stolen credentials get noticed.
- Cloud security posture management (CSPM and CNAPP)
Misconfigured cloud storage and over-permissive roles get caught before they leak.
Indicators of Compromise
Extracted by AI from the linked source. Not reviewed by an editor. How this works
- ip — 45.83.220.211
- ip — 57.129.54.120
- ip — 185.209.199.73