JPMorgan Chase Says Vendor Breach Exposed Marketing Data, Not Core Systems

JPMorgan Chase says attackers targeted third-party service providers and accessed marketing data those vendors hold on the bank's behalf. The data may include some customer names and email addresses, according to the bank's statement as reported by The Verge, which was published on 19 November 2026.
Chase says there is no disruption to its own services from the attack. Where appropriate, the bank says it will contact affected customers directly and offer support, including complimentary credit monitoring, a service that watches credit records for signs of misuse. The bank also said the vendor incident is not connected to a service disruption some customers experienced earlier this week. That outage, the bank has said, was caused by a software bug, as AP reported.
The disclosure is narrower than the claims circulating around it. Cybernews reported that a ransomware group, a criminal group that steals data and typically demands payment to withhold it, leaked email addresses belonging to around 16,000 JPMorgan Chase customers. According to the same report, the leaked dataset includes information linked to Chase's invitation-only Reserve program. Chase's own statement describes marketing data held by vendors.
The group claiming responsibility for the Chase breach also said it had targeted Visa. Visa confirmed an attack on a third-party vendor in Asia Pacific. The card network said its own systems were not involved and were not impacted, and that there is no indication payment data such as card numbers was affected. Cybernews reported exposed data connected to 6,000 premium Visa customers.
Both incidents, as described by the companies, sit with a third party rather than with the banks' or the card network's core systems. That is the common thread in the public accounts so far. Each firm's exposure runs through a supplier's environment, and each firm's disclosure turns on what that supplier held.
In my view, the marketing data category deserves more attention than its label suggests. Campaign and CRM (customer relationship management) datasets are often copied into vendor platforms for segmentation, enrichment and delivery, and they can sit outside the access controls applied to transaction systems. A name paired with an email address tied to a premium or invitation-only product is enough material for a convincing phishing lure, a fraudulent message built to look genuine. The practical risk to customers is likely to be targeted social engineering rather than direct account access.
The broader context here is vendor concentration. Large financial institutions run hundreds of processors, analytics providers and marketing platforms, and each integration is a path into customer records. Contractual security attestations and periodic assessments are standard, but they rarely map the full chain of subprocessors, the further companies a vendor passes data to, that touch a dataset. Incidents like these tend to push firms toward data minimization in vendor feeds (sending only the fields a task requires), tokenized or pseudonymized identifiers for marketing use, and tighter egress monitoring on vendor connections. Those are concrete controls, and they are available now.
The open questions are the ones the parties have not yet resolved in public: which vendors were involved, how many customers are affected, and whether the Reserve-linked records and the Visa-linked records come from the same supplier chain. Those answers will determine whether the two incidents are separate events or a shared exposure in the same ecosystem. Customers who receive notices should expect direct contact from the institutions, and complimentary credit monitoring gives them a concrete step to take while the investigation continues.


