Technology

Infoblox Confirms Breach Through a Third-Party SharePoint Migration Vendor

Martin HollowayPublished 9m ago3 min readBased on 1 source
Reading level
Infoblox Confirms Breach Through a Third-Party SharePoint Migration Vendor
Photo by panumas nikhomkhai on Pexels

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. These are the standard steps for an event of this kind: scope the access, cut off the path the attackers used, 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. That statement places 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. A migration vendor is a bit like a moving company: to do its job, it needs a copy of the keys to your old house and to your new one. Tools that move content between SharePoint environments usually need broad read access at the source and write access at the destination. That access typically runs through service accounts, app registrations or delegated permissions, which often persist for the length of a project and sometimes longer. Because those credentials and connectors are trusted by default, a compromise of the tooling can expose far more than the data being moved. The attack path here runs through a trust relationship rather than a flaw in the target platform.

For practitioners, the open questions are concrete. Security teams running SharePoint or Microsoft 365 environments with third-party migration partners will want to know which OAuth grants (permissions that let an app act on a user's behalf), enterprise applications and service principals (identities that apps use inside the tenant) those partners hold. They will also want to know whether any remain active after a project closes, and what 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. 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 a 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 most enterprise security programs can reach it.

What is still unknown 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. For now, the confirmed facts are narrow, and they point to a third-party migration path rather than to the company's products or release infrastructure.