NEWS

Infoblox confirms breach after hackers access company data via third-party vendor

Infoblox confirms breach after hackers access company data via third-party vendor
Image: Redação iMasters
News
Reading
5 min
In short

Infoblox, one of the world's largest providers of DNS, DHCP and identity management, confirmed that attackers accessed company information through a compromised data migration services provider.

Infoblox, one of the world's largest providers of DNS, DHCP, and identity and access management services (the so-called DDI category), confirmed a security incident on November 16, 2026. According to TechCrunch's report, hackers accessed "company information" through a compromised third-party vendor.

The company is privately held but substantial in size: it provides large corporations with the infrastructure that resolves domain names, distributes IP addresses, and controls who accesses what within the corporate network. It's the kind of tool that stays invisible in everyday operations until it stops working, or until it becomes an entry point for a larger attack.

The attack vector: a SharePoint migration vendor

In a statement to TechCrunch, Infoblox said it was "investigating a security event involving unauthorized access to certain company information through a compromised third-party data migration vendor." The company did not publicly name this vendor.

TechCrunch learned, based on a breach notification sent by Infoblox itself and from two people with knowledge of the incident, that the compromised vendor provides data migration services for SharePoint, Microsoft's internal file-sharing and hosting platform. One of the sources said sensitive customer data was extracted in the attack.

According to public internet records analyzed by TechCrunch, Infoblox hosts much of its files, email and infrastructure with Microsoft, including a SharePoint server that the report confirmed is accessible through the company's single sign-on (SSO) provider. In other words: the entry point was not an Infoblox product, but rather the weakest link in the chain, an external provider with access to internal data.

What the company says, and what it doesn't

Infoblox's spokesperson detailed the measures taken after the incident was discovered:

We immediately activated our incident response procedures, took steps to contain the incident and are working with leading outside cybersecurity experts to investigate the facts, understand the scope and address any confirmed risks.

Infoblox spokesperson, in a statement to TechCrunch

The company also stated it had "no indication that Infoblox products, cloud services, software updates or build-and-release processes were involved" in the attack, an important distinction: the issue would be confined to internal corporate data, not the development pipeline or the products customers run in production.

But the list of what Infoblox did not disclose is long:

  • It did not name the compromised vendor, although a source said the company has already ended its business relationship with it.
  • It did not disclose how many customers were affected, or whether it has already mapped that scope.
  • It did not confirm nor deny whether the attackers made contact with demands.
  • It did not detail what type of customer data may have been taken, beyond one source's indication that sensitive information was involved.

Why this matters for those who run DNS and DHCP

Companies like Infoblox occupy a sensitive place in network architecture: whoever controls DNS and DHCP effectively controls where an entire organization's traffic is routed. An incident that begins as a leak of corporate data (contracts, emails, internal documents) is concerning on its own, but takes on another dimension when the affected company is a critical infrastructure provider for third parties.

Infoblox was clear in saying there is no indication that products or the build-and-release process were compromised. That's the difference between an administrative incident (a leak of business data) and a software supply chain attack, the most feared scenario since cases like SolarWinds. As far as the disclosed information shows, this is not the latter scenario. But the company also did not offer any guarantees about customer data, which leaves the question open until the investigation advances.

The attack did not exploit a vulnerability in Infoblox software, nor directly in its cloud infrastructure. It exploited a vendor contracted specifically to migrate data within SharePoint, with authenticated access via the same corporate SSO used by the company's employees. This is the classic pattern of a supply chain attack: instead of attacking the final target, which likely has more mature defenses, the attacker targets the smaller service provider, with privileged access and weaker defenses.

For infrastructure and security teams in Brazil evaluating or already using DDI tools (DNS, DHCP and IPAM), the case reinforces practical governance points:

  1. Map which third-party vendors have access to internal systems via SSO, and review that access periodically, not just at the time of contracting.
  2. Separate, whenever possible, the access of data migration or maintenance vendors from access to production environments or build pipelines.
  3. Contractually require data vendors to report security incidents within a short window, and verify whether this is actually being followed in practice.
  4. Treat customer data stored on platforms like SharePoint with the same segmentation rigor applied to production databases.

What's still unknown

As of the publication of the original report, Infoblox had not publicly confirmed how many customers were impacted, the exact nature of the sensitive data mentioned by one of the sources, or the name of the SharePoint migration vendor that served as the entry point. The company also did not respond to whether the attackers made contact with demands, a detail that typically indicates whether the incident involves extortion or merely silent data exfiltration.

Until these points are clarified, teams using Infoblox products would do well to follow the company's official communications and, independently, review their own third-party access controls, since the central lesson of the case does not depend on the name of the compromised vendor: it's about the risk embedded in any external integration with access to corporate data.

Translated from the Brazilian Portuguese original · Read the original