Tuesday 17 November 2026 · UTC
Global

Your region, kept on this device.

Qubole supply chain attack used AWS cross-account roles to steal customer data and credentials

Compiled by RedTeamDaily · AI-assisted summaries · Human review not recorded for this version

Published

Read CSO Online report

What happened

Attackers abused trust links between the software platform and its customers' cloud accounts between 14 and 26 October. They copied files and secret passwords from dozens of organisations, including some that had stopped using Qubole but still had active access.

Like I’m new · Written by AI from 1 source · Report an error

Sources
1

Sources and verification

Sources and editorial review

No named human review has been recorded for this story. See the source evidence below.

No vendor or government source is linked to this story yet. Read the source reports; attribution is not independent verification.

How severity and exploitation labels work · All source reports · Report an error

What to do

  1. Review AWS CloudTrail records from October 1 across all accounts containing Qubole integration roles for suspicious AssumeRole activity from Qubole's AWS account.
  2. Investigate subsequent activity involving Secrets Manager, Parameter Store, Lambda and S3.
  3. Remove unused third-party integrations.
  4. Narrow trust policies to specific vendor IAM principals and restrict role assumption to documented vendor network ranges.

Written by AI from the sources, checked against them

Source timeline (UTC) · 1 update

  1. Tue 10 NovemberQubole supply chain attack exposed AWS, Entra ID, and Okta credentialsCSO Online

Explore this report

Ask AI about this story

Optional follow-up answers generated from our coverage. Check the linked sources before acting.

Ask your own question

Who and what is in it

Malware

Companies

Report a problem