Chase Says Vendor Cyberattack Exposed Customer Names and Emails
JPMorgan Chase says attackers breached third-party vendors and accessed marketing data that may include customer names and email addresses. The data is ideal raw material for Chase-branded phishing.

JPMorgan Chase said on 19 November 2026 that third-party companies providing services to the bank were hit by a cyberattack, and that the attackers likely accessed marketing data those vendors held for Chase. In a statement published on its official X account, the bank said the data may include some customer names and email addresses.
Chase stressed that its own services were not disrupted and that the incident is unrelated to the service disruption some customers saw earlier in the week. It said it will contact affected customers directly where appropriate and offer support, including free credit monitoring.
For the email industry, this is a textbook marketing data exposure: the records did not leak from the bank's core systems but from the vendors that handle its marketing. Names paired with confirmed customer email addresses are exactly what a phishing crew needs to send convincing messages that look like they come from a large bank.
Key facts
- Who: JPMorgan Chase, through third-party service providers (vendors not named).
- What: a cyberattack on those vendors; attackers believed to have accessed Chase marketing data.
- Data at risk: some customer names and email addresses, according to Chase.
- Services: no disruption to Chase services, and no link to the earlier outage, the bank says.
- Response: Chase will contact affected customers where appropriate and offer free credit monitoring.
- Disclosed: 19 November 2026, on the bank's official X account.
What Chase has confirmed
The bank's statement is short and careful. It says the attack targeted third parties that provide services to the firm, that the investigation is still ongoing, and that the attackers are believed to have accessed certain marketing data held by those vendors. Chase used the words "may include" for names and email addresses, which means the exact fields and the number of customers involved are not yet established.
Chase has not named the vendors, has not given a number of affected customers, and has not said when the intrusion took place. SMTPedia will update this article when the bank or a regulator publishes more details.
Why a marketing vendor breach matters to email teams
Marketing data usually lives far from a bank's hardened core: in email service providers, customer data platforms, loyalty and benefits programmes, and agencies. Each of those holds a copy of the customer list, and each copy is a separate attack surface. When one of them is breached, the exposed list is clean, current and tied to a trusted brand.
The most likely follow-up is a wave of phishing that impersonates Chase, including fake "data breach" notices that use the incident itself as a lure. Attackers often time these campaigns to land while the real notification emails are going out, so recipients cannot easily tell the genuine message from the fake one.
The sender side: brand protection
For any organisation that sends to a large consumer list, this incident is a reminder that email authentication is the only thing that stops lookalike mail on your own domain. A domain at DMARC p=reject cannot be spoofed exactly in the From header, which pushes attackers toward cousin domains that are easier to spot and block. A verified BIMI logo also gives recipients a visual cue that a message really comes from the brand.
What it means for senders
What changes
Chase customer names and email addresses held by marketing vendors may now be in criminal hands, which raises the risk of convincing Chase-branded phishing. Any brand that shares its list with marketing vendors faces the same exposure.
Who is affected
Chase customers whose data sat with the breached vendors; financial services senders and any company that copies its customer list into third-party marketing tools.
When
Disclosed on 19 November 2026. The investigation is ongoing and customer notifications are expected to follow.
Action checklist
- Map every copy of your list across ESPs, CDPs, agencies and benefits partners, and remove data that a vendor no longer needs.
- Move your sending domains to DMARC p=reject once all legitimate sources pass SPF or DKIM alignment.
- Prepare breach notification templates in advance that never ask recipients to click a login link, so customers can tell them apart from phishing.
- Warn your support team that customers may forward suspicious bank-branded emails, and give them a clear reporting path.
- Review vendor contracts for breach notification deadlines and data minimisation clauses.
- Watch your own complaint and spam trap signals in Google Postmaster Tools and Microsoft SNDS, since impersonation waves can affect how mailbox providers treat your real mail.
Sources
Related on SMTPedia
SMTPedia News follows our editorial standards. Spotted an error? See how we correct it.
Get SMTPedia news first on Google
Add us as a preferred source to see our stories in Top Stories and Discover.
Add as preferred sourceUseful story?
SMTPedia news is free and independent. A coffee helps us keep covering what changes for senders.
Buy SMTPedia a coffeeNewsletter