BreachesThird-Party Risk

Infoblox Breach: The Migration Vendor Still Had the Keys

November 18, 2026 · Brian Deitch

Infoblox, the DNS and network services company, confirmed that company and customer data was exposed after attackers got into its SharePoint through a compromised third-party data migration vendor. Yesterday it was a forgotten vendor key at Barracuda. Today it's a migration vendor at Infoblox. I'm sensing a theme.

Quick disclosure: I work at Zscaler. Infoblox sells into some of the same security buyers, so read this with that in mind. Everything here comes from public reporting.

What We Know

Per TechRadar, citing The Register:

  • How: a "compromised third-party data migration vendor" had trusted access to Infoblox's SharePoint. Attackers apparently used the vendor's account credentials to get in and pull data. How those credentials were stolen hasn't been said.
  • Employee data: a CEO email to staff, as reported, says employees' and dependents' direct deposit details, contact info, dates of birth and Social Security numbers were exposed.
  • Customer data: some NIOS deployment snapshots, including DNS and DHCP configurations, Grid databases and reporting logs.
  • What Infoblox says wasn't touched: products, cloud services, software updates, and build and release processes. The investigation is ongoing.
  • Response: notifications sent, two years of identity and credit monitoring offered to staff, and a warning to watch for phishing and vishing.

Credit where it's due: Infoblox confirmed it, notified people and said plainly what was and wasn't involved, including that build and release weren't. That's the question every customer asks first.

Why the Customer Data Matters

DNS and DHCP configs are a map. They show internal hostnames, subnets, server roles and naming conventions. That doesn't hand anyone access, but it makes reconnaissance and targeted phishing a lot easier.

The Real Lesson: Migration Access Outlives the Migration

Migrations are temporary. The access granted for them rarely is. A vendor gets broad read access to SharePoint so it can move everything, the project ends, and the account lives on with the same rights, often without MFA tied to your identity provider.

What To Do

If you're an Infoblox NIOS customer:

  • Ask Infoblox whether your snapshots were in scope, and which ones.
  • Assume your internal DNS map is known. Review externally exposed names, and watch for phishing that uses your real internal hostnames.
  • Rotate any credentials or keys that might have been in configs or logs you sent to support.

For everyone:

  • List every vendor with access to your SharePoint, Drive or Box, and what each can read. Remove anything tied to a finished project.
  • Scope vendor access to specific sites and time windows, with your own MFA and conditional access in front of it.
  • Alert on bulk downloads by vendor and service accounts.
  • Keep HR and payroll data out of general collaboration sites.

Bottom Line

Third-party access is still the easiest way in, and it's usually a credential someone forgot to turn off. Go find yours before someone else does.

Sources: TechRadar

infobloxsharepointthird-party-riskvendor-accessdata-breachdnsnioszero-trust
All postsDiscuss on LinkedIn