Infoblox, a privately held networking and security company that provides DNS, DHCP and access-management services to large enterprises, has confirmed that attackers reached internal company information through a compromised third-party data migration vendor. A company spokesperson gave the same statement to TechCrunch, The Register and Cyber Daily: Infoblox is "investigating a security event involving unauthorized access to certain company information through a compromised third-party data migration vendor." The Register first reported that the stolen data includes backup snapshots of some customers' NIOS network configurations, along with Social Security numbers, banking details and other personal data belonging to employees and their dependents. Infoblox has not said how many customers or employees were affected, and no regulator filing has been published. The investigation is ongoing.
What Happened
Infoblox confirmed the incident on 16 November. The spokesperson said the company "immediately activated" its incident response procedures, took steps to contain the incident and brought in outside cybersecurity experts "to investigate the facts, understand the scope and address any confirmed risks."
According to two people with knowledge of the incident and a notification Infoblox sent about the breach, TechCrunch reports that the vendor provided SharePoint data migration services. The Register's sources say the vendor had trusted access to Infoblox's SharePoint environment, and that the intruders used the vendor's accounts and access to take data directly from Microsoft SharePoint.
TechCrunch found through public internet records that Infoblox hosts much of its files, email and infrastructure with Microsoft. That includes a SharePoint instance reachable through the company's single sign-on provider.
Infoblox has not named the vendor. One person told TechCrunch that Infoblox has stopped working with it, but the spokesperson did not comment on that. According to TechCrunch, the company also would not say how many customers were affected, whether it yet knows that number, or whether the attackers have contacted it or made demands. No group has claimed responsibility in public reporting so far.
What Was Taken
Infoblox itself has only confirmed access to "certain company information." The more detailed picture comes from reporting:
- Customer NIOS configuration backups. The Register reports that the stolen data included configuration information from some customers' NIOS (Network Identity Operating System) deployments. These are saved snapshots of DNS and DHCP configurations, Grid databases and reporting logs, which can be used to fully restore an appliance or grid after a failure. One person separately told TechCrunch that sensitive customer data was taken. Infoblox has not publicly confirmed what customer data was involved.
- Employee and dependent personal data. The Register has seen an email from CEO Scott Harrell to staff. It says the compromised employee details include direct deposit (banking) information, contact details, dates of birth, and Social Security numbers for both employees and their dependents.
Volume: Not disclosed. SC Media notes that the company declined to give the total number of people affected or details of what scope of data was exposed.
Why It Matters
This is a supply chain breach at a company whose products sit at the core of its customers' networks. NIOS backups are not ordinary documents. They describe how a customer's network is laid out: internal DNS zones and records, DHCP scopes, IP address assignments, and possibly the names and roles of internal hosts. An attacker holding them has a detailed map for reconnaissance, targeted phishing, or later intrusions against those customers. Depending on how each customer configured its grid, the backups may also contain secrets that need rotating.
Infoblox says it has "no indication that any Infoblox products, cloud services, software updates or build-and-release processes were involved." That matters: on current evidence this was theft of stored data, not tampering with the software customers run. But the stolen data's value lies downstream, with the customers it describes.
The employee data is a ready-made kit for identity fraud and payroll redirection. Both The Register and Cyber Daily report that staff were warned to watch for "phishing, vishing, fraud, or other suspicious communications." Affected staff were offered two years of credit monitoring (according to SC Media, citing The Register) and a $100 "spot bonus" to buy a password manager.
The wider lesson is a familiar one. Migration vendors usually get broad, high-privilege access to file repositories for a limited project. That access often outlasts the work and is watched less closely than employee accounts.
The Attack Technique
What is known, based on The Register's sources:
- A third-party SharePoint migration vendor held legitimate, trusted access to Infoblox's Microsoft SharePoint environment.
- Attackers compromised that vendor's accounts.
- Using that access, they took data directly from Infoblox's SharePoint.
How the vendor's credentials were obtained has not been disclosed by Infoblox or by any outlet with sources on the incident. TechRadar points to infostealer malware and credential phishing as the usual routes in cases like this, but that is general context, not a confirmed finding. It is also unclear whether the vendor's access went through Infoblox's single sign-on, a separate service account, or API or app permissions. That distinction matters for anyone trying to find similar exposure in their own environment.
What Organizations Should Do
- Infoblox NIOS customers: treat backups as exposed until told otherwise. Contact Infoblox to confirm whether your grid's backups were involved. If they were, rotate any credentials, TSIG keys, SNMP strings, and integration secrets stored in the grid configuration. Review what internal network layout the backup would reveal.
- Audit third-party access to SharePoint and Microsoft 365. List every vendor account, guest account, service principal and app registration with access to file repositories. Remove anything tied to finished projects and limit what is left to the specific sites a vendor actually needs.
- Make vendor access time-limited and conditional. Give migration and project vendors access that expires, require phishing-resistant MFA, and apply conditional access policies (managed devices, known locations) to their accounts, the same as for staff.
- Monitor for bulk downloads. Alert on unusually large download, sync, or API export activity from SharePoint and OneDrive, especially from third-party identities, outside business hours or from new IP ranges.
- Keep sensitive HR and customer data out of shared file stores. Payroll records, Social Security numbers and customer configuration backups should not sit in a general SharePoint library that a migration vendor can reach. Use separate, access-restricted systems.
- Prepare staff and customers for follow-on fraud. After a breach like this, expect targeted phishing and voice calls that use stolen details to seem legitimate. Verify any request to change payroll deposit details or customer network settings through a separate, known channel.
Sources: Infoblox confirms company and customer data exposed in SharePoint b... | Cyber giant Infoblox confirms security incident after hackers acces... | Infoblox customer and staff data exposed in Sharepoint breach | Hacked! Infoblox discloses third-party data breach, employee data c... | Infoblox Confirms Supply Chain Breach After Attackers Access Sensit... | Infoblox investigates data breach involving third-party vendor bri... | اختراق أمني لشركة Infoblox بعد وصول قراصنة إلى معلومات داخلية | Infoblox data breach via migration vendor · Osegi