Better tools. Better news.
Saturday, November 21, 2026 · UTC
Finance

Ransomware gang n0n leaks JPMorgan high-net-worth customer contact data

Ransomware group n0n published 16000 JPMorgan Chase high-net-worth customer contact records.

TruthFoundry News Desk
References:
Share on X
Stands on 12 placed sources from 4 publishers.
As of 2026-11-19 17:11 UTC. Market figures are as the cited sources reported them at that time and may have moved since. This is news, not investment advice.
Cybernews researchers reported that ransomware gang n0n published approximately 16,000 customer email addresses linked to JPMorgan Chase's Reserve card program. [1] JPMorgan Chase stated on November 19 2026 that third-party service providers to the bank were targeted in a cyber attack, and attackers accessed vendor-held marketing customer data. [2][3] The Wall Street Journal reported on Thursday that a ransomware group leaked customer data belonging to Visa, Mastercard, and JPMorgan Chase via a third-party cyberattack. [4][5] On November 19, Mastercard confirmed that a cyberattack on a third-party service provider exposed limited data for some cardholders enrolled in a specific benefits programme. [6][7] Ransomware group n0n claimed it stole sensitive data from Visa and JPMorgan Chase, issuing a 48 hour ransom deadline before public leaks. [8] JPMorgan Chase confirmed no bank services were disrupted, and stated affected customers will be offered complimentary credit monitoring support. [9] n0n added JPMorgan Chase to its public leak site on November 16 2026 alongside 58 other organizations including Visa and Mastercard, with a 48 hour negotiation deadline. [10] Visa stated that no payment card numbers were compromised, its own systems were not breached, and the affected third-party provider operates in the Asia-Pacific region. [11][12]
Proof12 sources · 4 publishers · signed
What this stands on
  1. Cybernews researchers reported that ransomware gang n0n published approximately 16,000 customer email addresses linked to JPMorgan Chase's Reserve card program. · ZeroHedgeUnited States
  2. JPMorgan Chase stated on November 19 2026 that third-party service providers to the bank were targeted in a cyber attack, and attackers accessed vendor-held marketing customer data. · ZeroHedgeUnited States
  3. JPMorgan Chase stated attackers accessed marketing data including customer names and email addresses, with no disruption to bank services. · Investing.com
  4. The Wall Street Journal reported on Thursday that a ransomware group leaked customer data belonging to Visa, Mastercard, and JPMorgan Chase via a third-party cyberattack. · Investing.com
  5. The Wall Street Journal, citing cybersecurity firm SOCRadar, reported that ransomware group n0n claimed responsibility for this cyberattack. · Hindustan TimesIndia
  6. On November 19, Mastercard confirmed that a cyberattack on a third-party service provider exposed limited data for some cardholders enrolled in a specific benefits programme. · Hindustan TimesIndia
  7. Mastercard confirmed the breach exposed limited information for a subset of cardholders enrolled in a specific benefit program, with no impact on payment networks. · Investing.com
  8. Ransomware group n0n claimed it stole sensitive data from Visa and JPMorgan Chase, issuing a 48 hour ransom deadline before public leaks. · TechRadar
  9. JPMorgan Chase confirmed no bank services were disrupted, and stated affected customers will be offered complimentary credit monitoring support. · ZeroHedgeUnited States
  10. n0n added JPMorgan Chase to its public leak site on November 16 2026 alongside 58 other organizations including Visa and Mastercard, with a 48 hour negotiation deadline. · ZeroHedgeUnited States
  11. Visa stated that no payment card numbers were compromised, its own systems were not breached, and the affected third-party provider operates in the Asia-Pacific region. · Investing.com
  12. Both Visa and Mastercard stated that their own internal systems and payment networks were not impacted by the cyberattack. · Hindustan TimesIndia
They publish from United States, India. We do not know which country the other 2 publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · signed receipt ✓ · 12 sources · v 001The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Thursday, November 19, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world4 publishers reported the events across 4 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
They publish from United States, India. We do not know which country the other 2 publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)58616fcf3b7502a0026607481bc0d65f30c0ac8d85beff6be51610b21bee380c
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receipt signature (Ed25519)UZm1SI99wWeOxm7z87IZppQVOJwU6uBO7Y_fIdYch5pJlDtqEXXEJfFaT7OgsyUiA3HI2r7hvpM9L4KF3d5xAg
Signing keybMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUE
SignerDRM3 · data-extract v1
Filed asingest:raw_newsroomfloor.stories v1
Slice hash2fbdeca2505102e87fb76bd8cd6c213d6ef9981854fe9b208054d5c71b5bf823
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.