Mission

Vendor Got Hacked? Your Step-by-Step Response Plan

Vendor Got Hacked? Your Step-by-Step Response Plan

Know what attackers see before they do. See a live Radar report →

If you woke up to a headline that a vendor you rely on just got breached, your first question was probably: does this affect me, and what do I even do right now? Most small businesses don't have a playbook for this moment. You didn't choose to get breached — your vendor did — but you still have to clean it up.

This exact scenario played out recently in an MSP forum thread where an attacker compromised a vendor's storage account and used it to pivot into Microsoft Partner Center integrations across multiple client organizations. Nobody got a warning email before it happened. They found out the same way most businesses do: after the fact, scrambling.

And it's not an isolated case. According to The Hacker News, a flaw in the Web3Auth authentication provider was exploited to steal cryptocurrency from Keplr wallet users — people who had no direct relationship with Web3Auth at all, but who were exposed because an app they trusted depended on it. Separately, The Hacker News reported that a default admin:admin password on a shared identity platform used by multiple automakers allowed researchers to unlock and start cars remotely — a single weak link in one vendor's infrastructure, multiplied across every customer downstream. Even developer tools aren't safe: The Hacker News found that a configuration quirk in Claude Code exposed passwords and API keys in over 1,100 public GitHub repositories, because the tool's permission model made it too easy to leak secrets silently.

Three different vendors, three different failure modes, one common thread: the businesses affected had no warning and no checklist. Here's the one you need.

The Vendor Breach Response Checklist

1. Confirm what the vendor actually had access to

Before you panic, inventory the integration. Did this vendor have API keys, OAuth tokens, service accounts, or admin credentials into your systems? If it touched Microsoft 365, check what permissions were granted — our guide to auditing and revoking M365 OAuth app permissions walks through exactly how to find this.

2. Revoke and rotate immediately — don't wait for vendor confirmation

Don't wait for the vendor's official statement. Rotate API keys, reset shared credentials, and revoke OAuth tokens tied to that vendor the moment you have reasonable suspicion. This is the same lesson from the ConnectWise/SkyKick breach, where delayed app permission reviews cost organizations valuable containment time.

3. Check for lateral movement, not just the direct connection

Attackers who compromise one vendor often use that access to pivot into adjacent systems, exactly as happened with the Partner Center compromise. If the vendor had any service principal or delegated admin role, review it using the same process in our Azure service principal compromise guide.

4. Audit what credentials were ever shared with that vendor

Email threads, shared drives, ticketing systems — go back through your records. If credentials were ever emailed, texted, or pasted into a support chat with this vendor, treat them as compromised. This is the exact risk we detail in accidental credential exposure through third-party integrations.

5. Enable or tighten conditional access and MFA on anything the vendor touched

If the vendor had standing access to an admin account, add conditional access rules limiting where and how that account can be used going forward, even after rotation.

6. Document the timeline for your cyber insurance and clients

Write down when you learned of the breach, what you revoked, and when. This protects you contractually and is often required for insurance claims.

7. Run an independent scan after remediation

Don't take the vendor's word that everything is clean. Run your own external vulnerability scan to confirm no exposed endpoints, leftover tokens, or misconfigurations remain.

The Bigger Lesson: Vet Vendors Before They Breach You

Every one of these incidents traces back to a vendor relationship that was trusted without ongoing verification. Our post on red flags to vet before trusting software updates is worth reading before your next vendor signs on, not after.

Take Action

You can't prevent every vendor from getting breached — but you can make sure you're not the last to know, and not caught flat-footed when it happens. Proactive scanning catches exposed integrations, forgotten API keys, and lingering access before attackers find them for you. Oscar Six Security's Radar scan is $99 and gives you a clear, prioritized view of what's actually exposed across your environment, including third-party connections you may have forgotten about. Check out our solutions and get ahead of the next vendor breach before it becomes your breach. Focus Forward. We've Got Your Six.

Frequently Asked Questions

What should I do first if a vendor I use gets hacked?

Immediately inventory what access, credentials, or API tokens that vendor had into your systems, then revoke or rotate them without waiting for the vendor's official confirmation. Speed matters more than certainty in the first hours after a vendor breach disclosure.

How do I know if a vendor breach actually affects my business?

Check your integration logs, OAuth app permissions, and any shared credentials tied to that vendor's name. If you can't find a clear audit trail, treat the breach as affecting you until you can prove otherwise.

Should I report a vendor breach to my cyber insurance provider?

Yes, document the timeline of when you learned about the breach and what actions you took, since most cyber insurance policies require timely notification and evidence of reasonable remediation steps.

How much does a vulnerability scan cost for a small business?

Oscar Six Security's Radar scan costs $99 and provides a prioritized report of exposed systems, misconfigurations, and lingering third-party access points. It's designed as an affordable option for small businesses that need visibility without an enterprise security budget.

How can I prevent third-party vendor breaches from affecting my business in the future?

Limit vendor access to only what's necessary, review OAuth and API permissions regularly, and run independent vulnerability scans rather than relying solely on vendor assurances. Treat every integration as a potential attack surface, not just a convenience.

Step-by-Step Guide

  1. Confirm vendor access scope

    Identify exactly what credentials, API keys, or permissions the breached vendor had into your systems before taking any other action.

  2. Revoke and rotate credentials

    Immediately revoke OAuth tokens, rotate API keys, and reset any shared passwords tied to the vendor, without waiting for their official statement.

  3. Check for lateral movement

    Review any service principals or delegated admin roles the vendor held to ensure attackers haven't pivoted into adjacent systems.

  4. Audit historical credential sharing

    Search email, chat, and ticketing history for any credentials ever shared directly with the vendor and treat them as compromised.

  5. Tighten access controls

    Apply conditional access rules and MFA to any accounts the vendor touched, even after credentials are rotated.

  6. Document the incident timeline

    Record when you learned of the breach and every remediation step taken, for insurance and client communication purposes.

  7. Run an independent scan

    Verify remediation with your own vulnerability scan rather than relying solely on the vendor's confirmation that the issue is resolved.

Find out what's exposed. Radar scans your external attack surface and shows you exactly what needs fixing. See a sample report →