Infoblox Vendor Breach: What MSPs Should Check Now
Infoblox confirmed that attackers reached company information through a compromised third-party data migration vendor. Its products and update pipeline were not involved, but the access path is one every MSP should audit in its own tenants.
On 16 November 2026, Infoblox confirmed "unauthorized access to certain company information through a compromised third-party data migration vendor" [1][2]. The company says there is "no indication that any Infoblox products, cloud services, software updates or build-and-release processes were involved" [1]. Nothing in what Infoblox has confirmed requires customers to patch or pull Infoblox appliances. What it does require is a hard look at the outside vendors that hold standing access to your own Microsoft 365 and SharePoint data, and to your clients'.
What Infoblox confirmed
Infoblox's spokesperson gave the same statement to TechCrunch and The Register on 16 November 2026 [1][2]:
- Attackers gained "unauthorized access to certain company information through a compromised third-party data migration vendor."
- Infoblox "immediately activated" its incident response procedures, took steps to contain the incident, and brought in outside cybersecurity experts.
- There is "no indication" that Infoblox products, cloud services, software updates or build-and-release processes were involved.
Infoblox has not named the vendor, has not said how many customers or employees are affected, and has not said what types of data were taken [1][2]. No threat actor has been named. Treat anything beyond the points above as unconfirmed until Infoblox says more.
Why this matters to MSPs
The vendor in this case was a data migration provider. Reporting from both outlets, citing people familiar with the incident, says it provided SharePoint data migration services and held trusted access to Infoblox's SharePoint environment [1][2]. Infoblox has not confirmed those details, but the pattern is familiar: a migration or integration partner is granted broad, standing access for a project, and nobody removes it when the project ends.
MSPs sit in the same position twice. You grant vendors access to your own tenant, and you often hold or broker vendor access into your clients' tenants. A compromised third party with a valid account does not trip a password-spray alert or a malware detection. It looks like normal work, which is why it gets through.
What to do now
- Inventory third-party access in every Microsoft 365 tenant you manage. List guest accounts, enterprise applications and app registrations with SharePoint or Graph permissions, and service accounts created for migrations. Anything tied to a finished project should be removed.
- Review consented permissions, not just accounts. Applications with Sites.Read.All, Sites.FullControl.All or Files.Read.All grant tenant-wide reach. Confirm each one is still needed and owned by someone.
- Look for bulk downloads. Search the unified audit log for large FileDownloaded and FileSyncDownloadedFull volumes from a single account or app over the last 90 days, especially outside business hours.
- Rotate secrets on integrations. Client secrets and certificates for migration and backup tools should be rotated, and expiry dates shortened.
- If you or your clients run Infoblox NIOS or BloxOne, watch for direct notice from Infoblox and act on its guidance. Until it says what customer information was involved, treat any configuration you have shared with Infoblox support as potentially exposed, and review credentials that appear in those files.
- Warn clients about follow-on phishing. Breach news invites lookalike "Infoblox security notice" emails. Tell users to verify any request through a known contact.
Frequently asked questions
What did Infoblox confirm?
Infoblox confirmed unauthorized access to certain company information through a compromised third-party data migration vendor, and said there is no indication its products, cloud services, software updates or build-and-release processes were involved [1][2].
Do I need to patch or replace Infoblox appliances?
Nothing Infoblox has confirmed calls for that. The company says its products and update processes were not involved [1]. Follow any direct notice Infoblox sends to customers.
Was customer data taken?
Infoblox has not said. It declined to give the types or volume of exposed customer data, or the number of customers affected [1][2]. Reports citing unnamed sources say some customer data was involved, but Infoblox has not confirmed this.
Who was the vendor?
Infoblox has not named it. Reporting citing people familiar with the incident describes it as a SharePoint data migration provider [1][2].
What is the lesson for MSPs?
Standing third-party access is an attack path. Migration, backup and integration vendors often keep broad permissions long after a project ends. Audit and remove that access in your own tenant and every client tenant you manage.
How can an MSP detect abuse of a trusted vendor account?
By watching behaviour rather than credentials: bulk downloads, access at unusual hours, new locations, and permission changes by vendor accounts. That needs Microsoft 365 audit data reviewed continuously, not only after a breach is announced.
How Vijilan helps
Vijilan's SOC watches identity and Microsoft 365 activity around the clock, including third-party and service accounts, with machine speed where speed wins and a human approving the actions that carry real risk. If you want that coverage across your own tenant and your clients', ThreatDefend™ runs it on CrowdStrike Falcon with Vijilan's analysts behind it. Talk to us.
Sources
Threat notes, once a week
What our SOC actually saw this week: new attack patterns, the detections we shipped against them, and what it means if you run an MSP. Written by the analysts, not by marketing.
See what 24/7 looks like when the SOC actually acts.
Book a 20-minute platform walkthrough: no slide deck, just the console.
Book a walkthrough →