Back to Feed
Supply ChainNov 10, 2026

Over a Dozen Organizations Hit in Qubole Supply Chain Attack

Attackers exploited compromised Qubole IAM credentials to steal data from over a dozen organizations.

A threat actor exploited compromised IAM credentials for a Qubole AWS account to steal data from over a dozen organizations. The attackers assumed IAM roles that organizations had set up for Qubole's AWS account, accessing their AWS environments. These roles were often left in place long after Qubole was no longer in use, allowing the threat actor to enumerate resources, collect secrets, and access data from October 14 to October 26.

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run Qubole?

Get an email when a new story names Qubole, 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 lesson

Attackers exploited compromised Qubole AWS IAM credentials to assume cross-account roles that victim organizations had configured for Qubole's use, gaining unauthorized access to their AWS environments. The core failure was that organizations never revoked or audited these IAM roles after discontinuing their use of Qubole, leaving persistent, privileged access pathways open for years. This is a textbook supply chain access control failure: trusting a third-party vendor with standing cloud permissions without enforcing a lifecycle process to remove that trust when the relationship ends. The incident highlights how third-party integrations create implicit, long-lived attack surfaces that are frequently forgotten. Attackers had a 12-day window to enumerate resources, harvest secrets, and exfiltrate data entirely because no one was watching these dormant roles.

What helps against this

How we list vendors

Entities

Qubole (product)AWS (technology)IAM (technology)