Nov 20
/
Latest News
JPMorgan, Visa, Mastercard Tie n0n Leak to Vendors
JPMorgan Chase, Visa and Mastercard each acknowledged on Thursday, November 19, that outside service providers had suffered security incidents, three days after the extortion group n0n named them on its leak site and began releasing files it said were linked to them. All three said their own systems and payment data were not touched. None named the vendors involved or said how many customers were affected, and it is still not clear whether a single supplier sits behind all three leaks.
The group listed the companies on its leak site on November 16. According to a screenshot captured by the cybercrime tracking platform eCrime.ch and cited by Reuters, n0n claimed to hold JPMorgan cardmember engagement records covering hundreds of thousands of marketing campaign interactions tied to tens of thousands of email addresses. Cybernews reported that the gang also threatened to expose full names, mobile numbers, issuing bank and BIN details, and travel and dining bookings made by premium cardholders. The group set a 48-hour payment deadline, and when it passed, it published the data. SecurityWeek, which viewed the leak site, said all three firms were listed there as not having paid.
JPMorgan said in a post on X that attackers appeared to have reached marketing data kept by some of its vendors, possibly including the names and email addresses of some customers. The bank said it planned to reach out to those affected where appropriate and give them free credit monitoring. It also said the incident had nothing to do with the Chase service disruption earlier in the week, which it blamed on a software bug. Visa told reporters the claims traced back to an incident at an Asia-Pacific service provider and that no card numbers or other payment data were involved. Mastercard said a provider had exposed a limited set of email addresses belonging to a small group of cardholders enrolled in one benefits program, that the exposure was contained, and that its network and card use were unaffected.
Independent reviews of the files give a mixed picture. Reuters counted more than 16,000 customer email addresses in the JPMorgan set, some with phone numbers and postal codes, along with roughly 124 addresses that appeared to belong to bank staff. Hackread counted 16,541 distinct addresses in the JPMorgan files, 7,815 in the Visa material and 3,210 in the Mastercard material, while cautioning that these totals do not equal the number of people affected. The Visa records were mostly from Asia-Pacific markets such as Hong Kong, Taiwan, South Korea, Japan, Singapore and Australia, and the Mastercard files covered marketing data from North America, the Middle East and Africa. Neither outlet could verify that the data was authentic.
Cybernews took a more skeptical view of the Mastercard dump. Its researchers said the file was only about 280 KB with around 2,000 entries, badly formatted, with several people's details merged into single records. Researcher Aras Nazarovas said the material might be test data and that its value to criminals was mostly limited to phishing. He also found matching file structures and formatting across all three datasets, which he said suggested the records came from one shared third party rather than from the financial firms. Booking references in the files pointed to a loyalty or rewards program, Cybernews added.
Little is known about the group itself. Reuters, citing eCrime.ch, said n0n has claimed roughly 200 victims since it appeared in September 2026. Security firm SOCRadar told AFP that the group originates from Russia, though it could not confirm the leak claims. The Wall Street Journal, citing Recorded Future, reported that n0n uses stolen corporate data to extort its targets and enlists other hackers to help it gain network access. Separately, Reuters reported that the OCC, the national bank regulator, had questioned lenders about this week's unrelated outage, and a consultant quoted by Reuters argued that companies should be pressed harder on how much customer data they pass to vendors and whether sharing it is necessary at all.
The incident underscores that marketing and loyalty vendors often hold enough customer contact data to cause real harm, even when no account numbers leave the building. Third-party risk teams at banks, card issuers, insurers and other enterprises should inventory every provider that receives customer lists for campaigns or rewards programs and confirm that each one gets only the fields it truly needs, with retention limits and deletion checks. Auditors can test whether contracts require prompt breach notice, name the data in scope, allow forensic access and set out who pays for credit monitoring and customer outreach. Because several firms may share one supplier, GRC staff should map fourth parties and watch leak site trackers for their own name. Customer communications plans should also warn clients about phishing that cites real benefit programs, since that is the most likely way this data will be used.
Make the description more conciseAdd a defender-focused sectionFormat the IOCs as a table
AllPeoplePeopleFilesFilesMeetingsMeetingsEmailsEmails
The group listed the companies on its leak site on November 16. According to a screenshot captured by the cybercrime tracking platform eCrime.ch and cited by Reuters, n0n claimed to hold JPMorgan cardmember engagement records covering hundreds of thousands of marketing campaign interactions tied to tens of thousands of email addresses. Cybernews reported that the gang also threatened to expose full names, mobile numbers, issuing bank and BIN details, and travel and dining bookings made by premium cardholders. The group set a 48-hour payment deadline, and when it passed, it published the data. SecurityWeek, which viewed the leak site, said all three firms were listed there as not having paid.
JPMorgan said in a post on X that attackers appeared to have reached marketing data kept by some of its vendors, possibly including the names and email addresses of some customers. The bank said it planned to reach out to those affected where appropriate and give them free credit monitoring. It also said the incident had nothing to do with the Chase service disruption earlier in the week, which it blamed on a software bug. Visa told reporters the claims traced back to an incident at an Asia-Pacific service provider and that no card numbers or other payment data were involved. Mastercard said a provider had exposed a limited set of email addresses belonging to a small group of cardholders enrolled in one benefits program, that the exposure was contained, and that its network and card use were unaffected.
Independent reviews of the files give a mixed picture. Reuters counted more than 16,000 customer email addresses in the JPMorgan set, some with phone numbers and postal codes, along with roughly 124 addresses that appeared to belong to bank staff. Hackread counted 16,541 distinct addresses in the JPMorgan files, 7,815 in the Visa material and 3,210 in the Mastercard material, while cautioning that these totals do not equal the number of people affected. The Visa records were mostly from Asia-Pacific markets such as Hong Kong, Taiwan, South Korea, Japan, Singapore and Australia, and the Mastercard files covered marketing data from North America, the Middle East and Africa. Neither outlet could verify that the data was authentic.
Cybernews took a more skeptical view of the Mastercard dump. Its researchers said the file was only about 280 KB with around 2,000 entries, badly formatted, with several people's details merged into single records. Researcher Aras Nazarovas said the material might be test data and that its value to criminals was mostly limited to phishing. He also found matching file structures and formatting across all three datasets, which he said suggested the records came from one shared third party rather than from the financial firms. Booking references in the files pointed to a loyalty or rewards program, Cybernews added.
Little is known about the group itself. Reuters, citing eCrime.ch, said n0n has claimed roughly 200 victims since it appeared in September 2026. Security firm SOCRadar told AFP that the group originates from Russia, though it could not confirm the leak claims. The Wall Street Journal, citing Recorded Future, reported that n0n uses stolen corporate data to extort its targets and enlists other hackers to help it gain network access. Separately, Reuters reported that the OCC, the national bank regulator, had questioned lenders about this week's unrelated outage, and a consultant quoted by Reuters argued that companies should be pressed harder on how much customer data they pass to vendors and whether sharing it is necessary at all.
The incident underscores that marketing and loyalty vendors often hold enough customer contact data to cause real harm, even when no account numbers leave the building. Third-party risk teams at banks, card issuers, insurers and other enterprises should inventory every provider that receives customer lists for campaigns or rewards programs and confirm that each one gets only the fields it truly needs, with retention limits and deletion checks. Auditors can test whether contracts require prompt breach notice, name the data in scope, allow forensic access and set out who pays for credit monitoring and customer outreach. Because several firms may share one supplier, GRC staff should map fourth parties and watch leak site trackers for their own name. Customer communications plans should also warn clients about phishing that cites real benefit programs, since that is the most likely way this data will be used.
Executive IT Forums, Inc.
Educational Programs on Information Technology, Governance, Risk Management, & Compliance (GRC).
Our Newsletter
Get regular updates on CPE programs, news, and more.
Thank you!
Copyright © 2026 Executive IT Forums, Inc. All Rights Reserved.
