Cybersecurity and networking company Infoblox has confirmed a security incident in which attackers reached company information through a compromised outside supplier. The Infoblox data breach, first reported on November 16, 2026, is a pointed reminder that even security specialists can be exposed through the vendors they trust. Here is what is confirmed, what remains unknown, and what customers and employees should do now.
What Infoblox Has Confirmed About the Security Incident
According to TechCrunch’s report, an Infoblox spokesperson said the company is investigating unauthorized access to certain company information through a “compromised third-party data migration vendor.” The company says it activated its incident response procedures, moved to contain the incident, and brought in outside cybersecurity experts to establish the scope and address any confirmed risks.
Infoblox also said it has no indication that its products, cloud services, software updates or build-and-release processes were involved. That distinction matters. It suggests the intrusion hit internal file storage rather than the software customers run on their networks. Because the investigation is ongoing, that position could change.
Infoblox is a privately held company that sells DNS, networking and security services to large organizations, which is one reason the incident is drawing wide attention.
How the Attackers Got In: A SharePoint Migration Vendor
TechCrunch reported, citing two people with knowledge of the incident, that the vendor provides SharePoint data migration services. SharePoint is web-based software that companies use to host and share internal files and documents.
Sources also told The Register, as relayed by Cyber Daily, that the vendor had trusted access to Infoblox’s SharePoint system and that the intruders used the vendor’s own accounts to pull data straight out of it. In other words, the attackers did not need to break through Infoblox’s defenses directly. They borrowed a door that had already been opened for a legitimate project.
Neither the vendor nor the attackers have been named, and no threat actor had claimed responsibility at the time of Cyber Daily’s report. One person told TechCrunch that Infoblox has ended its work with the vendor, though the company did not comment on that point.
What Data Was Exposed in the Infoblox Data Breach?
Two groups of people may be affected, and the picture differs for each.
Employee and Dependent Data
In an email seen by The Register, CEO Scott Harrell reportedly told staff that the compromised data included direct deposit details, dates of birth, contact details and Social Security numbers for employees and their dependents. Cyber Daily reports that affected staff were warned to stay alert for phishing, vishing and fraud, and were given a US$100 payment to buy a password manager.
Customer Data
One source told TechCrunch that sensitive customer data was taken. Infoblox would not say how many customers were affected, whether it has been contacted by the hackers, or whether any demands have been made. One secondary news aggregator claims that configuration snapshots and logs belonging to some customers were among the stolen files. Infoblox has not confirmed this, so treat it as unverified until the company says otherwise.
Why Third-Party Vendor Breaches Are So Hard to Stop
Attacks through suppliers are attractive because they exploit trust. A vendor handling a migration project typically needs broad access to internal files for a limited time. If that vendor’s accounts are compromised, an attacker inherits the same reach, often without triggering the alerts that a direct intrusion would.
Data-handling tools and service providers have been repeat targets. The 2023 MOVEit Transfer vulnerability is a well-known example, and Infoblox itself published a knowledge base article on its MOVEit response at the time. The lesson is consistent: an organization’s security is only as strong as the weakest account it has authorized.
Security teams can reduce this risk with a few practical controls:
- Apply least privilege. Give vendors access only to the specific sites, folders or datasets a project requires.
- Time-box access. Set expiry dates on third-party accounts and remove them the day the work ends.
- Require strong authentication. Enforce multi-factor authentication and conditional access for every external account.
- Monitor vendor activity. Alert on bulk downloads, unusual hours and access from unfamiliar locations.
- Tighten contracts. Require prompt breach notification and clear security obligations from suppliers.
What Customers and Employees Should Do Now
Infoblox has said it has sent notifications and is providing support where appropriate. Until the scope is clearer, the following precautions are reasonable.
For Infoblox customers and partners:
- Watch for official notifications and verify any message through contacts you already know, not links in unexpected emails.
- Review what files or configuration data you have shared with Infoblox, and consider rotating any credentials or shared secrets that may have been included.
- Expect phishing attempts that reference Infoblox, and brief your team accordingly.
- Ask your account representative directly about the scope of any exposure.
For affected employees and dependents:
- Consider placing a credit freeze or fraud alert with the credit bureaus in your country.
- Monitor bank accounts, especially direct deposit destinations, for changes you did not make.
- Treat unsolicited calls, texts and emails about your identity or payroll with suspicion.
- US readers can find recovery steps at the Federal Trade Commission’s IdentityTheft.gov. Readers in the UK, Canada and Australia should consult their national fraud and cyber reporting bodies.
What We Still Don’t Know
Several important questions remain open:
- The identity of the compromised vendor and of the attackers
- The number of customers and employees affected
- Exactly which customer data was taken, and whether any of it has been published or used to extort the company
- How long the attackers had access before the incident was detected
Reporting is moving quickly, so details may change as Infoblox and outside investigators share more.
Conclusion
The Infoblox data breach shows how a single compromised supplier can expose a company that sells security for a living. The confirmed facts are limited: unauthorized access through a third-party data migration vendor, an active investigation, and no sign so far that Infoblox’s products or software pipeline were affected. Reports of stolen employee identity data and sensitive customer information raise the stakes. For organizations of every size, the practical takeaway is to audit vendor access now, enforce least privilege, and make sure every external account has an end date.
Word count: about 1,050 words (body only, measured at 1,067 including markdown link syntax).
Internal linking suggestions (Bizora): add links to your own articles on vendor risk management, multi-factor authentication for small businesses, and identity theft protection. I have not inserted URLs because I can’t verify which of these exist.
3. Frequently Asked Questions
What happened in the Infoblox data breach?
Infoblox confirmed that hackers accessed certain company information through a compromised third-party data migration vendor. The company is investigating with outside cybersecurity experts.
Were Infoblox’s products or software hacked?
Not according to the company. Infoblox says it has no indication that its products, cloud services, software updates or build-and-release processes were involved. The investigation is still ongoing.
What data was stolen?
Reports say employee and dependent data was exposed, including Social Security numbers, dates of birth, contact details and direct deposit information. One source told TechCrunch that sensitive customer data was also taken, but Infoblox has not said what or how much.
Who is behind the attack?
Unknown. No threat actor had claimed responsibility at the time of Cyber Daily’s report, and the vendor has not been publicly named.
How can I protect myself if I’m affected?
Watch your accounts for unusual activity, consider a credit freeze or fraud alert, use a password manager with unique passwords, and be cautious with unexpected emails, calls and texts.
4. Sources and External Links
- TechCrunch: “Cyber giant Infoblox confirms security incident after hackers access ‘company information’”: https://techcrunch.com/2026/11/16/cyber-giant-infoblox-confirms-security-incident-after-hackers-access-company-information/
- Cyber Daily: “Hacked! Infoblox discloses third-party data breach, employee data compromised”: https://www.cyberdaily.au/security/14454-hacked-infoblox-discloses-third-party-data-breach-employee-data-compromised
- The Register (cited through Cyber Daily, not independently opened): “Infoblox customer and staff data exposed in SharePoint breach”: https://www.theregister.com/security/2026/11/16/infoblox-customer-and-staff-data-exposed-in-sharepoint-breach/5310280
- Infoblox Community: “MOVEit CVE Response”: https://community.infoblox.com/kb/articles/30408
- Federal Trade Commission: IdentityTheft.gov: https://www.identitytheft.gov/
