Key takeaways
- Infoblox confirmed a security breach affecting company information through a compromised third-party data migration vendor that accessed the firm's SharePoint systems.
- Sensitive customer data was stolen in the breach, though Infoblox has not disclosed how many customers were affected or what specific information was compromised.
- Infoblox stated that none of its products, cloud services, or software updates were involved in the breach, limiting the incident to company infrastructure.
- The incident highlights risks from third-party vendor access, a persistent challenge in enterprise security where external partners require broad system permissions to operate.
Infoblox, a privately held cybersecurity firm, has confirmed a security incident in which unauthorized actors accessed company information through a compromised third-party data migration vendor. The breach surfaced when the company revealed that attackers had exploited access through a vendor specializing in SharePoint data migration services. Infoblox provides domain name resolution, identity and access management, and other networking security tools to enterprise customers across industries.
How the Breach Occurred
The compromised vendor as entry point
According to Infoblox’s disclosure, attackers obtained unauthorized access to company information through a third-party vendor that provides SharePoint data migration services. TechCrunch reviewed public internet records showing that Infoblox hosts a significant portion of its files, emails and infrastructure with Microsoft, including a SharePoint server that is accessible through Infoblox’s single sign-on provider. SharePoint is a web-based software platform that companies use to share and host internal files and documents. The vendor’s legitimate access to Infoblox’s SharePoint environment created the opening through which attackers reached company systems. Following the discovery of the breach, Infoblox terminated its working relationship with the vendor, according to a person familiar with the incident.
Immediate response and investigation activation
Infoblox stated that upon discovering the unauthorized access, the company immediately activated its incident response procedures and took steps to contain the breach. The company engaged external cybersecurity experts to investigate the incident, understand what information had been accessed, and address confirmed risks. An Infoblox spokesperson provided this statement to TechCrunch: “We immediately activated our incident response procedures, took steps to contain the incident and are working with leading outside cybersecurity experts to investigate the facts, understand the scope and address any confirmed risks.” The investigation remains ongoing as the company works to determine the full scope of the incident.
What Data Was Compromised
Sensitive customer information was taken
TechCrunch learned from two people with knowledge of the incident that sensitive customer data was taken during the breach. However, Infoblox has not publicly disclosed the specific nature of the customer data that was accessed. The company has not stated how many customers were affected by the incident or provided details about which customer accounts experienced data loss. When asked whether Infoblox had been contacted by the attackers or faced any extortion demands, the company did not provide a response. The absence of these specifics suggests either an ongoing investigation or a decision to withhold information during early phases of response.
Company systems and products remained secure
Infoblox made a clear distinction regarding what was not affected by the breach. The company stated that “no Infoblox products, cloud services, software updates or build-and-release processes were involved” in the breach. This distinction carries significance for the company’s customers. The compromise was limited to Infoblox company information and internal infrastructure rather than extending to customer-facing products or the security services that customers rely on Infoblox to provide. This means the security of customers’ own data and their use of Infoblox services was not directly impacted by the incident.
Details Still Under Investigation
The vendor identity remains unnamed
Infoblox has not publicly identified the third-party data migration vendor whose compromise led to the breach. The company declined to comment when asked about the vendor’s name. The specifics of the vendor’s business relationship with Infoblox, the systems access the vendor possessed, and the extent to which the vendor’s compromised systems were exploited have not been disclosed. What information the vendor stored on Infoblox’s SharePoint server and whether the vendor had access to other systems within Infoblox’s environment remain unanswered. These types of details typically emerge as forensic investigations conclude, though some organizations maintain confidentiality agreements that may prevent complete public disclosure.
Scope of compromise remains unquantified
Infoblox has not stated whether it has determined the total number of customers affected by the data access. The company has not disclosed specific categories of customer information that were compromised, such as contact details, account identifiers, payment information, or other data classes. Infoblox also has not provided a timeline for when it expects to complete its investigation and issue additional disclosures with confirmed findings. Standard incident response practices typically involve providing updated information to affected parties as investigations progress and facts are confirmed.
Third-Party Vendor Risk in Enterprise Security
The Infoblox incident illustrates a persistent challenge in enterprise security management: external vendors frequently require extensive system access to perform legitimate business functions, yet that access creates security exposure. Data migration vendors typically need comprehensive permissions across company files, databases and systems to accomplish their work. When vendor systems themselves are compromised or breached, attackers gain access to pre-authenticated pathways into client organizations. This dynamic has increasingly focused the security industry’s attention on vendor risk management and the proper control of third-party system access.
Many enterprises now implement additional security measures around vendor access, including monitoring of vendor activities, time-limited credentials that expire after specific periods, and privileged access management tools that restrict what systems vendors can reach. Despite these practices, the Infoblox breach suggests that comprehensive vendor security remains a complex challenge even for organizations focused on security. Infoblox’s decision to terminate the vendor relationship after the breach was discovered is standard remediation practice, but it comes only after unauthorized access had already occurred and company information had been taken.
Company Disclosure and Investigation Status
Infoblox’s public notification of the security incident and its engagement of external cybersecurity firms indicate a transparent approach to incident management. However, the limited information available about affected customers, the types of data accessed, or the expected investigation timeline suggests that either the investigation is still reaching conclusions or the company has chosen to limit disclosures during the early stages of response. As investigations progress, companies typically provide additional disclosures about confirmed facts and the actions taken to remediate the vulnerability. Infoblox customers and business partners will likely await further announcements as the incident response process continues.
Source: TechCrunch
Frequently Asked Questions
What vendor was compromised in the Infoblox breach?
Infoblox has not publicly named the third-party data migration vendor. The company stated it specializes in SharePoint data migration services and that Infoblox has terminated its relationship with the vendor.
How many customers were affected by the data breach?
Infoblox has not disclosed the number of customers affected or confirmed which customers experienced data loss. The company stated that sensitive customer data was taken but has not provided specifics about the scope.
Were Infoblox's products and services compromised?
No. Infoblox stated that no Infoblox products, cloud services, software updates, or build-and-release processes were involved in the breach. The incident was limited to company information and internal infrastructure.