Infoblox Data Breach: Vendor Hack Exposes NIOS Customer Data
Infoblox data breach: a hacked SharePoint migration vendor let attackers steal NIOS customer network snapshots and staff SSNs. What leaked and what to do now.
Threat card
- Status
- Under investigation
- Threat type
- Supply Chain
- Disclosed
- Nov 16, 2026
- Affected
- Infoblox: some customers' NIOS configuration snapshots (DNS, DHCP, Grid databases, reporting logs) and employee and dependent personal and banking data, via a compromised SharePoint migration vendor
The short version
- Attackers breached a third-party SharePoint migration vendor and used its trusted access to copy files from Infoblox's SharePoint.
- Stolen data includes some customers' NIOS configuration snapshots and employees' bank details, dates of birth and Social Security numbers.
- Infoblox says passwords were not in the NIOS files and its products, cloud services and software updates were not affected.
- No threat actor has claimed the attack and no IOCs have been published.
Last updated: 17 November 2026, 18:10 IST. This is a developing story.
Summary: The Infoblox data breach began at a third-party data migration vendor that had trusted access to Infoblox’s Microsoft SharePoint. Attackers used that access to copy configuration snapshots from some customers’ NIOS deployments, plus personal and banking details of Infoblox employees and their dependents. Infoblox customers should confirm with the vendor whether their NIOS backups were in scope, review the DNS and DHCP data those backups reveal, and watch for targeted phishing.
The Infoblox data breach is a supply chain incident at one of the largest providers of DNS, DHCP and IP address management (DDI) technology. Infoblox confirmed on 16 November 2026 that an unauthorized party accessed certain company information through a compromised third-party data migration vendor. Reporting since then shows the stolen files include customer network configuration backups and sensitive employee records, which makes this more serious than the first statement suggested.
What happened in the Infoblox data breach
According to a statement Infoblox gave to TechCrunch’s report on the Infoblox security incident, the company is investigating unauthorized access to company information through a compromised data migration vendor. Infoblox said it activated incident response, contained the incident and brought in outside cybersecurity experts.
Sources cited by The Register’s investigation into the SharePoint breach say the vendor provided SharePoint migration services and held legitimate access to Infoblox’s Microsoft environment. The attackers used the vendor’s accounts and access to pull data straight out of SharePoint.
Timeline (UTC)
| Date | Event |
|---|---|
| Not disclosed | Attackers compromise a third-party SharePoint data migration vendor working for Infoblox |
| Not disclosed | Vendor accounts are used to exfiltrate files from Infoblox’s SharePoint |
| 16 November 2026 | Infoblox confirms the security event to TechCrunch |
| 16 November 2026 | The Register reports that NIOS customer configuration data and employee records were taken, citing an internal email from CEO Scott Harrell |
| 17 November 2026 | Infoblox says it has sent notifications; investigation continues |
Infoblox has not said when the intrusion began, when it was detected, or how the vendor itself was first compromised.
Who is behind it
No threat actor has been named and no group has publicly claimed the attack at the time of writing. Infoblox has not said whether it received an extortion demand. The vendor has not been identified. Threatspedia will update this post if a claim appears on a leak site or Infoblox attributes the activity.
Technical details
Attack vector
This is a trusted relationship compromise. The migration vendor needed broad read access to Infoblox’s SharePoint to move data, so its accounts became a direct path to internal files once the vendor was breached. No software vulnerability or CVE has been linked to the incident so far.
What a NIOS snapshot contains
NIOS (Network Identity Operating System) is the operating system behind Infoblox’s DDI appliances and Grid deployments. The stolen material reportedly includes saved snapshots of some customers’ NIOS data: DNS and DHCP configurations, Grid databases and reporting logs. Administrators use these backups to fully rebuild an appliance or Grid after a failure or a bad upgrade.
Infoblox and current reporting say the files do not include passwords or login credentials. Even so, a full backup is effectively a map of a customer’s internal network: zone data, internal hostnames, IP ranges, DHCP scopes and how the Grid is built. That is high-value reconnaissance for any follow-on intrusion.
MITRE ATT&CK mapping
| Tactic | Technique (ID) | Observed use |
|---|---|---|
| Initial Access | Trusted Relationship (T1199) | Access through a SharePoint migration vendor with legitimate permissions |
| Initial Access / Persistence | Valid Accounts: Cloud Accounts (T1078.004) | Vendor accounts used inside Infoblox’s Microsoft environment |
| Collection | Data from Information Repositories: SharePoint (T1213.002) | Files pulled directly from SharePoint |
| Exfiltration | Exfiltration Over Web Service (T1567) | Likely, given cloud-to-cloud access; not confirmed |
Indicators of compromise
No IOCs have been published by Infoblox or a credible third party.
Impact
- Customers: NIOS configuration snapshots for some customers, covering DNS, DHCP, Grid databases and reporting logs. The number of customers affected has not been disclosed.
- Employees and dependents: According to the CEO email seen by The Register, bank deposit details, contact information, dates of birth and Social Security numbers. Affected staff are being offered two years of credit monitoring and identity protection for themselves and their families, plus funds for a password manager.
- Products: Infoblox says it has no indication that its products, cloud services, software updates or build-and-release processes were involved.
Infoblox technology sits in the core network of large enterprises, government agencies and service providers, so even configuration-only exposure matters to a wide range of sectors.
What security teams should do now
- Contact your Infoblox account team and ask directly whether any NIOS backup, support bundle or Grid database from your organisation was stored in the affected SharePoint and is in scope.
- If yes, treat your DNS zones, internal hostnames, IP plans and DHCP scopes as known to an adversary. Prioritise hardening of the most sensitive systems those files reveal.
- Rotate any secrets that could live in NIOS configuration or backups even though credentials are reportedly not exposed: TSIG keys, RADIUS and LDAP bind secrets, SNMP community strings, API service accounts and any Grid shared secrets.
- Restrict NIOS Grid Manager and API interfaces to management networks only, and enforce MFA for all administrator logins.
- Raise phishing and vishing alerts for network and DNS administrators. Attackers holding real configuration data can build very convincing lures that pose as Infoblox support.
- Audit your own third parties: list every vendor with read access to SharePoint, OneDrive or Teams, remove access that is no longer needed, and set expiry dates on migration and project accounts.
- In Microsoft 365, hunt for bulk file downloads, unusual FileDownloaded and FileSyncDownloadedFull events in the unified audit log, and guest or vendor accounts accessing large numbers of sites.
What to do now
0 of 6 done
Questions readers ask
What happened in the Infoblox data breach?
Attackers compromised a third-party vendor that was migrating Infoblox's SharePoint data and used the vendor's trusted access to copy internal files, including some customers' NIOS configuration backups and employee personal data.
Was my company's data exposed in the Infoblox breach?
Only some customers' NIOS snapshots are reported to be affected, and Infoblox has not published a number. Infoblox says it has sent notifications, so check with your account team if you have not heard from them.
Were Infoblox products or updates compromised?
Infoblox says its investigation so far shows no sign that its products, cloud services, software updates or build pipelines were involved.
Did the Infoblox hackers steal passwords?
Current reporting says the stolen NIOS files do not contain passwords or login details. Rotating secrets that may sit in configuration is still a sensible precaution.
Sources
One short email when something serious breaks.
Threatspedia covers major cyber threats only, verified against primary sources. Read our editorial policy, or report a correction.


