Key facts
- On November 16, Infoblox said hackers reached internal corporate data through a hacked third-party vendor that performs data migration.
- The initial disclosure understated the incident because stolen data covers customer network configuration and sensitive employee records.
- The third-party vendor supplied SharePoint migration services and could access Infoblox's Microsoft environment.
- Stolen files include NIOS deployment configuration data for some customers.
Infoblox said on Nov. 16, 2026, that intruders accessed internal corporate data through a compromised outside vendor that handles data migration. Security Affairs reported that the initial disclosure understated the incident because the stolen data covers customer network configuration and sensitive employee records.
Security Affairs reported that the outside provider handled SharePoint migration and could reach Infoblox’s Microsoft setup. Attackers logged in with the vendor’s credentials and extracted data directly from Microsoft SharePoint. On Nov. 16, 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,” Security Affairs reported. The company confirmed the incident that same day, describing the access as involving an external provider responsible for data migration, and the spokesperson restated that characterization to the outlet.
The stolen material includes NIOS deployment configuration data for certain customers. The saved snapshots hold DNS settings, DHCP settings, Grid databases and reporting logs used to restore an entire appliance or grid after a failure or a faulty upgrade. Security Affairs reported that these snapshots contain operational information that organizations normally restrict to trusted administrators and support staff, and that the stolen customer data gives hackers a clear picture of an affected company’s internal network, system names and configuration, which intruders could use to plan more targeted attacks. The article contrasts the absence of passwords with the operational value of the network snapshots for planning follow-on intrusions against customers.
Infoblox said passwords and login details were not part of the stolen material. Security Affairs reported that the stolen files contained Social Security numbers, birthdates, contact information and bank deposit details, according to an e-mail from Infoblox chief executive Scott Harrell that The Register viewed. The Register reviewed an e-mail from Infoblox chief executive Scott Harrell stating that the stolen material included staff members and their family dependents.
The company has started notifying affected people and is offering support and guidance, Infoblox said. Security Affairs reported that employees received $100 for a password manager and two years of credit monitoring and identity protection for their families. Infoblox told staff to watch for scam e-mails, bogus calls, fraud and suspicious messages.

On Nov. 16, the spokesperson said Infoblox started its incident response procedures, stopped the incident, and brought in leading outside cybersecurity experts to examine the facts, learn the scope, and fix confirmed risks. The statement described the immediate containment steps and the involvement of external investigators after the breach was disclosed. Infoblox said it launched its incident response process, halted the breach, and hired external cybersecurity investigators to review what happened, determine the extent, and address confirmed risks. The company says its investigation shows no sign that products, cloud services, updates or build-and-release processes played a role, and Infoblox has not identified the supplier and has not described how the initial compromise happened.
Customer and employee counts, the stolen data volume and any extortion demands remain undisclosed. Security Affairs said the provider sells DNS, network automation and security services that organizations depend on for critical IT infrastructure. Data migration firms often must manage big amounts of internal information on systems linked to corporate identity platforms. If supplier credentials are breached, attackers may reach beyond the supplier’s own environment.
Security Affairs said organizations should view outside supplier access as part of their own attack surface. Organizations should limit supplier account permissions, track access, remove temporary rights when migration work ends, and review shared information and exported backups for credentials. The piece closes with guidance for other organizations that use external migration providers, framing supplier access as part of the customer’s own attack surface.

Join the discussion