CYBER ATTACK / TECHNOLOGY

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.

THE STORY

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 TO DO

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:

01 / WHAT WE KNOW

Qubole data breach: the details

Reports on the Qubole data breach each day3 Nov to 16 Nov · today is lighter, still counting
See the numbers
DayReports
3 Nov0
4 Nov0
5 Nov0
6 Nov0
7 Nov0
8 Nov0
9 Nov1
10 Nov2
11 Nov0
12 Nov0
13 Nov0
14 Nov0
15 Nov0
16 Nov (so far)0
02 / LATEST

Latest Qubole news

TIMELINE

Qubole data breach: timeline

SOURCES

Sources for the story

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.