Your Weakest Vendor Is Your Breach
Visa, Mastercard, JPMorgan, TSMC and Maersk all said their own systems were not breached, and they were probably right. The data still leaked, through vendors, a cloud provider and an inherited legacy system. Here is the pattern and what to do about it.
This week three stories crossed my desk, and they read like the same story told three times. Visa, Mastercard and JPMorgan Chase had customer data leaked, but not from their own systems. TSMC confirmed employee data was out, but it came from a cloud provider. Maersk had data taken from a legacy system that arrived with a company it bought back in 2022.
In every case the company said the same thing: our own systems were not breached. That is probably true. It is also not what customers hear. They see your name in the headline, not your vendor’s.
So here is the uncomfortable point: your attack surface is no longer the network you built. It is every company that holds a copy of your data, and every system you inherited and never quite cleaned up.
The brand in the headline was never the system that was breached
Read each column top to bottom: the company you know, the side door the attacker used, and what came out.
Look at the green boxes first. In all three cases the company’s own statement is that its core systems were fine, and I have no reason to doubt that. Now look at the red boxes. The attacker never needed the core systems, because the data already sat somewhere else: with a service provider, with a cloud host, or in an old system that came along with a company Maersk bought.
This is the part many risk registers miss. We assess vendors when we sign the contract, then rarely look again. Meanwhile they keep copies of our data, and acquired systems keep running outside our normal controls. Every one of those is part of your attack surface, whether it appears on your network diagram or not.
Be honest about what is known, and act before it is
When a breach breaks, the first hours are full of claims. Ransomware groups exaggerate to put pressure on victims, and companies are careful about what they confirm. Both columns below matter, but for different reasons.
Confirmed by the companies
- ✓Visa: an incident at a third-party provider in Asia-Pacific; no card numbers affected.
- ✓Mastercard: limited information on a subset of cardholders in one benefit program.
- ✓JPMorgan: outside providers targeted; marketing data such as names and emails likely accessed.
- ✓TSMC: leaked data matches data held by a cloud service provider.
- ✓Maersk: unauthorised access and data extraction from one inherited legacy system.
Only claimed by the attackers
- ?n0n listing the three payment brands on its leak site with a 48-hour deadline.
- ?6.9GB and about 46,000 TSMC employee records offered for sale.
- ?About 100GB from Maersk and a $5 million demand from WhiteArmor.
- ?That the Maersk system is the old LF Logistics platform bought in 2022.
A leak-site listing is not proof. But by the time a vendor confirms the details, your customers have already read the headline. Your plan has to work on claims, not only on confirmations.
How exposed are you through this supplier?
Pick one vendor you rely on and answer four questions. Nothing leaves your browser.
How the score works: each answer adds points for how much damage a breach at that supplier could do and how little you would know about it. Sensitive data, deep network access, an old review and no notice clause all push the score up. The result lists the specific fixes for your answers, so start at the top and work down.
What I would put on the board on Monday
None of this needs a new tool. Most of it is a list, a contract clause and a one-hour conversation. The left side is what I would get done this week; the right side is what turns it into a habit.
Share less with every vendor
The data a supplier does not hold cannot leak from it. Make data minimisation a contract term.
Finish every acquisition
Bring inherited systems into your identity, logging and patching, or switch them off. “Legacy” is a risk label, not a status.
Tier vendors by blast radius
Review the ones holding sensitive data or network access every year, not just at signing.
Would a vendor breach catch you off guard?
Answer honestly. Each “no” is a place where you would learn about a vendor breach late, or from a journalist instead of from your supplier.
Your customers will not ask whose server it was.
“Our systems were not breached” is a true sentence that protects nobody. The data was yours, the customers were yours, and the headline was yours. Treat your vendors and your inherited systems as part of your own network, because to an attacker they already are.
Sources
- PYMNTS: Visa, Mastercard and JPMorgan customer data leaked
- Decrypt: hackers leak Visa, Mastercard and JPMorgan data
- Sumsub: Visa confirms third-party incident
- CyberDelegate: claims remain unverified
- BleepingComputer: TSMC breach linked to cloud provider
- Cybernews: TSMC confirms data breach
- Computing: Maersk confirms data theft from legacy system
- SupplyChain247: Maersk data theft and LF Logistics claim
- SecureWorld: inherited M&A risk
Facts as reported up to 21 November 2026. Attacker claims are marked as claims.
- Third-Party Risk
- Supply Chain
- Data Breach
- Opinion