JPMorgan, Visa and Mastercard report limited data exposure at third parties

src-bc1a6e58

JPMorgan Chase, Visa and Mastercard have each confirmed that customer information was exposed in incidents involving third-party providers. The disclosures point to a recurring vendor-risk challenge: information held outside a company’s own systems can still affect its customers and brand.

JPMorgan said hackers exfiltrated a limited amount of customer data from a third-party site. Based on the bank’s investigation so far, the information included customer names and email addresses associated with marketing data. JPMorgan reported no disruption to its services.

Visa attributed its incident to a third-party service provider in the Asia-Pacific region. The company said its own systems were not compromised and that card account numbers were not involved. Mastercard separately said a third-party provider incident exposed a limited number of email addresses, described as non-payment information, belonging to a small subset of cardholders enrolled in a specific benefit program.

Mastercard said the exposure had been contained and that it was working with affected cardholders to provide support. The company also said the incident did not affect its payment network or customers’ ability to use their cards. The companies’ statements describe different incidents and do not establish that the same provider was involved in each case.

Ransomware claims remain unverified

The disclosures followed claims by a ransomware group calling itself n0n that it had sensitive information belonging to JPMorgan, Visa and Mastercard. Security researchers at Sophos and SOCRadar confirmed that the group had named all three companies as victims. SOCRadar said it had observed posts on the group’s leak site that included sample data, but had not independently confirmed that n0n carried out the attacks.

That distinction matters for incident response and public attribution. A group’s claim, or the posting of sample files, does not by itself establish how data was obtained or whether the claimed victim’s systems were directly breached. Sophos researcher Rafe Pilling said some claims involving major brands should be treated cautiously, noting that data in a number of attacks appeared to originate from third parties running marketing, loyalty or concierge programs.

Researchers also found an internet-accessible file server and reported that n0n had used artificial intelligence to build scanning and reconnaissance scripts. Sophos researchers have associated the group with credential stuffing against FortiGate SSL VPN portals, use of compromised Remote Desktop Protocol and Windows Remote Management credentials, and remote access tools such as MeshCentral to maintain access. These observations describe activity attributed to the group; they do not confirm the method behind the incidents reported by the three financial companies.

Third-party exposure and operational impact

JPMorgan and Visa said their incidents were unrelated to technology disruptions reported earlier in the week. JPMorgan had separately said a software bug in on-premises hardware systems caused issues with customer transactions, while stating that those issues had no connection to cyber risk. Keeping operational incidents distinct from security events helps avoid conflating outages with confirmed data exposure.

For enterprise risk teams, the disclosures underscore the need to understand what customer data vendors hold, where it is processed and how quickly providers can notify clients when an incident occurs. Marketing and benefit-program information may not include payment credentials, but names and email addresses can still create privacy and fraud risks. Organizations should also be able to determine which customer groups are affected, coordinate support, and assess whether vendor access or data-sharing arrangements need to change.

The companies’ statements indicate limited exposure and no reported interruption to payment services, but they do not provide a complete account of the providers’ environments or the incidents’ technical details. Further conclusions about the n0n claims or the scope of the underlying activity would require independent confirmation.