Skip to main content
All incident reports
Incident report

Infoblox confirms breach after intruders reached company files via a migration vendor

Infoblox has confirmed that intruders accessed company information through a compromised third-party data migration vendor. TechCrunch reports the vendor works on SharePoint migrations, and one person with knowledge of the incident says sensitive customer data was taken. This report sets out what Infoblox has confirmed, what it has declined to answer, and what customers and vendor-dependent organisations should do.

· First published

The short version

  • The breach. Infoblox confirmed unauthorised access to certain company information through a compromised third-party data migration vendor. Its spokesperson said the company activated incident response procedures, took containment steps and is investigating with outside experts.
  • The vendor. TechCrunch reports, citing two people with knowledge of the incident, that the vendor provides SharePoint data migration services and that Infoblox sent a notification about the breach. One of those people said sensitive customer data was taken.
  • Product impact. Infoblox says it has no indication that its products, cloud services, software updates or build-and-release processes were involved.
  • Unanswered questions. Infoblox would not say how many customers are affected, whether it has been contacted by the hackers, or whether any demands have been made. It has not named the vendor.

What Infoblox has confirmed

Infoblox, a privately held vendor of networking and security services including domain name resolution and identity and access management, confirmed the incident. A spokesperson described it as an event "involving unauthorized access to certain company information through a compromised third-party data migration vendor" and said the company is investigating the facts and the scope.

The company said it found no indication that its products, cloud services, software updates or build-and-release processes were caught up in the breach. It has not named the vendor. One person with knowledge of the incident told TechCrunch that Infoblox has ended its work with the vendor; the spokesperson did not comment on that.

Who may be affected

According to a notification sent by Infoblox about the breach, the compromised supplier handles SharePoint data migration. SharePoint is web-based software organisations use to store and share internal files and documents. Public internet records reviewed by TechCrunch show Infoblox keeps much of its files, email and infrastructure with Microsoft, including a SharePoint server that TechCrunch confirmed is reachable through Infoblox's single sign-on provider.

One person with knowledge of the incident said sensitive customer data was taken. Infoblox has not confirmed that, has not said how many customers are affected, and would not say whether it is aware at this time. The company also declined to say whether the attackers had contacted it or made demands.

What is not known yet

  • Who carried out the intrusion and whether the compromised migration vendor was targeted deliberately to reach its clients.
  • How many Infoblox customers are affected, and which records or files the intruders obtained.
  • Whether customer data was in fact taken, which TechCrunch's source says but Infoblox has not confirmed.
  • The identity of the data migration vendor, and whether other organisations that used the same vendor are affected.
  • Whether the attackers have made contact or issued any demand.

What to do

If you are an Infoblox customer

  1. Ask Infoblox, through your account team, whether data your organisation shared with the company sat in systems the migration vendor could reach.
  2. Treat material you supplied for migration work as potentially exposed and watch for it appearing in leak forums or extortion messages.
  3. Keep a record of the correspondence and dates, since notification and contractual decisions may depend on them.

If you use third-party migration or IT vendors

  1. Limit each vendor's accounts to the files and systems in the migration scope, and disable them the day the project ends.
  2. Ask the vendor to name any subcontractors that will touch your data and to confirm which of your files it holds or copies.
  3. Log access to your file stores and single sign-on during migration projects and review those logs for accounts you did not expect.

For everyone else

  1. Inventory which outside organisations can reach your file stores through single sign-on and remove accounts that belong to suppliers whose work has finished.
  2. Check that contracts with any supplier holding your data require it to tell you promptly if it is breached.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.