Third-Party Breach Exposes Customer Data for Chase, Visa, and Mastercard

J.P. Morgan Chase, Visa, and Mastercard confirmed a data breach at a third-party service provider in the Asia Pacific region, resulting in the exposure of limited customer information including names and email addresses. The breach, linked to the n0n ransomware group's attack on Qubole, did not affect payment data or disrupt core services. All three companies emphasized that their systems were not compromised and that customer card usage remains unaffected.
In November 2026, a cyberattack on Qubole, a cloud data analytics firm owned by Idera, led to the exposure of customer data linked to J.P. Morgan Chase, Visa, and Mastercard. The breach, attributed to the n0n ransomware group, occurred between October 14 and 26, when attackers exploited compromised Qubole credentials to access AWS environments through pre-configured IAM roles. They allegedly exfiltrated 53.9 GB of data, including customer contracts, pricing records, and user information, and claimed to hold nearly one petabyte from Qubole’s customer networks. On November 16, the n0n group published purported data from Chase, Visa, and Mastercard on its extortion site, including names and email addresses—specifically from a small subset of Mastercard cardholders enrolled in a benefit program. The incident was confirmed by all three companies, which emphasized that their core systems were not breached, payment data remained secure, and services were unaffected. The attack originated in the Asia Pacific region and was linked to Qubole’s role as a third-party service provider. Prior to public disclosure, the group claimed to have contacted Qubole and some affected firms, but demands were reportedly ignored. Qubole has not responded to requests for comment.
The broader context involves increasing reliance on third-party vendors for cloud infrastructure and data analytics, creating expanded attack surfaces. Qubole’s use in managing cloud data for financial institutions highlights how vulnerabilities in one service provider can cascade across multiple high-profile organizations. While no payment data was compromised, the exposure of names and email addresses raises concerns about phishing, social engineering, and reputational damage. The incident follows earlier reports from security firms Sentra and Wiz, which first identified the breach. What remains unclear is the full scope of the data leak, whether additional organizations were affected, and the extent of the n0n group’s access beyond the claimed datasets. Investigations into the breach’s root cause and the effectiveness of vendor risk management protocols are ongoing.
This incident underscores the systemic risks posed by third-party dependencies in critical infrastructure, particularly in finance. While no payment data was compromised, the exposure of names and email addresses could enable targeted phishing campaigns, potentially undermining consumer trust in digital banking and payment systems. The fact that the breach originated through a cloud analytics provider highlights how supply chain vulnerabilities are becoming a primary vector for cyberattacks, especially when access controls are misconfigured. This could prompt financial institutions to reassess their vendor risk assessments and demand stricter security standards from partners. A comparable case is the 2020 SolarWinds breach, where a compromised software update led to widespread infiltration across government and private sectors—though in this instance, the impact was more direct and systemic. The current situation may lead to increased regulatory scrutiny of third-party cybersecurity practices, particularly in the financial sector. Moving forward, organizations may prioritize real-time monitoring of vendor access and adopt zero-trust frameworks. The broader market may see a shift toward more transparent vendor security disclosures, though the long-term impact on consumer behavior remains uncertain.