QUBOLE.
DATA BREACH
Qubole (technology) was hit by a data breach first reported on 9 November 2026. No group has been publicly named as behind it in these reports. 3 news reports in the last 14 days, 0 in the last 24 hours; the latest, from BleepingComputer: “Hackers exploit trusted AWS access to breach multiple cloud environments”. See every attack on the live map.
What happened in the Qubole data breach
Qubole, a big-data and data lake platform owned by Idera according to The Hacker News, was hit by a supply-chain campaign. Its platform runs inside customers' AWS accounts through cross-account IAM roles. Sentra first noticed suspicious activity in several customer environments, and Wiz, working with Sentra and Google's Mandiant, investigated.
The attacker harvested secrets and copied data from S3 buckets, in some cases downloading entire buckets. Wiz also described a separate campaign from 8 to 11 October that used customers' own AWS access keys set up for Qubole integrations.
Wiz has not disclosed how many organisations were affected. SecurityWeek reports more than a dozen, while Sentra's account, reported by CSO Online and others, describes dozens of Qubole customers. Nobody has been named as the attacker. Wiz says the campaign looks broad and opportunistic and has not tied it to a specific group.
- What was taken: According to Wiz, the attacker collected credentials, keys and secrets held in AWS Lambda, Secrets Manager and SSM Parameter Store, and copied data from customer S3 storage. SecurityWeek says the stolen material included customer files, secrets, keys, environment variables and credentials. Sentra says the attacker made no changes or deletions, only copies. The Hacker News reports that the attacker used the TruffleHog tool to validate stolen access keys, Entra ID client secrets and Okta credentials.
- Who is affected: SecurityWeek reports that the attacker hit over a dozen organisations. Sentra says dozens of Qubole customers were impacted. Wiz did not disclose the number of organisations involved.
- Who is behind it: Nobody has been named. Wiz describes the actor only as an unidentified attacker and says researchers have not attributed the campaign to a specific group. The Hacker News says the researchers believe the 8 to 11 October campaign used customers' AWS keys that had been set up for Qubole. An IP address linked to Mullvad VPN attempted to assume customer roles, according to Sentra.
- The response: Sentra said it alerted the researchers after spotting activity across several customers' environments. Wiz recommended that organisations review AWS CloudTrail records from 1 October 2026 onwards.
Was my data taken in the Qubole data breach?
For this data breach: Review every IAM role that trusts Qubole, including roles you no longer use, and remove Qubole from any role it no longer needs. Rotate any secrets, keys, Lambda variables, Secrets Manager entries or SSM parameters that the roles could reach, and revoke active sessions. Restrict trust policies to Qubole's specific IAM principal and add source IP conditions where Qubole supports them. Sentra advises telling Qubole about your exposure.
Only Qubole can confirm whose data was involved. If you are a customer, these five steps cover you either way:
- Look for an email or letter from Qubole. Firms whose data is taken usually have to tell the people affected, and it says what was taken.
- If you have an account with Qubole, change its password, and the password anywhere else you used the same one.
- Turn on two-step sign-in where you can, so a stolen password is not enough on its own.
- Expect scam emails, texts and calls that mention Qubole or this breach. Do not click links in them; go to the real website yourself.
- Check whether your email address has turned up in known breaches at haveibeenpwned.com. In the UK, report money lost to fraud to Action Fraud.
Qubole data breach: the details
- Type: Data breach
- Sector: Technology
- Reports, last 14 days: 3
- Latest report: 19:31 UTC, 10 November 2026
See the numbers
| Day | Reports |
|---|---|
| 3 Nov | 0 |
| 4 Nov | 0 |
| 5 Nov | 0 |
| 6 Nov | 0 |
| 7 Nov | 0 |
| 8 Nov | 0 |
| 9 Nov | 1 |
| 10 Nov | 2 |
| 11 Nov | 0 |
| 12 Nov | 0 |
| 13 Nov | 0 |
| 14 Nov | 0 |
| 15 Nov | 0 |
| 16 Nov (so far) | 0 |
Latest Qubole news
- Hackers exploit trusted AWS access to breach multiple cloud environmentsBleepingComputer · Data breach · Place unknown · 10 Nov 2026, 19:31 UTC
- Over a Dozen Organizations Hit in Qubole Supply Chain AttackSecurityWeek · Data breach · Place unknown · 10 Nov 2026, 13:27 UTC
- Hackers exploit Qubole's trusted AWS access to breach customer accounts and steal dataThe Hacker News · Data breach · Place unknown · 09 Nov 2026, 17:51 UTC
Qubole data breach: timeline
- 2026-10-08: A separate campaign begins, using customer-owned AWS access keys set up for Qubole integrations, according to Wiz.
- 2026-10-11: The separate campaign using customer-owned AWS access keys ends, according to Wiz.
- 2026-10-14: Credentials tied to Qubole's AWS account call sts:AssumeRole to obtain temporary credentials for customer integration roles, which Wiz traces as the main activity.
- 2026-10-18: The attackers begin using a second IAM user from the same Qubole AWS account, according to Wiz.
- 2026-10-26: The main campaign window closes, according to Wiz, The Hacker News and CSO Online.
- 2026-11-09: Wiz publishes its analysis of the campaign, and The Hacker News reports it.
- 2026-11-10: SecurityWeek reports that more than a dozen organisations were hit.
Sources for the story
- Hackers Exploit Qubole's Trusted AWS Access to Breach Customer Accounts and Steal Data
- Over a Dozen Organizations Hit in Qubole Supply Chain Attack - SecurityWeek
- Qubole supply chain attack exposed AWS, Entra ID, and Okta credentials
- Hackers Use Qubole AWS Credentials To Breach Customer Cloud Environments - Dataconomy
- Inside the Qubole Supply Chain Attack: How Sentra Found It
- Qubole customers targeted in AWS cross-account access attack
- Hackers Abuse Qubole's Trusted AWS Access to Breach Multiple Cloud Accounts and Steal Sensitive Data
Qubole data breach: common questions
What happened to Qubole?
Qubole (technology) was hit by a data breach first reported on 9 November 2026. No group has been publicly named as behind it in these reports.
What is the Qubole supply chain attack?
An attacker used IAM credentials tied to Qubole's AWS account to assume trusted roles in customer AWS environments. Wiz says the attacker then harvested secrets and copied S3 data, mainly between 14 and 26 October 2026.
Who is behind the Qubole attack?
Nobody has been named. Wiz says researchers have not attributed the campaign to a specific group and do not know how the stolen data is being used.
How many organisations were affected by the Qubole breach?
SecurityWeek reports more than a dozen organisations, while Sentra says dozens of Qubole customers were impacted. Wiz has not disclosed a number.
How do I check whether my AWS account was affected?
Wiz recommends checking all accounts that contain Qubole integration roles.
What data was stolen in the Qubole attack?
According to Wiz, the attacker accessed secrets and copied data from customer S3 storage. SecurityWeek says customer files, secrets, keys, environment variables and credentials were taken.
Who is behind the Qubole data breach?
No group has been publicly named in the reports collected here. Attribution can take weeks and is often disputed.
Was my data affected?
Only Qubole can say whose data was involved; its own statement is usually linked from the latest reports below. If you are a customer, watch for emails or texts that mention the breach, change your password there and anywhere you reuse it, and turn on two-step sign-in.