News and insights

Chase, Visa and Mastercard: customer data exposed at suppliers

Three of the best-known names in payments have said that customer details were exposed at their suppliers, not in their own systems. The data was mostly names and email addresses used for marketing. It shows how far customer data travels, and how hard it can be to say where.

What happened

On 19 November 2026, JPMorgan Chase said that “third parties who provide services to the firm were the target of a cyber attack”. It believes the attackers “accessed certain marketing data held by those vendors”, which may include some customer names and email addresses.

Chase did not name the suppliers or say how many customers were affected. It said its services were not disrupted. It plans to contact affected customers and offer free credit monitoring.

Visa said the incident involved a third-party service provider in Asia Pacific. It said its own systems were not affected and no payment data, such as card numbers, was exposed.

Mastercard said an incident at a third-party provider exposed a limited number of email addresses. They belong to a small group of cardholders in one benefit programme. It said the exposure has been contained.

A ransomware group calling itself n0n published data it says came from all three companies on 16 November. Cybernews, a security news site, reports that the Chase file holds about 16,000 customer email addresses. A Cybernews researcher said the files share the same layout, which suggests one common source. None of this has been independently verified.

The group says the data came from a supplier the three companies shared. The companies have not named any supplier, and that claim has not been confirmed.

What to do now

The useful lesson is not about these three companies. It’s whether you could answer the same questions about your own suppliers.

  • List the suppliers that hold customer data, including marketing, email and analytics tools, and the providers they use.
  • Send them only what they need. A campaign tool may need an email address, but not account numbers or phone numbers.
  • Ask your key suppliers who they rely on. A breach two steps down the chain still lands on your customers.
  • Check the access you’ve given suppliers into your own systems, and remove what is no longer used.
  • Know who you must tell, and by when, if a supplier tells you your customers’ data was exposed.

These Blueprint requirements cover the same ground:

  • RW-SUP-01 A list of your suppliers (Foundation). Record what each supplier provides and what data or access it has, marketing tools included.
  • RW-SUP-04 Agreements in place before personal data is shared (Foundation). Sign a data processing agreement before any supplier gets personal data.
  • RW-SUP-13 Subcontractors known and held to the same standard (Advanced). Critical suppliers should tell you which subcontractors handle your service, and hold them to the same standard.
  • RW-SUP-07 Supplier risks in your risk register (Established). A breach at a marketing supplier is a risk like any other, with an owner and a treatment.
  • RW-DET-05 Incidents reported on time (Foundation). Tell regulators and the people affected within the time the law or your contracts allow.

How RiskWitness helps

“Which of our suppliers hold customer details?” Suppliers. Record each supplier with what it provides, an owner, whether it handles personal data, and where the data is held. RiskWitness works out how critical each one is from a few questions, including the data it holds and the access it has.

“Who do they rely on?” Suppliers. Note each supplier’s own key suppliers. Record whether the contract passes security requirements on to its subcontractors, and whether a data processing agreement is in place. Keep assurance evidence and send questionnaires.

“What does it mean for us?” Risks. Record the risk of a breach at a supplier that holds customer data, linked to the supplier, with an owner. Score it before and after controls, and choose a treatment.

“Who do we need to tell, and by when?” Incidents. Record the supplier’s incident, linked to the supplier and the risk, with when you became aware. RiskWitness shows which regulators may need telling, with their deadlines.

“What will we change?” Actions and Reports. Turn follow-ups into actions with owners and due dates, such as removing unused supplier access or sending less data. Map your supplier controls to the RiskWitness Blueprint requirements above. Then produce a PDF report or slide deck for leadership.

Every step is kept in a history that shows who did what, when, and the old and new values. Nobody can edit or delete it. When leadership, an auditor, a customer or a regulator asks how you responded, the answer is already written down.

Sources