SecurityOnlineDo Son
Wiz uncovers attacks abusing Qubole access to AWS accounts
Part of the Qubole story · since 9 Nov
- Mon 9 Nov, 16:46 UTC. cybersixt, first report. Attackers used Qubole's AWS account to steal data from its customers.
- Mon 9 Nov, 19:00 UTC. The Hacker News, its first report on the story. Wiz details attacker breach of Qubole linked AWS accounts.
- Tue 10 Nov, 14:00 UTC. SecurityWeek, its first report on the story. Qubole supply chain attack exposed data at over a dozen firms.
- Fri 13 Nov, 08:30 UTC. SecurityOnline, its first report on the story. Wiz uncovers attacks abusing Qubole access to AWS accounts. This article, 4th of 4.
Between 14 October and 26 October 2026, Wiz, Sentra and Mandiant say threat actors abused Qubole cross‑account access to breach multiple customer AWS environments. The intruder used compromised IAM credentials from Qubole’s vendor account (805246085872) to call sts:AssumeRole and assume trusted customer roles, enabling access to storage, compute and database services. Every AssumeRole request carried an External ID and, according to the researchers, every one succeeded.
The attacker used role session names such as quiam-enum and quiam-scope-full to map targets and privileges, and much of the activity stemmed from dormant Qubole cross‑account roles that remained enabled after customers stopped using the platform.
Credential harvesting and data theft followed. The attacker retrieved credentials from AWS Secrets Manager, SSM Parameter Store and Lambda function environment variables, then used TruffleHog to test stolen keys against AWS, Microsoft Entra ID and Okta. Wiz also identified a bootable Linux image named sso_agent.iso on the attacker’s OVH server, which loads ntfs3 to target Windows disks, runs scripts over TCP port 23458 and reboots after 90 minutes to erase traces.
Most victims reported that these Qubole roles had been inactive prior to the intrusion, yet trust policies allowed the attacks to succeed. The operation’s attribution remains unconfirmed; a handle “non” claimed responsibility, but investigators have not verified this.
Organisations are advised to remove unused or legacy third‑party IAM trust relationships, review CloudTrail for October 2026 AssumeRole activity from account 805246085872 outside AWS IP ranges and related AIDA3W7DIFLYOLTK63SFS activity, revoke active sessions and rotate secrets and Lambda variables accessed by the compromised Qubole roles.
How the story developed
4 articles from 4 outlets since 9 Nov. Picked up again on 13 Nov after 3 days quiet. This was the 4th report, 4 days after the first.
- Mon 9 Nov, 16:46 UTC. cybersixt, first report. Attackers used Qubole's AWS account to steal data from its customers.
- Mon 9 Nov, 19:00 UTC. The Hacker News, its first report on the story. Wiz details attacker breach of Qubole linked AWS accounts.
- Tue 10 Nov, 14:00 UTC. SecurityWeek, its first report on the story. Qubole supply chain attack exposed data at over a dozen firms.
- Fri 13 Nov, 08:30 UTC. SecurityOnline, its first report on the story. Wiz uncovers attacks abusing Qubole access to AWS accounts. This article, 4th of 4.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
- Quiet time, folded
Show all 4 articles as a listHide the list
- Mon 9 NovDay 02
- Attackers used Qubole's AWS account to steal data from its customers16:46 · cybersixt · First report
- Wiz details attacker breach of Qubole linked AWS accounts19:00 · The Hacker News
- Tue 10 NovDay 11
- Qubole supply chain attack exposed data at over a dozen firms14:00 · SecurityWeek
Quiet for 3 days
Fri 13 NovDay 41- Wiz uncovers attacks abusing Qubole access to AWS accounts08:30 · SecurityOnline · Picked up again · This article, 4th of 4