JPMorgan Chase says a cyberattack involving outside service providers may have exposed customer marketing records containing names and email addresses. Separately, Cybernews researchers reported finding roughly 16, 000 Chase customer email addresses in files that appeared to be linked to the bank’s invitation-only Reserve card program.
- Chase has not named the providers or said how many customers may be affected.
- The 16, 000 figure counts email addresses in files Cybernews reviewed. It is not a confirmed total of affected customers.
- Chase said the data incident did not disrupt its services.
- A separate service slowdown was attributed to a software bug, not the data incident.
What Chase has disclosed
In a statement posted on X on Nov. 19, Chase said its investigation pointed to customer marketing records held by companies that provide services to the bank. The records may have included customers’ names and email addresses.
Chase did not identify the companies, say when the incident occurred or disclose how many customers may have had information accessed. The bank said the incident did not disrupt its services and that it would contact affected customers directly. Support may include complimentary credit monitoring.
Credit monitoring can alert someone to certain changes on their credit report. It does not stop phishing messages or prevent every form of identity theft, so it is not a complete security fix.
What Cybernews found and what it does not prove
Cybernews said its researchers reviewed files posted by a group calling itself n0n and found roughly 16, 000 JPMorgan Chase customer email addresses. The files appeared to be connected to Chase’s invitation-only Reserve card program.
The figure reflects the email addresses in the files Cybernews reviewed. The researchers could not determine whether the files contained the complete dataset, so the number is not a confirmed count of customers affected by the incident Chase described.
The reported link to the Reserve program could make the information useful for targeted phishing, Cybernews senior information security researcher Aras Nazarovas said. A scammer could use a detail such as someone’s connection to a premium card program to make a fraudulent message seem more credible.
This is a plausible risk, but there is no evidence that Chase customers have received phishing messages using these records. Chase has not confirmed that card numbers, passwords or banking credentials were exposed. Customers should be wary of unexpected emails, texts or calls that demand urgent action. Verify requests through Chase’s official app, website or the number on their card. Sophisticated phishing attempts and phishing scams involving cryptocurrency show why caution matters.
The service slowdown was a separate incident
Chase also experienced a service disruption on Nov. 16. Gulf News reported that some customers encountered errors accessing online services and that transactions involving Chase could be delayed. Chase attributed the slowdown to a software bug affecting hardware at its own premises.
Chase said the slowdown was unrelated to the vendor incident. The distinction matters: one involved customer records held by outside providers. The other was an operational problem that the bank attributed to its own software and hardware.
Delays in transactions involving Chase did not mean Zelle’s network was down. Gulf News reported that Zelle’s operator said its network remained operational.
Key questions and answers
-
What information may have been exposed in Chase’s vendor-held records?
Chase said the records may have contained names and email addresses. Cybernews separately reported finding roughly 16, 000 customer email addresses in files its researchers reviewed.
-
Does the 16, 000 figure represent every affected Chase customer?
No. It is Cybernews’s count of email addresses in the files its researchers examined. They could not determine whether those files were complete.
-
Were Chase card numbers or banking credentials exposed?
Chase has not confirmed that card numbers, passwords or banking credentials were exposed. A Reddit post discussing Chase’s disclosure does not change what the bank has confirmed.
-
Did the data incident cause Chase’s Nov. 16 service slowdown?
No. Chase said the incidents were unrelated and attributed the slowdown to a software bug affecting hardware at its own premises.
-
What should Chase customers do?
Be cautious with unexpected messages or calls, especially those that use personal or card-program details to pressure you into acting. Verify requests through Chase’s official channels and check any direct notice from the bank for details about available support.