Breaches and incidents

Chase, Visa and Mastercard confirm they are investigating third-party breaches

Chase says customer names and email addresses held by vendors may have been exposed, and Mastercard reports email addresses from one benefit programme. An extortion group claims the data, and a cloud analytics provider is the suspected entry point.

By Junglewise News DeskPublished 5 min read
Visa's former headquarters building in Foster City, California, with the Visa logo on its facade under a blue sky.
Coolcaesar, CC BY-SA 4.0 via Wikimedia Commons

JPMorgan Chase, Visa and Mastercard have each confirmed they are investigating breaches at third-party providers that may have exposed customer information, The Register reported. None of the three says its own systems were touched. The data involved, so far as any of them has described it, is contact information rather than payment information.

Chase said the attackers reached marketing data held by vendors. "Based on our investigation so far, we believe the attackers accessed certain marketing data held by those vendors, which may include some customer names and email addresses," the bank said in a post on X. Mastercard described a smaller exposure: email addresses belonging to cardholders enrolled in one benefit programme. Visa said the claims relate to a service provider in Asia Pacific and that no card numbers were affected. The practical consequence for the people in those records is a sharper phishing risk: a name, an email address and a verified relationship with a named bank or card programme is exactly the raw material a convincing fake message needs.

The scale is worth stating plainly, because the companies involved are not small. J.P. Morgan Chase Bank is the largest bank in the United States by assets, with roughly $4.1 trillion as of June 2026, and its consumer banking division counts about 78 million active digital customers, BleepingComputer reported. Visa and Mastercard operate payment networks across more than 200 countries, moving trillions of dollars a year. None of the three has said how many individuals are in the exposed data, and all three have declined to name the providers involved or say when the breaches happened.

What to do now

The exposed data appears to be names and email addresses rather than card numbers or credentials, so the immediate risk is social engineering rather than direct fraud.

  • Treat unexpected messages that appear to come from Chase, Visa or Mastercard with suspicion, especially ones that reference a benefits or rewards programme. Do not click links in them. Go to the provider directly, through an address or app you already use, if something needs checking.
  • Warn staff and customers who may be in scope. A phishing attempt built on a real name, a real email address and a real card programme will not look like the usual clumsy attempt.
  • Watch card and account statements for unauthorised activity, even though the three companies say payment data was not involved. Mastercard said there is "no impact to the Mastercard payment network or the ability for people to use their cards".
  • If your organisation uses Qubole, the cloud data analytics service that is the suspected source, review the identity and access management (IAM) roles you granted it in Amazon Web Services and audit what those roles could reach. Between 14 and 26 October 2026, attackers used compromised Qubole credentials to reach customers' AWS environments through those roles. Rotate the credentials, tighten the permissions to the minimum the integration actually needs, and check CloudTrail logs for activity in that window.
  • More broadly, inventory which outside suppliers hold your customer contact data and which ones hold standing access to your cloud environments. The two lists are the ones that matter here.

Technical details

The three firms' statements are consistent on one point: their own infrastructure was not breached. Visa's spokesperson said, "Visa is aware of these claims. They are associated with an incident involving a third-party service provider in Asia Pacific." Visa added that its systems were not involved and not impacted, that no payments data such as card numbers were affected, and that the incident is unrelated to the system disruptions seen across various industries in the preceding week.

Mastercard 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." The company said the exposure has been contained and that its teams are working with the provider to support affected cardholders.

Chase did not respond to a request for comment from The Register but confirmed the investigation publicly, saying third parties providing services to the firm were the target of a cyberattack. The bank said the incident did not disrupt any of its services and is not connected to the outages some customers experienced earlier in the week, which were attributed to a software bug in on-premise hardware systems.

An extortion group calling itself n0n has claimed responsibility for all three alleged intrusions, posting the companies to its data-leak site on Monday and leaking what it says is Chase, Visa and Mastercard data on 16 November 2026. Those claims are not confirmed by the companies. The group is believed to be based in Russia, emerged in September and listed 108 victims in its first month.

The suspected common thread is Qubole, a cloud data analytics company owned by Idera, used for automated processing, real-time analysis and reporting. On 11 November 2026, n0n claimed an attack on Qubole. Between 14 and 26 October 2026, attackers used compromised Qubole credentials to reach customers' AWS environments through IAM roles those customers had previously configured to give Qubole access, meaning the intrusion travelled along permissions the victims had granted themselves.

By the group's own account, it removed 53.9 GB spread over 30,743 files from Qubole itself. The haul is said to cover contracts and pricing records, details of employees and trial users, and production data. n0n further claims to be sitting on close to a petabyte pulled from Qubole customer networks. Those volumes come from the attackers and have not been verified. The group also says it approached Qubole and some affected companies before public write-ups from Sentra and Wiz described the attacks, and that its extortion demands went unanswered. Qubole did not respond to BleepingComputer's request for comment.

What remains unknown is substantial: the identity of the providers each firm used, the dates of the individual breaches, the number of people affected, and whether anything beyond names and email addresses left those vendors' systems.

Share this article

Related stories

Scan your domain free: see what attackers can see from outside, in about 30 seconds.

This article as Markdown. Atom feed.