Infoblox Breach via SharePoint Migration Vendor: What to Do
TL;DR · the short version
Infoblox, the privately held DNS, DHCP and network security company, confirmed on 16 November 2026 that it is investigating "unauthorized access to certain company information through a compromised third-party data migration vendor." It says it activated incident response, contained the incident, brought in outside experts and sent notifications, and that it has "no indication" that its products, cloud services, software updates or build-and-release processes were involved. Infoblox has not named the vendor, said what data was taken, how many people are affected, or when the access happened. Sources told TechCrunch the vendor provides SharePoint data migration services and that sensitive customer data was taken; The Register reports customer NIOS configuration snapshots (DNS and DHCP configuration, Grid databases, reporting logs) and, per a CEO email it saw, employee and dependant data including Social Security numbers and direct deposit details. Those details are not confirmed by Infoblox. For security leaders the lesson is to find and remove the access that migration vendors and consultants keep in Microsoft 365 after a project ends.
Infoblox, the network and DNS security company, confirmed on 16 November 2026 that it is investigating "unauthorized access to certain company information through a compromised third-party data migration vendor." Infoblox says the incident is contained and that it has "no indication" its products, cloud services, software updates or build-and-release processes were involved. It has not named the vendor, said what data was taken or how many people are affected. Sources told TechCrunch and The Register that the vendor did SharePoint migrations and that customer and employee data was taken; Infoblox has not confirmed those details.
Independent analysis. PlayCISO is not affiliated with Infoblox. Facts as reported on 18 November 2026; The Register says it will update its story.
Confirmed vs not yet known
Confirmed by Infoblox (spokesperson statements to TechCrunch and The Register): unauthorized access to "certain company information" through "a compromised third-party data migration vendor"; incident response activated, incident contained, outside cybersecurity experts engaged; notifications sent "and are providing support and guidance as appropriate"; "no indication that any Infoblox products, cloud services, software updates or build-and-release processes were involved."
Reported by sources, not confirmed by Infoblox: the vendor provides SharePoint data migration services and had trusted access to Infoblox's SharePoint (TechCrunch, The Register); the intruders used the vendor's accounts to pull data from SharePoint (The Register); sensitive customer data was taken and Infoblox has ended its work with the vendor (TechCrunch sources); customer NIOS configuration snapshots and employee and dependant data including Social Security numbers were exposed (The Register, partly from a CEO email it saw).
Not yet known: the vendor's name; how the vendor was compromised; when the access started and ended; how many customers and employees are affected; whether any group has claimed it or made demands (Infoblox did not say); any regulator or state attorney general filing (we found none as of 18 November).
What happened
An Infoblox spokesperson told TechCrunch the company is "investigating a security event involving unauthorized access to certain company information through a compromised third-party data migration vendor," and that it "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." The same spokesperson told The Register: "We have sent notifications about this security event and are providing support and guidance as appropriate" and "Our priority is to fully investigate and resolve this issue."
TechCrunch, citing two people with knowledge of the incident and a notification Infoblox sent, reports that the vendor provides SharePoint data migration services. It also notes that public internet records show Infoblox hosts much of its files and email with Microsoft, including a SharePoint server reachable through its single sign-on provider. The Register's sources say the vendor had trusted access to Infoblox's SharePoint and that the intruders used the vendor's accounts to extract data.
What data is reported
- Customer data (The Register): configuration information for some customers' NIOS deployments, which The Register describes as saved snapshots including DNS and DHCP configurations, Grid databases and reporting logs. A TechCrunch source said "sensitive customer data" was taken.
- Employee data (The Register, from a CEO email it saw): direct deposit details, contact information, dates of birth and Social Security numbers for employees and their dependants. Staff were offered a $100 "spot bonus" for a password manager and two years of credit monitoring and identity protection, and were warned to be "especially alert for phishing, vishing, fraud, or other suspicious communications."
Infoblox declined to say what types of data were exposed or how many people are affected. Treat both lists as reported, not confirmed.
Useful next, if this was relevant to you
Timeline
| Date (2026) | Event | Source |
|---|---|---|
| Not disclosed | Vendor compromised; vendor accounts used to reach Infoblox SharePoint | The Register (sources) |
| Not disclosed | Infoblox notifies affected people; CEO emails staff about employee data | Infoblox statement; The Register |
| 16 Nov | Infoblox confirms the incident to TechCrunch; sources say a SharePoint migration vendor was involved | TechCrunch |
| 16 Nov | The Register reports customer NIOS configuration snapshots and employee data exposed | The Register |
| 17 Nov | Follow-up coverage; vendor, counts and dates still undisclosed | Security Affairs |
What security leaders should do this week
If you are an Infoblox customer:
- Ask your account team directly whether your data was in scope, which files (support bundles, configuration backups, Grid database exports) and from what dates. Log the answer. The third-party breach intake lists the questions.
- Assume your network map is known if your snapshots were included: DNS zones, DHCP scopes and internal naming help an attacker plan. Review what is exposed externally and tighten monitoring on the systems those files describe.
- Rotate secrets that may sit in shared files. Depending on configuration, a backup or support bundle can hold keys, shared secrets or account details. If you are unsure what yours contained, rotate DNS signing and update keys, integration credentials and admin passwords that existed when the files were shared.
- Warn your staff about follow-on phishing that uses Infoblox's name or the incident.
For every organisation that has used a migration vendor or consultant in Microsoft 365:
- List the apps. In Microsoft Entra, review enterprise applications and app registrations that hold SharePoint or Microsoft Graph permissions (for example Sites.FullControl.All, Sites.ReadWrite.All, Files.Read.All). Note who consented, when, and when each was last used. Practise spotting risky grants in the OAuth consent lab.
- List the service principals and secrets. Look for client secrets and certificates on those apps, especially long-lived ones created for a project. The non-human identity checklist scores them.
- List the people. Vendor guest accounts, named vendor accounts in your tenant, site collection admin rights and group memberships granted "for the migration".
- Remove what the finished project left behind. Revoke admin consent, delete secrets, disable accounts and remove site admin rights the same day a migration is signed off. Put that step in the statement of work.
- Hunt for bulk reads. Search the unified audit log for large numbers of file downloads or sync events by vendor identities and apps over the last 90 days.
- Limit by default next time. Prefer site-scoped access (Sites.Selected) over tenant-wide permissions, time-box guest access, and require the vendor to use phishing-resistant MFA on accounts that touch your tenant.
- Check the contract. Notice deadlines, the vendor's duty to tell you how it was compromised, help with your own notifications, and deletion of your data at project end. Walk the vendor side with the third-party breach response checklist.
Why it matters
A migration vendor needs broad read access to every site it moves, and that access often outlives the project. That makes it one of the most powerful identities in a Microsoft 365 tenant, and one of the least watched. Infoblox's statement that its products were not involved is reassuring for its customers' networks; the reported loss of configuration snapshots and staff identity data is the part to act on. It is the same pattern as this week's Uber breach through Fireworks AI: a trusted vendor's access used against its customer. For the wider week, see Cyber incidents, 17-18 November 2026: what is confirmed.
FAQ
Was Infoblox hacked?
Infoblox says it is "investigating a security event involving unauthorized access to certain company information through a compromised third-party data migration vendor." It says it has "no indication that any Infoblox products, cloud services, software updates or build-and-release processes were involved." So, per Infoblox, attackers reached company information by way of a vendor, not through its products.
What data was taken in the Infoblox breach?
Infoblox has not said. The Register reports that configuration snapshots of some customers' NIOS deployments were exposed (DNS and DHCP configurations, Grid databases and reporting logs), and that an email from CEO Scott Harrell it saw told staff that employees' direct deposit details, contact information, dates of birth and Social Security numbers, and those of their dependants, were involved. A source told TechCrunch that sensitive customer data was taken. Infoblox declined to confirm the data types.
Which vendor was involved in the Infoblox breach?
No source has named it. TechCrunch, citing two people with knowledge of the incident and a notification Infoblox sent, reports it is a vendor that provides SharePoint data migration services. The Register's sources say the vendor had trusted access to Infoblox's SharePoint and its accounts were used to pull data out. One TechCrunch source said Infoblox has ended its work with the vendor.
Are Infoblox NIOS or BloxOne customers at risk?
Infoblox says there is no indication its products, cloud services, software updates or build pipeline were involved, so this is not reported as a product compromise. The reported risk is data exposure: a NIOS configuration snapshot describes your DNS zones, DHCP scopes and network layout, which helps an attacker plan. Ask your Infoblox account team whether your data was in scope, and treat any secret that was in a file you shared with Infoblox as exposed until they say otherwise.
How many people were affected by the Infoblox breach?
Not disclosed. Infoblox would not tell TechCrunch or The Register how many customers or employees were affected. We found no state attorney general or regulator filing with a count as of 18 November 2026.
How do I check what a SharePoint migration vendor can still access?
In Microsoft Entra, list enterprise applications and app registrations with SharePoint or Graph permissions such as Sites.FullControl.All or Sites.ReadWrite.All, check who consented and when each was last used, and remove the ones tied to finished projects. Then check guest and named vendor accounts, their group and site memberships, and any SharePoint app-only access. Search the unified audit log for bulk file downloads by those identities.
Sources
- TechCrunch: Cyber giant Infoblox confirms security incident after hackers access "company information" (16 Nov 2026): Infoblox spokesperson statement, SharePoint migration vendor, sources
- The Register: Infoblox customer and staff data exposed in SharePoint breach (16 Nov 2026): Infoblox statement, NIOS snapshots, CEO email to staff
- Security Affairs: Infoblox confirms supply chain breach (17 Nov 2026)
Infoblox has not published a statement on its own website that we could find; its words above are as given to TechCrunch and The Register. This article is educational guidance for security leaders, not legal advice.