TUESDAY, NOVEMBER 17, 2026 Tech news, minus the noise.
N News Cast
LATEST
Cybersecurity

The Infoblox Supply Chain Breach Started With a Vendor, Not a Hacker

Infoblox confirmed on November 16 that attackers reached company data through a compromised third-party migration vendor, taking customer network configuration snapshots and sensitive employee records.

The Infoblox Supply Chain Breach Started With a Vendor, Not a Hacker
Source: Federal Bureau of Investigation, public domain, via Wikimedia Commons

Infoblox supply chain breach started with a trusted vendor

The Infoblox supply chain breach was confirmed on November 16, and it is a textbook case of the risk nobody budgets for. Attackers reached internal company information through a compromised third-party provider that handled data migration work. Infoblox told TechCrunch it is investigating a security event involving unauthorized access to certain company information through that vendor, and reporting from The Register says the supplier was handling SharePoint migration.

Infoblox has not named the supplier or explained how its systems were first compromised. That gap matters. The vendor had legitimate access to Infoblox's Microsoft environment, which is exactly why the attack worked. The attackers did not need to break into Infoblox. They walked in through a door Infoblox had opened on purpose.

What the attackers took

The stolen material is worse than a list of email addresses. According to reporting based on an internal email from CEO Scott Harrell, the exposed employee information includes direct deposit details, contact information, dates of birth, and Social Security numbers for employees and their dependents. That is identity-theft starter kit material, and it covers families, not just staff.

The customer side is arguably more damaging. The stolen files reportedly include snapshots from customer deployments of NIOS, Infoblox's Network Identity Operating System, the platform that manages core network services like DNS and DHCP. Those snapshots map a customer's internal network: system names, configurations, and setup details. The data does not include passwords or login details, but it gives an attacker a clear map of where to look next.

What was not touched, so far

Infoblox has been careful about the limits of the incident. The company says it has no indication that any of its products, cloud services, software updates, or build-and-release processes were involved. That distinction matters to customers, because a compromise of the software supply chain would be a far bigger problem than a compromise of a migration vendor's access.

Even so, the company has not disclosed how many customers or employees were affected, the full volume of stolen information, or whether the attackers made any demands. The investigation is ongoing, and the honest answer is that the full picture is not public yet.

The third-party pattern keeps repeating

This is not an unusual story anymore, and that is the problem. The Maileva breach earlier this month exposed 22 million French residents through a mail platform flaw. The N-able N-central zero-days are being exploited right now through remote management tooling. Verizon's 2026 Data Breach Investigations Report found a third party involved in 48 percent of breaches, up from 30 percent the year before. Huntress found abuse of remote monitoring tools up 277 percent in 2025.

The pattern is consistent: the target hardens its own perimeter, and the attacker goes around it through a vendor, a migration project, or a management tool. The Infoblox case adds a detail worth remembering. The vendor was doing SharePoint migration, which is routine, boring, and exactly the kind of project that gets broad access without much scrutiny.

What to do if you are an Infoblox customer

Start with access. Audit every third-party account with access to your environment, especially vendors on temporary projects, and revoke anything that is no longer needed. Rotate credentials that any vendor could have touched, and review your NIOS deployment configurations against the snapshots that may have been taken.

Then look at your own vendors the same way. Ask which of them hold standing access to your systems, what data they can reach, and when that access was last reviewed. The 3-2-1 backup rule still applies, because a network map in attacker hands is a precursor to ransomware, not just a privacy incident. The lesson of this breach is not that vendors are untrustworthy. It is that trusted access needs the same monitoring as untrusted access, and usually gets less.

AS
News Cast Editorial Team

We cover AI, gadgets, startups and security — original reporting and explainers, written by humans, for humans. Got a tip? Reach us via the contact page.