Chase, one of the biggest banks in the United States, hit by a cyberattack
JPMorgan Chase chose a Thursday morning post on X to say the thing no bank wants to say. Attackers hit third-party service providers that work for the bank and reached marketing data those vendors held — data that, in the bank's own words, “may include some customer names and emails.” The bank insists its services never stopped, and that this is not Monday's outage. A criminal group is already claiming the haul. What Chase has confirmed, and what it has not, are two very different lists.

Photo: Jim Henderson — “Chase Bank Bwy & Steinway 2022”, CC BY 4.0, via Wikimedia Commons. File photo of a Chase branch in Astoria, Queens.
The disclosure arrived at 6:17 a.m. Mountain Time on Thursday, November 19, as a post on X. In it, JPMorgan Chase said that third-party service providers of the bank had been targeted in a cyberattack, and that the attackers accessed marketing data in those providers' possession. The sentence that matters is the bank's own: that data “may include some customer names and emails.”
Chase is the largest bank in the United States, and a sentence like that, from an institution of that size, is never small — even when the words are carefully bounded. The bank moved in the same announcement to draw the boundary itself: there is no interruption to its services, and Chase will contact affected customers directly, offering free credit monitoring where appropriate. What the bank did not say is equally exact. It has not said that card numbers were taken. It has not said that passwords were taken. On the record as Chase wrote it on Thursday, the exposure sits in marketing data, held by vendors, and it reaches names and email addresses.
The claim Chase has not confirmed
According to Reuters, an extortion group calling itself “n0n” has claimed responsibility for the attack. The group says the data it published contains around 16,000 customer email addresses, some of them accompanied by phone numbers and ZIP codes, apparently linked to the bank's Chase Reserve program. Two qualifications travel with every one of those figures, and this magazine prints them in the same breath: Reuters could not independently verify the authenticity of the material, and Chase has not confirmed the group's claim. The 16,000 figure, the phone numbers, the ZIP codes and the Reserve connection all belong to the claim — not to the bank.
The distinction is not pedantry; it is the story. An extortion group is paid in attention and in pressure, and its commercial interest is to make a haul sound as large and as sensitive as possible. A claim of responsibility is a negotiating instrument before it is a fact. What is verified on Thursday is narrower and, in its own way, more uncomfortable: the bank itself confirms that attackers reached customer data — it simply has not confirmed whose telling of the scale is true. Until Chase or an independent verification settles the question, the group's numbers describe what a criminal organization wants believed.
One detail of the claim deserves its own caution. If the group's description were accurate, the dataset would not be a random slice of Chase's customer base: material tied to the Chase Reserve program would skew toward the bank's premium cardholders — precisely the customers a phishing operation would most want to reach by name. That conditional is doing real work in this paragraph. The Reserve connection is part of the claim, not part of the confirmation, and it should change no reader's behavior today beyond the vigilance the confirmed facts already justify. It is recorded here because, if it is ever confirmed, it will be the detail that defined the incident.
The card networks are in the story — because the data was not at the bank
Visa and Mastercard are also aware of the incident, according to the same reporting. Visa's position draws the map of where this actually happened: its own systems were not involved, and the incident took place at an external provider in Asia-Pacific. Read together with Chase's statement, the picture is consistent across every source reporting it: the data that may be out was not sitting in the bank's own systems. It was sitting with the companies the bank hires.
That is the structural fact underneath the headline. A modern bank is a web of vendors, and marketing data is precisely the kind of data that lives outside the vault — names, emails, the raw material of campaigns, held by the firms that run them. The attackers, on the bank's own account, never needed the vault. They went to the firms outside it, where the security budget is smaller and the data, for the purposes of a phishing campaign, is nearly as good. Chase's customers are now exposed, if they are exposed, through the least defended door in the building: somebody else's.
This is not Monday's outage — Chase says so itself
The timing guarantees the confusion, so the bank addressed it head-on. On Monday, November 16, a payments failure hit several of the largest banks in the United States, Chase among them — an incident this magazine covered at the time. Chase attributed that outage to a software bug in its own hardware. On Thursday, the bank stated plainly that the cyberattack is not connected to Monday's failure. On the record as both the bank and Reuters present it, the two events have different causes, different systems and different authors: Monday was an internal failure; Thursday was an external attack on third parties.
The denial matters because the alternative reading writes itself — one bank, two failures, four days — and because it is exactly the reading the verified record does not support. Two bad weeks in a row is a story. A single hidden catastrophe behind both would be a much bigger one, and no source reporting this incident has produced evidence for it. What the record supports is narrower and stranger: the largest bank in the country had an ordinary, embarrassing internal failure on Monday, and then, on Thursday, had to announce that criminals had been inside its vendors.
What is known so far
- Chase confirmed on Thursday (post on X, 6:17 a.m. MT) that third-party service providers were targeted in a cyberattack.
- The attackers accessed marketing data held by those providers; per the bank, it “may include some customer names and emails.”
- The bank reports no interruption to its services.
- The bank says the attack is not connected to Monday's outage, which it attributes to a software bug in its own hardware.
- Chase will contact affected customers directly and will offer free credit monitoring where appropriate.
- Visa says its systems were not involved and places the incident at an external provider in Asia-Pacific.
What is not known
- Whether the n0n group's claim is authentic — Reuters could not verify it independently, and Chase has not confirmed it.
- How many customers are affected — the bank has published no figure; the ~16,000 emails belong to the group's claim.
- Which providers were hit — Chase has not named them.
- Whether card numbers or passwords were taken — the bank has not said that they were.
If you bank with Chase, the risk to manage is phishing
The practical reading for customers starts from what the bank actually confirmed: names and email addresses — plus, if the unverified claim is accurate, some phone numbers and ZIP codes. That is not the key to anyone's account. It is, however, the complete starter kit for a convincing phishing message. A note that knows your name, your bank and your ZIP code does not read like spam, and the days after a disclosure like this one are precisely when such notes arrive.
The bank's own plan is therefore the first line of defense: Chase says it will contact affected customers directly. Treat that as the only channel that counts. Any email, text or call that claims to be Chase and asks for a password, a code or a card number should be treated as hostile until proven otherwise — no legitimate follow-up to this incident needs your password. Verify anything through the official app or the number printed on the back of your card, never through a link that arrives uninvited. And where the bank offers free credit monitoring through its own channels, it is worth accepting.
Beyond that, the accounts themselves can simply be watched: the bank reports no interruption to its services, and no source it has endorsed claims that balances or credentials are in play. The exposure Chase has confirmed is an exposure of contact data. The danger it creates is not that someone walks into your account — it is that someone writes to you, by name, pretending to be the bank that just admitted your name got out.
This story remains under active follow-up. We are watching for any further word from JPMorgan Chase or from the group claiming responsibility for the attack.
Published Thursday, November 19, 2026.
𝐆𝐄𝐓 𝐅𝐑𝐄𝐄 𝐅𝐔𝐋𝐋 𝐌𝐀𝐆𝐀𝐙𝐈𝐍𝐄 𝐀𝐓 thebuyerspulse.com
Sources
- JPMorgan Chase, statement published on X (Thursday, November 19, 2026, 6:17 a.m. MT): third-party service providers targeted in a cyberattack; marketing data accessed that “may include some customer names and emails”; no interruption to services; no connection to Monday's outage; affected customers to be contacted directly, with free credit monitoring where appropriate.
- Reuters (November 19, 2026): the bank's disclosure; the extortion group n0n's claim of ~16,000 customer emails, some with phone numbers and ZIP codes, apparently linked to the Chase Reserve program — not independently verified by Reuters; Visa and Mastercard aware; Visa: its systems were not involved and the incident occurred at an external provider in Asia-Pacific.
- Gizmodo (November 19, 2026) · Tampa Bay 28 / Associated Press · The Sun · SkimWire · Cybernews via Newsweek: same-day coverage of the disclosure.
- The Buyer's Pulse (November 17, 2026): the Monday, November 16 payments outage at major US banks — the incident Chase says is unrelated to this attack.
- Photo: Jim Henderson — “Chase Bank Bwy & Steinway 2022”, CC BY 4.0, via Wikimedia Commons. File photo of a Chase branch in Astoria, Queens.