Chase says vendor cyberattack may have exposed customer names and emails
Chase says a vendor cyberattack may have exposed some names and email addresses. Here’s how to verify a notice, handle suspicious texts and report fraud.
JPMorgan Chase said Thursday, Nov. 19, that a cyberattack targeting service providers may have exposed names and email addresses for some customers. The bank said its investigation pointed to marketing data held by those outside companies. Its public statement gave customers a preliminary description of the files the attackers may have accessed.
The Associated Press reported that the material appeared to contain mostly email addresses, with some phone numbers. The AP also reported that Chase described the affected information as separate from credit card data. Visa and Mastercard confirmed vendor-related exposure to the AP and said customer payment information was unaffected. Chase’s public statement left the total number of affected Chase customers and the vendors’ identities unspecified.
For customers, the immediate decision is how to respond if a notice arrives. Independent verification matters because a caller or sender can repeat a customer’s name or an incident mentioned in the news. Chase’s Security Center advises people to contact the bank through a known number when they are unsure who sent a request.
How Thursday’s disclosure fits with Monday’s outage
Chase customers encountered service problems earlier in the week. On Monday, Nov. 16, a technical issue caused delays at Chase and affected some payments to Chase accounts through Zelle, according to the AP’s coverage of the banking delays. Chase attributed the service disruption to a software problem. The bank said Tuesday its systems were operating normally, the AP subsequently reported.
Thursday’s disclosure concerned information that outside vendors held. Chase described the two incidents as separate. That timeline matters when a customer tries to piece together whether a delayed payment or an unexpected email had anything to do with the attack. A Monday transfer problem belongs with the transaction’s status and support history. A Thursday breach notice belongs with the account’s security messages and the bank’s instructions for affected customers.
What to do with a notice, a text or an unfamiliar charge
If a breach notice arrives: Open the Chase app or go to the bank’s site independently. For a phone call, use the number on the back of your card or on a statement. Ask whether the bank sent the notice, which account or program it relates to, and whether the bank has identified the information involved. Keep the notice and any case number you receive through the verified channel.
If someone calls or texts about your account: End the exchange and start a new one through a number or app you already trust. A text can carry real details about a public incident and still come from an impostor. Treat links, attachments and requests to relay a one-time passcode as reasons to pause. The Federal Trade Commission’s phishing guidance recommends contacting the company using a phone number or website you know. It also explains where to report suspicious messages.
If you see a transaction you do not recognize: Open the transaction record through the app or your statement, then contact the bank directly through Chase’s fraud reporting channels. Give the bank the date, amount and merchant as shown on your account. Ask which steps apply to that account. The transaction record is more useful to the fraud team than guessing whether an exposed email address and the charge came from the same source.
What a fuller disclosure would clarify
The bank’s wording describes a category of information, marketing data, and gives two potential examples, names and emails. The AP’s description of some phone numbers adds detail from its reporting. As notices reach customers, the questions to track are which programs or services were involved, which fields each vendor stored, how the bank is notifying affected people and what help it is offering.
That distinction can change a customer’s next step. Someone receiving an unsolicited text can report it and check their account through known channels. Someone who entered credentials through a link has a separate account-security issue to report promptly. The FTC’s guide for people who responded to a phishing message outlines steps based on what they shared.
A verified notice can also be useful later. Save a copy that shows the date, the affected product if named, and any steps the bank recommends. If the scope changes, that record gives you something concrete to compare with a later communication from the bank.
The public disclosure gives a starting point. The bank’s verified customer channels are where account-specific answers should come from. See Newsmerica’s guide to outage and cyber incident records for more on which notices answer questions about cause, scope and recovery.
Trust & transparency
How we handled this story
Verified Chase’s Nov. 19 statement through its official public embed, corroborated the distinction from the Nov. 16 outage with AP reporting, and checked Chase and FTC reporting guidance.
Grounded in this reporting
Ask Newsmerica
Ask about this article. Answers quote the closest published passages and link back to their sources.
This tool retrieves article passages; it does not add outside facts.Keep exploring
More from Newsmerica
Related coverage
Business & Economy
Black Friday 2026 dates for Walmart, Target, Best Buy and Home Depot
Business & Economy
30 states join FTC’s Dollar General lawsuit as Family Dollar deal awaits approval
Business & Economy



