The Infoblox SharePoint breach exposed sensitive company information after attackers compromised a third-party data migration provider. The intruders reportedly used the provider’s trusted access to extract customer configuration material and employee data from Infoblox’s Microsoft SharePoint environment.
Infoblox has contained the incident and engaged external cybersecurity specialists. The networking and security company says there is no indication that its products, cloud services, software updates, or development and release systems were involved.
How the Infoblox SharePoint breach happened
Infoblox confirmed that it is investigating unauthorised access to certain company information through a compromised third party. That organisation provided SharePoint data migration services and had legitimate access to Infoblox’s environment for its work.
According to the initial report, attackers took control of the vendor’s accounts or access and used that established trust to reach information stored in Microsoft SharePoint. This was therefore an intrusion through a supplier relationship, rather than the exploitation of a disclosed vulnerability in an Infoblox product.
Infoblox’s SharePoint service is accessible through its single sign-on provider. However, the company has not explained how the migration provider was initially compromised, whether multifactor authentication was enabled, or what permissions were attached to the affected identities.
No proof-of-concept code or exploit tooling applies to the case because no product vulnerability has been identified. The confirmed exploitation activity consists of attackers abusing authenticated third-party access to enter the SharePoint environment and exfiltrate information.
What the attackers reportedly accessed
The stolen customer information reportedly includes configuration snapshots from some deployments of Infoblox NIOS, or Network Identity Operating System. These backups can hold operational information used to restore appliances or an Infoblox Grid after a failure or unsuccessful upgrade.
Depending on how a backup was created and stored, relevant material can include DNS and DHCP configurations, Grid database content, and reporting logs. DNS controls how systems find online and internal services, while DHCP assigns network settings to connected devices. Grid information can also describe how Infoblox appliances are organised and managed.
This means the reported exposure concerns more than ordinary business documents. Configuration archives may reveal details about an organisation’s network structure, naming conventions, address ranges, services, and administrative arrangements. Infoblox has not disclosed which customers were affected, which snapshot types were taken, or whether every reported archive contained the same categories of information.
The incident also involved internal employee data. An email reportedly sent by Infoblox chief executive Scott Harrell said exposed information included direct deposit banking details, contact information, dates of birth, and Social Security numbers relating to employees and their dependants.
These detailed data categories currently come from the initial reporting rather than a comprehensive public incident notice from Infoblox. The company has not publicly confirmed the number of employees, dependants, or customer organisations affected.
Infoblox SharePoint breach timeline and status
The Infoblox SharePoint breach became public late on 16 November 2026. The first report was published at 21:53 UTC and described the use of a migration vendor’s trusted access to remove data from SharePoint.
At 22:12 UTC on 16 November, separate reporting published Infoblox’s on-the-record confirmation. The company said it had activated its incident response processes, contained the event, and brought in external cybersecurity experts to support the investigation.
Further coverage appeared on 17 November, but it did not add official information about the scale, technical cause, or attacker. As of that date, several important elements remained unknown:
- The identity of the compromised migration provider.
- The date of the vendor’s initial compromise and the attackers’ dwell time.
- When Infoblox discovered the unauthorised activity.
- The number of affected customers, employees, and dependants.
- The volume of information viewed or exfiltrated.
- Whether the attackers contacted Infoblox or issued demands.
No threat actor has been named, and there is no public attribution to a criminal group or state-linked operation. Infoblox has also declined to say whether it received a ransom demand or other communication from those responsible.
No indicators of compromise had been released by 17 November. Customers and defenders therefore do not have incident-specific IP addresses, domains, file hashes, or other technical indicators against which to search their systems.
Which Infoblox products and versions are affected?
Infoblox says it has no indication that any of its products or cloud services were compromised. It also reports no evidence that software updates, build systems, or release processes were affected by the intrusion.
No vulnerable NIOS version has been identified, and the company has not associated the incident with a particular appliance, platform, or configuration. The NIOS material was reportedly data stored in SharePoint, not evidence that attackers breached customers through a flaw in NIOS itself.
This distinction is important when assessing the Infoblox SharePoint breach. The affected technology environment was Infoblox’s company information store and a supplier’s access path into it. Organisations should not interpret the report as evidence of a malicious Infoblox update or a direct compromise of deployed appliances.
However, customers whose configuration snapshots were present in the affected SharePoint environment may face a separate information exposure risk. Infoblox has reportedly notified affected customers, but it has not published the selection criteria, the specific backup contents involved, or the relevant storage period.
Support offered to affected employees
Infoblox reportedly advised employees to remain alert for phishing, voice phishing, and financial fraud. The company also offered employees and dependants two years of credit monitoring and identity protection.
A reported internal measure included a $100 stipend for password management services. These actions reflect the sensitivity of the employee information described, particularly identity details and direct deposit data that could support convincing impersonation or fraud attempts.
Why the Infoblox SharePoint breach matters
The incident demonstrates how legitimate supplier access can become an attack route into a well-defended organisation. A migration provider may need broad, temporary visibility to move data, but those permissions can expose large document collections if the provider’s identity or systems are compromised.
It also shows the risks of keeping sensitive network backups in collaboration platforms. SharePoint is designed to make information available to authorised users, yet configuration archives can provide attackers with valuable context for targeted phishing, impersonation, or later intrusion attempts.
What organisations should do now
Infoblox customers should review any notification received from the company and establish which backups or snapshots may have been shared for migration. They should watch for unusually informed phishing or support requests that refer to genuine DNS, DHCP, Grid, or network details.
Organisations using Microsoft 365 should also identify external and supplier identities with SharePoint access. Immediate checks should focus on whether those permissions remain necessary, whether they are limited to specific sites and folders, and whether migration accounts were disabled after projects ended.
- Review sign-in and SharePoint audit logs for unusual supplier activity.
- Revoke dormant migration accounts, sessions, and access tokens.
- Segregate configuration backups from general collaboration libraries.
- Rotate exposed credentials or secrets if backups may contain them.
- Confirm that third-party access is time limited and independently monitored.
Because Infoblox has not released technical indicators, organisations should base their response on data exposure and access records rather than searching for a named malware strain. Any further customer action should be guided by Infoblox’s direct notifications and the findings of its continuing investigation.
Originally reported by theregister.com.







