The JPMorgan third-party data breach exposed marketing data, including customer names and email addresses, held by vendors, showing that vendor compromise now reaches even the largest banks.
Infosecurity Magazine reported the story on November 19, after JPMorgan confirmed on X that attackers had accessed certain marketing data held by impacted third-party vendors. The disclosure came shortly after the ransomware group N0n listed JPMorganChase, Visa and Mastercard on its data leak site. If you run a regulated business that shares customer data with marketing, loyalty or concierge vendors, this story is directly relevant to you: the data that leaked appears to have lived outside the banks' own networks, at companies most customers have never heard of.
Key Takeaways
- JPMorgan confirmed on November 19, at 13.29 GMT, that attackers accessed certain marketing data held by third-party vendors, which may include some customer names and email addresses.
- The bank stated there is no disruption to its services and that affected customers will be offered support, including complimentary credit monitoring, where appropriate.
- JPMorgan separately stated the incident is not related to a November 16 service disruption caused by a software bug in its on-premise hardware systems.
- According to a Wall Street Journal report cited by Infosecurity Magazine, the leak included 16,000 customer email addresses linked to JPMorgan's invitation-only Reserve card program, typically reserved for clients with $10m or more in managed assets.
- No compromised third-party vendor has been named, and it is unknown whether the JPMorgan, Visa and Mastercard incidents are related, even though all three followed N0n listing the firms on its leak site.
What Happened: The Facts in Detail
The disclosure
JPMorgan, part of the JPMorganChase group, revealed on X on November 19, at 13.29 GMT, that it believes attackers accessed certain marketing data held by impacted vendors. The bank said that data may include some customer names and email addresses. Chase, the consumer and retail banking arm of JPMorganChase, issued the same statement on its own X account the same day.
Two points in the statement deserve attention. First, JPMorgan said there is no disruption to its services. Second, the bank committed to contacting affected customers directly where appropriate and offering support, including complimentary credit monitoring. That combination, services intact but customer data exposed, is the signature of a vendor-side compromise rather than an intrusion into the bank's core systems.
The ransomware claims that preceded it
The notification came after the ransomware group N0n listed JPMorganChase, Visa and Mastercard on its data leak site. Reuters reported that Visa and Mastercard confirmed they had experienced data breaches as a result of a third-party compromise. Visa said that no payment data has been impacted. A Mastercard spokesperson said the breach affected non-payments information from a small subset of cardholders enrolled in a specific benefit program.
Following JPMorgan's notification on November 19, N0n reportedly released data relating to customers of the three banks, stating that they had each missed a 48-hour deadline to pay its extortion demand.
What leaked
According to a Wall Street Journal report, personal data from thousands of customers of the three financial organizations was included in the leak. That includes 16,000 customer email addresses linked to JPMorgan's invitation-only Reserve card program, typically reserved for clients with $10m or more in managed assets.
That detail matters beyond its headline value. The Reserve card program is a marketing and concierge operation. The exposed data set, names and email addresses tied to a premium program, is exactly the kind of information a vendor collects to run outreach on a brand's behalf. It is not account credentials, transaction records or payment data, at least as far as the confirmed reporting goes. But it is high-value data for attackers: an email list of ultra-high-net-worth clients is a targeting list for sophisticated phishing and social engineering.
What this was not
JPMorgan added that the incident is not related to a service disruption on November 16, which it said was caused by a software bug in its on-premise hardware systems. The bank drew that line explicitly, presumably because customers experiencing the outage might reasonably have assumed the two events were connected. They were not, per the bank's own statement.
Who is N0n
N0n is a relatively new ransomware group, first observed in September 2026. The actor has reportedly threatened victims with destroying their backup infrastructure if they do not give in and pay its extortion demand. Rafe Pilling, senior director of threat intelligence at the Sophos Counter Threat Unit, cautioned that the group is having a "real impact" but that some of its claims around major brands need to be treated with caution.
Why the JPMorgan Third-party Data Breach Matters Technically
The most important technical fact in this story is one Sophos's Pilling articulated clearly: "In several cases, the data appears to have come from third-party providers running marketing, loyalty or concierge programs, rather than from the brands' own networks." He added, "That still matters to the individuals whose data has been exposed, but it's very different from saying criminals have broken into Visa or JPMorgan and are moving around inside their systems."
That distinction is the whole story for a business reader. When a bank hires a vendor to run a loyalty program, that vendor accumulates a copy of customer data: names, email addresses, program tier, sometimes spending indicators. The bank's own security perimeter may be excellent. The vendor's may not be. The attacker does not need to defeat the bank; it needs to defeat whichever vendor holds the easiest copy of the data.
This pattern is not unique to finance. Verizon's 2025 Data Breach Investigations Report found that third-party involvement in breaches rose from 15% to 30%. In healthcare, business associates accounted for about 66% of breached records in 2024, and the Change Healthcare breach ultimately reached 192.7 million individuals in the final HHS filing of July 31, 2025. The JPMorgan third-party data breach fits a well-established trend: the data your organization shares is attacked wherever it is weakest, not wherever it originated.
There is also an extortion mechanics lesson here. N0n set a 48-hour deadline and published data when it expired, and has reportedly threatened to destroy victims' backup infrastructure if demands are not paid. Double and triple extortion has become the standard playbook: steal first, encrypt second, publish third. A vendor holding your customer data may face that playbook with far less incident response maturity than you have. When the deadline passes, your customers' names are on a leak site, and your brand is in the headline, even though your network was never touched.
Finally, note what the attackers targeted: marketing data. Organizations routinely apply their strictest controls to payment systems and core databases while treating marketing platforms as low risk. The 16,000 Reserve card email addresses show that marketing data can be sensitive enough to drive extortion demands against three of the world's largest payment and banking brands. Data classification programs that label customer email lists as trivial are miscalibrated.
For organizations subject to incident response obligations, the governance question is equally pointed. NIST SP 800-61 Rev. 3, the incident response guidance finalized on April 3, 2025, frames incident response as something to be incorporated throughout cybersecurity risk management activities under the NIST Cybersecurity Framework 2.0, not as an ad hoc reaction. A vendor breach that exposes your customers is your incident to manage: your notification obligations, your customer communications, your credit monitoring offer. JPMorgan's statement, offering complimentary credit monitoring and direct contact with affected customers, shows what that responsibility looks like in practice, at a scale few organizations could absorb easily.
CISA's Cross-Sector Cybersecurity Performance Goals 2.0 make the same point from the defensive side. The CPGs are a voluntary baseline of practices aimed at reducing risk to critical infrastructure, updated to align with NIST CSF 2.0 and its new GOVERN function, which covers leadership accountability, oversight, and risk management. Vendor risk sits squarely inside that governance scope. If leadership does not know which vendors hold customer data, what data they hold, and how those vendors detect and respond to incidents, the organization cannot govern that risk, no matter how strong its internal controls are.
What the Evidence Does and Does Not Show
Precision about the limits of the reporting matters here, because ransomware groups exaggerate and early breach reporting is often wrong. Here is what is established, and what is not.
Established by the sources
- JPMorgan confirmed, in its own statement on X on November 19, that it believes attackers accessed certain marketing data held by impacted vendors, which may include some customer names and email addresses.
- JPMorgan stated there is no disruption to its services, and that the incident is unrelated to the November 16 service disruption caused by a software bug in on-premise hardware systems.
- Visa and Mastercard confirmed breaches resulting from a third-party compromise, per Reuters reporting. Visa said no payment data was impacted; Mastercard said the breach affected non-payments information from a small subset of cardholders in a specific benefit program.
- The Wall Street Journal reported that the leak included 16,000 customer email addresses tied to JPMorgan's Reserve card program.
- Sophos's threat intelligence lead assessed that the data appears to have come from third-party providers running marketing, loyalty or concierge programs, not from the brands' own networks.
Not known at the time of writing
- The compromised third-party vendors have not been named. None of the reporting identifies which companies were breached.
- It is unknown whether the JPMorgan, Visa and Mastercard incidents are related. All three followed N0n listing the firms on its leak site, but a shared listing is not proof of a shared vendor or a shared attacker operation.
- The full scope of the data exposed beyond the reported figures is not established. JPMorgan's own language was careful: it "believes" attackers accessed "certain marketing data" which "may include" some customer names and email addresses.
- How the attackers got into the vendor environment, and when, is not stated in any of the reporting.
- The accuracy of N0n's broader claims requires caution. Sophos's Pilling explicitly warned that some of the group's claims around major brands need to be treated with caution, and distinguished between data exposed via third-party providers and criminals operating inside the brands' own systems.
That last point deserves emphasis for any reader who consumes breach news. A leak site listing is a negotiating tactic, not a verified finding. The verified facts here come from the banks' own confirmations and from named reporting, not from N0n's claims. Sophos's framing, that the data appears to have come from third-party providers rather than the brands' networks, is the most technically grounded assessment available, and it reframes the entire incident: this is a story about vendor security, not about a breach of JPMorgan's core systems.
The Compliance and Risk Implications for Regulated Organizations
The JPMorgan third-party data breach is not just a banking story. It is a case study in how regulated organizations inherit risk from vendors they do not control, and how extortion groups now exploit that gap. The attackers reportedly did not breach JPMorgan's own network. They compromised third-party vendors running marketing, loyalty, and concierge programs, which is precisely the kind of supplier relationship that rarely appears on a board risk register with the same rigor as core banking systems.
For regulated businesses, the lesson is uncomfortable but clear: your compliance obligations do not stop at your network boundary, and neither does your breach exposure. When a vendor holding your customer data is compromised, regulators, customers, and in some cases the Department of Justice will treat the incident as yours. The CISA Cross-Sector Cybersecurity Performance Goals 2.0 exist partly for this reason, offering a baseline set of practices broadly applicable across critical infrastructure, updated to align with the NIST Cybersecurity Framework 2.0 and its new GOVERN function, which emphasizes leadership accountability and oversight of risk, including risk that sits with suppliers.
Organizations subject to CMMC and NIST SP 800-171 already live with this reality. The DFARS 252.204-7019 requirement to post a current NIST SP 800-171 self-assessment score to the Supplier Performance Risk System reflects a federal judgment that supplier risk is contract risk. The JPMorgan incident shows why that judgment applies well beyond defense contracting. A marketing vendor with a weak security posture can expose customer names and email addresses that trigger notification duties, extortion campaigns, and reputational damage, all without a single attacker touching your environment.
There is also a governance dimension. JPMorgan issued its statement on November 19 and explicitly distinguished the breach from an unrelated service disruption on November 16 caused by a software bug in on-premise hardware systems. That separation matters. Regulated organizations need incident response processes, aligned with NIST SP 800-61 Rev. 3, that can distinguish, document, and communicate multiple simultaneous events accurately. Conflating an outage with a breach, or vice versa, creates regulatory and legal exposure of its own.
What This Means for Regulated Industries
Defense Contractors
Defense contractors should read this story as a warning about the vendors that sit outside their CMMC boundary. If you enclave CUI into a narrowly scoped boundary, that is good practice, but ask what customer or program data lives in vendor-run marketing, event, or membership systems. Those systems rarely carry CUI, but they carry names, emails, and organizational affiliations that are valuable to foreign intelligence services and criminal groups alike. Your NIST SP 800-171 incident response family requires an operational incident handling capability and the tracking, documenting, and reporting of incidents. A vendor breach involving your customer data should be handled under that process, not routed to marketing. DFARS 252.204-7012 requires reporting a cyber incident affecting covered defense information to DoD within 72 hours of discovery, and you cannot meet that deadline with a vendor relationship you discovered only after the extortion post went live.
Healthcare
Healthcare organizations have already learned this lesson the hard way. Business associates accounted for about 66% of breached healthcare records in 2024, and Change Healthcare's breach ultimately reached 192.7 million individuals in the final HHS filing of July 31, 2025. The JPMorgan incident confirms the pattern extends to financial services marketing vendors, and it will extend to healthcare marketing, scheduling, and patient engagement vendors too. The HIPAA Breach Notification Rule at 45 CFR 164.404, 164.406, and 164.408 applies regardless of whether the compromise happened on your servers or your business associate's. Review your business associate agreements, confirm which vendors hold patient contact data, and verify that your risk analysis under 45 CFR 164.308(a)(1)(ii)(A) actually covers them rather than stopping at your own infrastructure.
Legal
Law firms hold client data that is attractive precisely because it is sensitive and often time-critical: deal information, litigation strategy, settlement figures. The N0n group's approach, listing major brands on a leak site and releasing data after a missed 48-hour extortion deadline, is a playbook that works against firms of any size. Firms should treat third-party e-discovery, marketing, and client portal vendors with the same scrutiny they apply to their own systems.
Financial Services
For banks, credit unions, and fintech firms, the JPMorgan third-party data breach is a direct preview of their own worst case. The leaked data reportedly included 16,000 customer email addresses linked to JPMorgan's invitation-only Reserve card program, typically reserved for clients with $10 million or more in managed assets. That is a targeted phishing and social engineering list of the bank's most valuable clients, and it was compiled by a marketing vendor, not the bank. Financial firms should map every vendor that touches customer contact data, confirm PCI DSS scoping for any vendor in or near the cardholder data environment, and prepare for the reality that extortion groups will name them publicly whether or not the claims are accurate. As Sophos' Rafe Pilling cautioned, some claims around major brands need to be treated with caution, but the reputational cost of the accusation lands regardless.
An Action Plan for This Month
You cannot fix vendor risk in a month, but you can take concrete steps that materially reduce exposure. Here is an ordered plan a security or IT leader can start now:
- Inventory every vendor that holds customer or patient contact data. Include marketing platforms, loyalty and concierge programs, event management tools, and email service providers. The JPMorgan breach came through exactly this category, and most organizations cannot produce this list from memory.
- Classify what each vendor actually holds. Names and email addresses are lower sensitivity than payment data, but they fuel phishing campaigns against your highest-value customers. Rank vendors by the sensitivity and value of the data, not by contract size.
- Review contractual security and notification terms for your top-tier vendors. Confirm each vendor is obligated to notify you of an incident promptly, to cooperate in your investigation, and to meet the security commitments your regulators expect of you.
- Test your own incident response process against a vendor-originated scenario. NIST SP 800-61 Rev. 3 frames incident response as part of broader cybersecurity risk management. Run a tabletop where the breach starts at a vendor: who calls whom, who notifies regulators, who talks to customers, and how fast.
- Confirm your regulatory reporting paths and pre-position what you can. If you are a defense contractor, obtain the DoD-approved medium assurance certificate needed for DFARS 252.204-7012 reporting in advance, because you cannot get one during an incident. If you are a covered entity, confirm your HIPAA notification workflow against 45 CFR 164.404, 164.406, and 164.408.
- Preserve evidence obligations in vendor contracts. After a reported defense incident, affected system images and monitoring data must be preserved for at least 90 days. Make sure your vendors have equivalent preservation duties so evidence does not disappear before you need it.
- Harden the human target. Leaked email addresses feed phishing and impersonation. Verify MFA is enforced on your customer-facing and executive accounts, and align password guidance with NIST SP 800-63B-4, which favors length over composition rules and eliminates forced periodic rotation.
- Validate your monitoring covers vendor-facing channels. Cloud coverage across Microsoft 365, Azure, AWS, and Google Workspace should detect unauthorized access, configuration drift, impossible travel, and suspicious API activity, because vendor integrations often connect through those platforms.
- Benchmark your program against the CISA Cross-Sector Cybersecurity Performance Goals 2.0. They are a voluntary but prioritized baseline, aligned to NIST CSF 2.0, and they give leadership a defensible answer to the question of whether essential protections were in place.
- Establish a standing vendor risk review cadence. A one-time assessment decays. Quarterly review of your highest-risk vendors, tied to your governance process, keeps the program alive and gives auditors the evidence they expect.
How Petronella Technology Group, Inc. Helps
Petronella Technology Group, Inc. helps regulated organizations turn this kind of incident into a manageable, documented program rather than a scramble. Our Third-Party Risk Management Services are built for exactly the failure mode this breach illustrates: vendors that hold your customers' data but sit outside your direct control. For organizations that need executive-level ownership of the problem without the substantial all-in annual cost of a full-time CISO, our vCISO services deliver a written current-state assessment within 30 days of onboarding, a prioritized 90 to 180 day remediation roadmap, and a first quarterly board memo at day 75 to 90.
Detection matters too. If a vendor compromise leads to credential abuse or suspicious activity in your environment, you need to see it fast. Our Managed Detection and Response service combines 24/7 threat monitoring, AI-powered analytics, and human-led investigation, with full coverage operational within 30 days of contract signing, and reporting designed to provide the evidence auditors need for HIPAA, CMMC, PCI DSS, SOC 2, and NIST 800-171 verification. Our AI-augmented hybrid SOC runs on a private AI cluster, which matters for defense industrial base and healthcare clients that cannot send CUI or PHI to a public-cloud SOC.
When an incident does occur, response speed and privilege protection determine the outcome. Our Incident Response Retainer Services and data breach forensics capabilities give you a pre-established path, and our broader cybersecurity services and compliance programs address the underlying control gaps. For defense contractors, our supply chain security services and CMMC readiness practice, delivered by a Cyber AB Registered Provider Organization (RPO #1449) where every practitioner holds the CMMC-RP designation, address the vendor and subcontractor dimension directly.
The first step is a free 30-minute scoping consultation. Call Penny, our AI assistant, at 919-348-4912, or reach us through the contact form.
Related reading
- Cyber Incident Response Plan Guide
- Amazon Data Breach Exposes Customer Names & Emails
- Zero Trust Evidence You Can Ask Third-Party AI Support
- NVIDIA Probes Gentlemen Ransomware Breach Claims
- French Bank Heist Service Provider Attack Hits $133 Million
Sources
- JPMorgan Confirms Customer Data Breach Following Third-Party Compromis
- Cross-Sector Cybersecurity Performance Goals
- SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity R
Frequently Asked Questions
What data was exposed in the JPMorgan third-party data breach?
JPMorgan stated on November 19 that it believes attackers accessed certain marketing data held by impacted vendors, which may include some customer names and email addresses. Following the notification, the N0n group reportedly released data including 16,000 customer email addresses linked to JPMorgan's invitation-only Reserve card program, according to a Wall Street Journal report.
Did hackers break into JPMorgan's own systems?
No. Based on the available reporting, the compromise occurred at third-party vendors running marketing, loyalty, or concierge programs, not inside JPMorgan's network. As Sophos' Rafe Pilling noted, that is very different from criminals breaking into the bank and moving around inside its systems, though it still matters to the individuals whose data was exposed. JPMorgan also stated there was no disruption to its services.
Who is the N0n ransomware group?
N0n is a relatively new ransomware group, first observed in September 2026. It listed JPMorganChase, Visa, and Mastercard on its data leak site, reportedly released customer data after the banks missed a 48-hour extortion deadline, and has reportedly threatened to destroy victims' backup infrastructure if they do not pay. Experts caution that some of its claims around major brands should be treated with caution.
Were the Visa and Mastercard breaches related to the JPMorgan incident?
It is not known. Visa and Mastercard both confirmed breaches resulting from a third-party compromise, with Visa stating no payment data was impacted and Mastercard indicating non-payment information from a small subset of cardholders in a specific benefit program was affected. None of the compromised third-party vendors have been named, so whether the incidents share a common vendor remains unknown at the time of writing.
What should my organization do if a vendor holding our customer data is breached?
Treat it as your incident. Activate your incident response process, confirm what data and which customers are affected, meet your regulatory notification obligations, and preserve evidence. NIST SP 800-61 Rev. 3 provides recommendations for incorporating incident response throughout cybersecurity risk management, and the NIST SP 800-171 incident response family requires an operational incident handling capability, not just an external report after the fact.
How can we reduce third-party breach risk before it happens?
Start with a complete inventory of vendors holding customer or patient data, classify what they hold, and review their contractual security and notification commitments. Then validate your own monitoring, incident response readiness, and governance oversight. The CISA Cross-Sector Cybersecurity Performance Goals 2.0, aligned to NIST CSF 2.0, offer a prioritized baseline for these protections, and a vCISO-led vendor assessment program can turn that baseline into a documented, auditable practice.
Related reading: NVIDIA Probes Gentlemen Ransomware Breach Claims.
Related reading: NVIDIA Probes Gentlemen Ransomware Breach Claims.
Free online course from the Petronella Technology Group, Inc. Training Academy
Free crash course: 5 practical steps to protect your data and meet HIPAA, CMMC, PCI-DSS, and FTC Safeguards compliance standards.
Price: Free
Start the free course Cybercrime and Identity Theft Defense Mastery ($997)
Free, practical, and specific to regulated environments. We will email it to you.
No spam. Unsubscribe anytime.