A Vendor Breach Hit JPMorgan, Visa and Mastercard Customers at Once
JPMorgan Chase, Visa and Mastercard all disclosed on November 19 that a cyberattack on a vendor exposed some customer information, including names and email addresses.

Three of the biggest names in payments had to explain the same breach on the same day, and none of them was the company that got hacked. On Thursday, November 19, JPMorgan Chase, Visa and Mastercard all said a cyberattack on a vendor exposed some customer information. The breach happened to someone else. The customers belong to them. That is the whole problem with the modern vendor data breach, and this week it hit the top of the financial system.
What happened, and what leaked
The facts, as disclosed so far, are thin in the places that matter most. JPMorgan said attackers accessed certain marketing data held by vendors, which may include some customer names and email addresses. The bank said it would contact affected customers directly, and it stressed that the incident is not related to the outage it faced earlier this week. The timing invites speculation anyway, but there is no evidence linking the two.
Visa said the breach stemmed from a vendor operating in Asia-Pacific, and that Visa's own systems played no part. Mastercard issued a similar disclosure. None of the three companies has identified which vendors were breached, which is the detail everyone wants and nobody has.
The leak site tells a sharper story. According to the Wall Street Journal, citing cybersecurity firm SOCRadar, a group called n0n claimed responsibility. On November 16, n0n claimed to have obtained cardmember engagement records. Cybernews researchers who examined the release counted around 16,000 customer email addresses, along with phone numbers and JPMorgan Chase account IDs. The released JPMorgan dataset was only 502 KB, and it was unclear whether it represented a sample or everything the attackers had stolen. JPMorgan has not named the vendors or confirmed n0n's responsibility or the 16,000 figure, so treat those numbers as reported, not confirmed.
The Reserve program connection
One detail stands out. The data appear to relate to JPMorgan's Reserve program, an invitation-only Visa credit card that usually requires customers to have at least $10 million in assets under management. That is a small, wealthy customer base, and it is exactly the kind of list that is valuable to criminals: names, emails, phone numbers and account IDs for people with serious money.
This is not the first time a breach has targeted the rich rather than the many. High-value customer lists are worth more per record than mass databases, and they are easier to monetize through targeted phishing. A generic phishing email goes to spam. A phishing email that knows your name, your card program and your bank lands differently, and the people behind this breach know that.
For the affected customers, the practical risk is not that someone drains an account tomorrow. It is that their contact details are now in criminal hands, attached to a marker that says this person is worth targeting. That risk lasts longer than the news cycle.
The vendor breach pattern
This incident fits a pattern that has defined the last month of breach news. The Fireworks AI breach hit Uber, Notion and Cursor through one shared cloud provider. The Optimizely breach hit 178 companies including Zoom, Salesforce and HSBC through a flaw in a signup flow. The Infoblox supply chain breach started with a vendor, not a hacker. The Expedia breach came through a third-party vendor too.
The pattern is simple: companies have spent years hardening their own systems, so attackers go after the softer targets around them. A vendor with access to your customer data is a door into your company that you do not control. You can audit it, you can contract it, but you cannot patch it yourself, and you often do not find out it was breached until the data shows up on a leak site.
Regulators have noticed. The question they keep asking is whether a bank is responsible for a vendor's security, and the answer is increasingly yes, at least in the eyes of customers. JPMorgan, Visa and Mastercard all moved fast to disclose, which is the right call. But disclosure after the fact does not undo the exposure.
What customers should do now
If you are a JPMorgan, Visa or Mastercard customer, the advice is boring and correct. Watch for phishing emails and texts that use your name and reference your bank or card. Do not click links in messages about your account; go to the bank's site or app directly. Turn on transaction alerts if you have not already, and check your statements for anything unfamiliar.
If you are in the Reserve program, take it a step further. A targeted phishing attempt against a high-value customer is more likely to be well-crafted, and it may arrive by phone or text rather than email. Be skeptical of any unexpected contact that asks you to confirm details or move money, no matter how legitimate it sounds.
The Rhysida attack on Waterman Group showed what happens when attackers steal a password register and payroll data: the damage spreads for months. A vendor data breach is quieter, but the logic is the same. The data is out, the criminals have it, and the only defense left is vigilance. The companies involved will say their systems were not breached, and that may be true. It is also beside the point. Your data was in a vendor's system, and that system was breached. That is the breach that matters.


