Infoblox Confirms Breach Through Compromised Third-Party Migration Vendor

Infoblox has confirmed a cybersecurity incident in which hackers accessed company information through one of its technology vendors. The disclosure, reported by TechCrunch on November 16, 2026, describes unauthorized access to certain company information through a compromised third-party data migration vendor.
The company said it is investigating the security event. It has activated its incident response procedures, taken steps to contain the incident, and is working with outside cybersecurity experts on the investigation. Those steps are the standard sequence for an event of this kind: scope the access, cut the path, and establish what was taken before drawing conclusions about impact.
Infoblox also said it has no indication that any of its products, cloud services, software updates or build-and-release processes were involved in the breach. That statement sets the boundary of the incident at the vendor relationship rather than the company's own software delivery chain, which is the first question most customers and security teams will ask.
According to TechCrunch, citing an Infoblox breach notification and two people with knowledge of the incident, the compromised vendor provided SharePoint data migration services.
The broader context here is the position migration vendors occupy. Tools that move content between SharePoint environments typically require broad read access at the source and write access at the destination, usually through service accounts, app registrations or delegated permissions that persist for the length of a project and sometimes beyond it. A compromise of that tooling can expose far more than the data being moved, because the credentials and connectors are trusted by default. The attack path in this case therefore runs through a trust relationship rather than a vulnerability in the target platform.
For practitioners, the open questions are concrete. Security teams running SharePoint or Microsoft 365 estates with third-party migration partners will want to know which OAuth grants, enterprise applications and service principals those partners hold, whether any remain active after a project closes, and what the audit logs show for bulk downloads or unusual site collection access during the relevant window. Vendor offboarding, least-privilege scoping and time-bound access for migration work are not new controls, but incidents like this one tend to show how often they are skipped in practice.
In my view, the most useful thing an incident of this type can do for the wider industry is push supply-chain review down to the SaaS connector level. Most third-party risk questionnaires still ask about the vendor's own controls and stop short of the credentials the vendor holds inside a customer tenant. Closing that gap is largely a matter of inventory and discipline, and it is within reach of most enterprise security programs.
What remains to be established is the scope: how many organizations and what categories of information are involved, and how the vendor was compromised. Infoblox's investigation with outside experts will determine those answers. Until then, the confirmed facts are narrow, and they point to a third-party migration path rather than to the company's products or release infrastructure.


