Short answer

Infoblox confirmed on 16 November 2026 that attackers reached company information through a compromised third-party data migration vendor with access to its SharePoint. Infoblox says none of its products or cloud services were involved. Reports say employee and some customer data were taken.

If you think your details were included, start with our checklist on what to do after a data breach.

Key facts

Key facts about the Infoblox incident
OrganizationInfoblox
Incident typeSupply-chain compromise
StatusConfirmed by the organization
SectorNetworking and cybersecurity
CountryUnited States
Disclosed2026-11-16
People or records affectedNot disclosed. Infoblox has not said how many customers or employees are affected.

What data was exposed

  • Employee and family member direct deposit details, contact details, dates of birth and Social Security numbers (per a CEO email reported by ITdaily, citing The Register)
  • Configuration snapshots of some customers' NIOS deployments (reported, not confirmed by Infoblox)

What happened

Infoblox is a privately held company that provides DNS, DHCP and identity services to large organizations. On 16 November 2026 TechCrunch reported that it had confirmed a security incident. A company spokesperson said it was “investigating a security event involving unauthorized access to certain company information” through a compromised third-party data migration vendor.

Two people with knowledge of the incident told TechCrunch the vendor does SharePoint data migration, and one said Infoblox has ended its work with it. Infoblox did not comment on that claim and has not named the vendor. ITdaily, citing The Register, reports that the attackers used the vendor’s trusted access to Infoblox’s SharePoint system.

What was taken

Infoblox has not published a list. What is known comes from reports and should be read with that in mind.

For staff, ITdaily reports that an email from chief executive Scott Harrell said the exposed data covers direct deposit details, contact details, dates of birth and Social Security numbers of employees and their family members. ITdaily also reports that affected employees were offered two years of credit monitoring and identity theft protection.

For customers, ITdaily reports that configuration snapshots of some NIOS deployments were taken, including DNS and DHCP configurations, Grid databases and reporting logs. It says it is unclear whether sensitive customer data was stolen. One source told TechCrunch sensitive customer data was taken, and Infoblox has not confirmed what.

What is still unknown

Infoblox did not say how many customers or employees are affected, or whether it knows yet. It did not say whether the hackers contacted it or made demands. No group has claimed responsibility in the coverage we reviewed.

Why a vendor breach matters

Infoblox says its own products were not involved, and nothing in the reports contradicts that. The exposure came through a supplier that was allowed into a file system. That pattern is common: an organization can run strong defences and still lose data held by a partner. See other supplier-side cases such as the Tradier and Etna Software incident and the ConnectWise Cloud Backup attack.

What to do now

If you are an employee or dependent, a Social Security number is the long-term risk, because it cannot be changed easily. Follow our data breach checklist, freeze your credit, and be wary of phishing messages and calls that use your real details. Customers should wait for direct contact from Infoblox and check any message through their support portal. The wider breach tracker lists related incidents.

Scams to watch for after this breach

Criminals use breach news as cover. Expect messages that mention the incident, quote real details, or offer help.

  • Phishing, vishing or fake HR messages aimed at Infoblox employees and their families that quote real Social Security or bank details.
  • Fake 'security update' emails sent to Infoblox customers that claim to come from Infoblox support.
  • Attempts to open credit or file tax returns using stolen Social Security numbers.

What to do if you are affected

  1. 01If you work for Infoblox or are a dependent, use the credit monitoring and identity theft protection your employer offered, and place a fraud alert or credit freeze with the credit bureaus.
  2. 02Check your direct deposit and bank account activity, and tell your bank if you see changes you did not make.
  3. 03If you are an Infoblox customer, treat unexpected emails about the incident as suspect and use the contacts in your support portal.
  4. 04Do not share passwords or codes with callers or emailers who already know personal details.
  5. 05Customers should review who has access to their DNS and DHCP configuration records and rotate secrets stored in them if Infoblox advises it.

Frequently asked questions

What did Infoblox confirm?

A 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. It said it activated incident response procedures and is working with outside cybersecurity experts.

Were Infoblox products affected?

Infoblox says there is no indication that any of its products, cloud services, software updates or build and release processes were involved.

Has Infoblox said what was taken?

Not in its public statement. ITdaily reports that, according to an email from CEO Scott Harrell, employee and family member payroll and identity details were exposed. Reports say configuration snapshots of some customers' NIOS deployments were also taken. A source told TechCrunch that sensitive customer data was taken, but Infoblox has not confirmed what.

Has anyone claimed the attack?

No threat actor had claimed it in the reports we read, and Infoblox did not say whether attackers made contact or demands.

Sources

  1. Cyber giant Infoblox confirms security incident after hackers access 'company information', TechCrunch, 2026-11-16
  2. Infoblox confirms data breach via SharePoint migration vendor, ITdaily, 2026-11-17

This post summarises public reporting as of 2026-11-19. Details of live incidents change; we update posts when the organization or regulators publish new facts. Spot an error? See our editorial and corrections policy.