Chase, Visa and Mastercard Vendor Breach: What Customers and Small Businesses Should Know

Chase, Visa and Mastercard Vendor Breach: What Customers and Small Businesses Should Know

This week, JPMorgan Chase, Visa and Mastercard each confirmed that customer information was exposed after a cyberattack on third-party service providers. None of the three says its own systems were breached, and card numbers were not exposed. But for the customers affected, the real risk is just starting: convincing phishing.

What happened

Here’s what has been reported so far:

  • Chase said third parties that provide services to the bank were the target of a cyberattack, and that it will contact affected customers directly where appropriate.
  • Visa said the incident involved a third-party provider in the Asia-Pacific region, that its own systems weren’t involved, and that no payment data such as card numbers was affected.
  • Mastercard said a third-party provider incident exposed a limited number of email addresses and other non-payment information for a small group of cardholders enrolled in a specific benefits programme.
  • A ransomware group called n0n has claimed the attack and on 16 November posted data it says came from the three companies. Reports say it published around 16,000 email addresses and phone numbers.
  • Reports link the attack to Qubole, a data platform provider, and say the attackers used stolen Qubole credentials in October to reach customers’ cloud (AWS) environments. This link has not been officially confirmed.

The exposed details reportedly include names, email addresses and some phone numbers. Some reports mention account IDs. None of the companies has said exactly how many people were affected.

The real risk: targeted phishing

Leaked names, emails and phone numbers are exactly what scammers need to make a fake “bank security” message look real. Expect:

  • Emails saying “Unusual activity on your card” with a link to a fake login page
  • Text messages asking you to “verify” a payment or reply with a code
  • Phone calls from “the fraud team” that already know your name and that you’re a customer, asking for a one-time passcode or to “move money to a safe account”
  • Fake breach notifications with links to “check if you’re affected”

How to protect yourself

  • Don’t click links in unexpected bank or card messages. Open your banking app or type the website address yourself.
  • Call your bank back using the number on the back of your card, not the number in the message.
  • Never share one-time passcodes, PINs or passwords. Your bank will never ask for them.
  • Turn on transaction alerts in your banking app so you see any payment immediately.
  • Use our guide to check if your email has been in a data breach, and change any reused passwords.

For more on recognising these messages, see how to protect yourself from phishing scams.

Lessons for small businesses: your vendors are your risk

This breach follows a familiar pattern in 2026: attackers go after the supplier that holds data for many big companies, rather than the companies themselves. Earlier this month, a newsletter vendor breach exposed millions of SEGA subscribers and customers of hundreds of other brands.

Your business almost certainly shares customer data with suppliers too: your email marketing tool, CRM, accounting software, payroll provider, IT support company and cloud platforms. If one of them is breached, it’s still your customers who get the phishing emails.

What to do

  1. List the vendors that hold customer or employee data. Include free tools and “temporary” exports.
  2. Ask the important ones how they protect it. Do they use MFA on all admin accounts? Do they have a recent security certification such as ISO 27001 or SOC 2? How quickly will they tell you about a breach?
  3. Share only what’s needed. Don’t send a full customer database to a tool that only needs email addresses.
  4. Use separate accounts and MFA for every vendor portal, and remove access for staff and suppliers who no longer need it.
  5. Check how vendors connect to your cloud. In this case, stolen credentials reportedly gave attackers a route into customers’ cloud environments. Review which third parties have access roles or API keys in your Microsoft 365, Google Workspace or AWS accounts, and remove any you don’t recognise.
  6. Have a customer warning ready. If a vendor is breached, a quick, clear message to customers (“we will never ask for your password or OTP”) reduces the harm.

Our guide to third-party vendor security risks goes into more detail.

Quick checklist

For customersFor businesses
Ignore links in “bank security” messagesList vendors that hold customer data
Call back on the number on your cardAsk key vendors about MFA and breach notice
Never share OTPs or passwordsShare only the data each tool needs
Turn on transaction alertsReview third-party access to your cloud accounts
Change reused passwordsPrepare a customer warning template

Sources: statements from JPMorgan Chase, Visa and Mastercard; BleepingComputer and other reporting (16–20 November 2026).