Skip to main content

Praxis AI™Vijilan's most advanced SOC platform is open to early adopters.

Sign up here
Threat Intelligence · November 20, 2026

JPMorgan Chase, Mastercard and Visa Confirm Vendor Cyberattacks

JPMorgan Chase, Mastercard and Visa each say a third-party provider was hit, exposing marketing or contact data such as names and email addresses. Payment systems were not affected. What MSPs serving financial clients should do now.

Vijilan Incident Desk· 5 min read
JPMorgan Chase, Mastercard and Visa Confirm Vendor Cyberattacks
Short answer

JPMorgan Chase said on 19 November 2026 that third parties who provide services to it "were the target of a cyberattack", and that the attackers appear to have accessed marketing data held by those vendors, which may include some customer names and email addresses [1][2]. Mastercard said the same day that an incident at a third-party provider exposed a limited number of email addresses, which it described as non-payments information, for a small subset of cardholders in one benefit program [1][2]. Visa said earlier in the week that claims about it relate to an incident at a third-party service provider in Asia Pacific [1][2]. None of the three says its own systems or payment services were affected. For anyone running IT for a financial-services client, the lesson is about vendors, and about the phishing that usually follows a leak of names and email addresses.

What has been confirmed

  • JPMorgan Chase (19 November): Third parties that provide services to the bank were targeted. Based on its investigation so far, it believes the attackers accessed certain marketing data held by those vendors, which may include some customer names and email addresses. It says there is no disruption to its services, that it will contact affected customers directly where appropriate and offer support including complimentary credit monitoring, and that there is no connection to the service disruptions some customers saw earlier in the week [1][2].
  • Mastercard (19 November): It was recently informed of an incident at a third-party provider that exposed a limited amount of email addresses, non-payments information, from a small subset of cardholders enrolled in a specific benefit program. It says there is no impact on the Mastercard payment network or on people's ability to use their cards [1][2].
  • Visa (earlier in the week): It says the claims are associated with an incident involving a third-party service provider in Asia Pacific [1][2].

None of the companies has named the vendors involved, said when the attacks happened, or said whether the incidents share a common provider [1]. None has named an attacker. Record counts circulating online come from claims and press reviews of leaked files, not from the companies, so we do not repeat them here.

Why this matters to MSPs

Every one of these incidents started at a supplier, not at the bank or card network. Visa's own Fall 2026 threats report, published on 17 November, found that incidents involving third-party agents rose 62% compared with the previous six months, and that those providers were linked to approximately 56% of compromised payment credentials Visa identified between January and June 2026 [3]. An MSP is a third party too. The data in this case, names and email addresses tied to a bank or card program, is exactly what makes a phishing email look real.

What to do now

  1. Warn financial-services clients about follow-on phishing. Tell staff to expect emails and calls that mention Chase, Mastercard or Visa and a real program or card benefit. No genuine bank or card network will ask for a password, a one-time code or a transfer to a "safe account".
  2. Tighten email defenses for those clients. Check that DMARC, SPF and DKIM are enforced on their own domains, and that lookalike-domain and brand-impersonation rules cover the bank and card brands their staff deal with.
  3. List the vendors that hold client data. For each client, write down which marketing, loyalty, benefits and CRM providers receive customer or staff data, and what data each one actually needs. Data a vendor does not hold cannot leak from that vendor.
  4. Check vendor notification terms. Make sure each contract says how quickly the vendor must tell your client about an incident, and who receives that notice.
  5. Apply the same test to yourself. If your clients asked you tomorrow which of their data you hold and how fast you would tell them about a breach, have the answer written down.

Frequently asked questions

What data was exposed?

JPMorgan Chase says the attackers appear to have accessed marketing data held by vendors that may include some customer names and email addresses. Mastercard says email addresses for a small subset of cardholders in one benefit program were exposed [1][2].

Were card numbers or passwords taken?

None of the companies has said so. Mastercard describes the exposed data as non-payments information, and says its network and cardholders' ability to use their cards are unaffected [1][2].

Were the banks' own systems breached?

The companies describe the incidents as attacks on third-party providers. None says its own systems were breached [1][2].

Is this connected to the bank outages earlier in the week?

JPMorgan Chase says there is no connection to the service disruptions some customers experienced earlier in the week [1][2].

What should a customer of these companies do?

Treat unexpected emails or calls that mention these brands with suspicion, never share passwords or one-time codes, and contact the company through the number on the card or its official app.

If you want a team watching identities, email and endpoints for the phishing and account-takeover attempts that follow incidents like this, ThreatDefend™ runs CrowdStrike Falcon with a 24/7 SOC: machine speed where speed wins; a human approves the actions that carry real risk. Talk to us.

Sources

  1. JPMorganChase, Mastercard, Visa report cyberattack on third-party service providers (ABC News)
  2. JPMorgan, Visa, Mastercard Say Third-Party Vendors Targeted in Cyberattack (Reuters via Claims Journal)
  3. Visa Report: AI-Enabled Fraud and Third-Party Attacks Are Scaling Worldwide (Visa)

Found this useful? Send it to someone who needs it.

Threat notes, once a week

What our SOC actually saw this week: new attack patterns, the detections we shipped against them, and what it means if you run an MSP. Written by the analysts, not by marketing.

One email a week. One click to stop, and we do not sell your address to anyone.

ThreatDefend™

Our stack. Our SOC.

Managed XDR on CrowdStrike Falcon, deployed and run 24/7 by the Vijilan SOC.

See ThreatDefend™

Questions this answers

What data was exposed?

JPMorgan Chase says the attackers appear to have accessed marketing data held by vendors that may include some customer names and email addresses. Mastercard says email addresses for a small subset of cardholders in one benefit program were exposed.

Were card numbers or passwords taken?

None of the companies has said so. Mastercard describes the exposed data as non-payments information, and says its network and cardholders' ability to use their cards are unaffected.

Were the banks' own systems breached?

The companies describe the incidents as attacks on third-party providers. None says its own systems were breached.

Is this connected to the bank outages earlier in the week?

JPMorgan Chase says there is no connection to the service disruptions some customers experienced earlier in the week.

What should a customer of these companies do?

Treat unexpected emails or calls that mention these brands with suspicion, never share passwords or one-time codes, and contact the company through the number on the card or its official app.