Skip to content
Rush Commerce
Software & Dev2 min read

Infoblox data breach came through a data migration vendor

Infoblox confirmed hackers reached company information through a compromised data migration vendor. Products weren't hit. Revoke migration access when the job ends.

Infoblox, a DNS and network security company, confirmed on November 16 that hackers accessed "company information" through a compromised third-party data migration vendor. It says its products and cloud services were not involved. The Infoblox data breach is the second vendor-access story we've covered in a week, after Expedia. The pattern is the lesson: the contractor who moved your files often still has the keys.

What actually happened

Per TechCrunch:

  • The confirmation. An Infoblox spokesperson said the company is investigating unauthorized access to certain company information through a compromised data migration vendor. It started incident response, contained the incident and brought in outside experts.
  • The vendor. Infoblox hasn't named it. Two people with knowledge of the incident told TechCrunch it provides SharePoint data migration services. One said Infoblox has ended work with the vendor.
  • Customer data. Infoblox says "company information." One unnamed source told TechCrunch sensitive customer data was taken. Infoblox has not confirmed that, and would not say how many customers are affected.
  • Products. Infoblox says it has no indication that its products, cloud services, software updates or build-and-release processes were involved.
  • Unknowns. No group has claimed the attack. Infoblox did not say whether anyone made demands.

Why vendor access matters for your business

A migration vendor gets the widest access you will ever hand out. To move a file share into SharePoint or Google Drive, they need read access to everything, usually through an admin-consented app or a service account. The project ends in a month. The grant doesn't.

Small businesses do migrations all the time: new email host, new drive, new store platform, new CRM. Every one leaves something behind. Check for these:

  • App consents. In Microsoft 365, open Entra ID → Enterprise applications and sort by last sign-in. In Google Workspace, check Security → API controls. Remove anything from a finished project.
  • Service accounts and guest users. Disable migration accounts the day the cutover is signed off.
  • Shared admin passwords. If a contractor ever had one, rotate it.
  • Contracts. Write offboarding into the statement of work: vendor removes its access, you confirm it in writing.

None of this needs a security budget. It needs a calendar reminder on the last day of the project.

Key takeaways

  • Infoblox confirmed hackers reached company information through a compromised data migration vendor
  • Sources told TechCrunch the vendor does SharePoint migrations; Infoblox hasn't named it
  • Infoblox says products, cloud services and build processes were not involved
  • A customer-data claim comes from one unnamed source and is unconfirmed
  • Revoke migration app consents, service accounts and shared passwords the day a project ends

Every migration should end with an access teardown. When we move a business onto a new stack, removing our own access is a line item, not an afterthought. See how we run migrations, or ask us to audit who still has keys to yours.

Sources: TechCrunch.

  • #data-breach
  • #vendor-risk
  • #sharepoint
  • #infoblox
  • #access-control
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.