Skip to main content
Emerging ThreatsData Breaches

Ransomware Group Exposes Chase, Visa, Mastercard Customer Data

Financial institution office interior with subtle hints of data breach, people working in background.

"We have learned that third parties who provide services to the firm were the target of a cyber attack," J.P. Morgan Chase wrote on X, acknowledging a breach at vendors that — according to the bank — may have exposed some customers' names and email addresses.

J.P. Morgan Chase: vendor attack, no service disruption, limited confirmed impact

J.P. Morgan Chase said a cyberattack targeted third-party service providers and that, based on the bank's investigation so far, "the attackers accessed certain marketing data held by those vendors, which may include some customer names and email addresses." The firm emphasized the incident did not disrupt Chase services and said it was unrelated to a separate service disruption earlier in the week. Chase's consumer banking division reports about 78 million active digital customers; the company is the largest U.S. bank by assets with about $4.1 trillion as of June 2026.

Visa and Mastercard: third-party incidents; no payments data affected, Mastercard limits exposure

Visa and Mastercard each confirmed they were made aware of incidents tied to a third-party service provider. Visa told BleepingComputer that "Visa's systems were not involved and were not impacted. No payments data such as card numbers were affected." Visa added the event was "associated with an incident involving a third-party service provider in Asia Pacific" and said it was unrelated to other system disruptions earlier that week.

Mastercard similarly said it was "recently informed of an incident at a third-party provider that resulted in the exposure of limited amount of email addresses – non-payments information – from a small subset of cardholders enrolled in a specific benefit program." Mastercard's spokesperson also assured that "There is no impact to the Mastercard payment network or the ability for people to use their cards," and that "at this time, the exposure has been contained and our teams are working with the provider to support the impacted cardholders as needed."

Qubole and n0n ransomware: claimed access path, haul, and timeline

The hacking group n0n claimed responsibility for an attack on Qubole on November 11, 2026, and posted alleged data from Chase, Visa, and Mastercard to its extortion site on November 16, 2026. BleepingComputer reports Qubole is a cloud data analytics company owned by Idera that provides cloud data analytics, automated processing, real-time analysis, and reporting.

According to the details attributed to n0n, between October 14 and 26, 2026 the actors used compromised Qubole credentials to access customers' AWS environments through IAM roles that the affected companies had configured to grant Qubole access. n0n claimed to have stolen 53.9 GB across 30,743 files directly from Qubole, specifying customer contracts, pricing records, staff and trial-user information, and production data. Separately, the group claimed to hold nearly one petabyte of data taken from Qubole's customer networks.

Data types leaked and competing claims

The publicly quoted statements show a mix of confirmed corporate assessments and attacker claims. Chase described accessed material as "marketing data" that "may include some customer names and email addresses." Mastercard described exposure limited to a small number of email addresses tied to a benefit program and said non-payments information was involved. Visa explicitly stated no payments data such as card numbers were affected. The n0n group, by contrast, described a much broader haul from Qubole — both the 53.9 GB of files it says it took directly from Qubole and a claimed one-petabyte dataset from customer networks — and asserted it contacted Qubole and some affected companies with extortion demands before public reporting from Sentra and Wiz appeared, but that its demands were ignored.

How technologists, procurement leaders, and customers are likely to respond

  • Technologists and security teams: will be watching the reported attack vector closely — n0n said the actors used compromised Qubole credentials to assume IAM roles into customers' AWS environments — and may re-evaluate third-party access controls and IAM role trust relationships that grant vendors cross-account access.
  • Affected enterprises and procurement leaders: will face renewed pressure to verify vendor security practices and to audit which vendors hold marketing or non-payments customer data, given the multinational scope suggested by involvement of global payment networks and a cloud analytics provider.
  • End users and cardholders: should note the companies' public statements — Chase warned customer names and email addresses may have been accessed; Mastercard described a limited exposure of email addresses for a subset of cardholders; Visa said no card numbers were affected — and await follow-up communications from their providers about containment and remediation.

Two practical markers remain: Qubole, the vendor named in reports and described as owned by Idera, had not responded to BleepingComputer's request for comment as of the publication of those reports; and the hacking group published alleged data on November 16, 2026. Those facts leave open how many organizations beyond Chase, Visa, and Mastercard may have been touched, and how quickly affected parties can validate the scope of exposed records. The coming days will show whether vendor access models and IAM configurations that permit extensive third-party access are tightened — and whether the companies involved provide more granular confirmations of which customers, if any, should take further steps.

Source: BleepingComputer — Vendor data breach exposes Chase, Visa, Mastercard customer info