Summary
J.P. Morgan Chase has warned that a cyberattack on third-party service providers exposed customers' personal information and marketing data. Mastercard reports a limited exposure, and Visa says its systems were not involved. Chase did not name the vendor, but BleepingComputer reports that the n0n ransomware group claims an attack on Qubole, a cloud data analytics company owned by Idera, which is suspected to be the provider involved.
What the companies say
- Chase: providers were targeted, services were not disrupted, and the incident is unrelated to a service disruption earlier in the week. Its investigation so far shows attackers accessed certain marketing data held by the vendors, which may include customer names and email addresses. Chase has not said how many customers are affected.
- Mastercard: limited email addresses and non-payment information from a small subset of cardholders in a specific benefit program. It says the exposure is contained and its payment network is unaffected.
- Visa: says its systems were not involved and no payment data, such as card numbers, was affected.
- Qubole: did not respond to BleepingComputer's request for comment.
The attacker's claims (unverified)
According to BleepingComputer's reporting:
- October 14 to 26, 2026: attackers allegedly used compromised Qubole credentials to reach customers' AWS environments through IAM roles customers had set up for Qubole.
- November 11: n0n claimed the Qubole attack.
- November 16: n0n leaked the claimed Chase, Visa and Mastercard data on its extortion site.
- n0n claims 53.9 GB across 30,743 files from Qubole itself, including customer contracts, pricing records, staff and trial-user information and production data, and nearly one petabyte overall from customer networks.
- n0n says it contacted Qubole and some affected companies before Sentra and Wiz published reports, and that its demands were ignored.
These figures come from the attackers and have not been verified.
Why it matters
The reported path ran through IAM roles that customers granted to a vendor. A compromised vendor credential then became access inside customer cloud accounts, which is a common third-party risk pattern.
What to do
- Chase customers should expect phishing that uses their name and email, and avoid clicking links in unexpected messages.
- If you use Qubole, review IAM roles trusted by Qubole's AWS account, rotate related credentials, and check CloudTrail for unusual activity between October 14 and 26.
- Scope vendor IAM roles to least privilege and require external IDs and short sessions where supported.
- Inventory which vendors hold marketing or customer data, and confirm how they would notify you of a breach.