Infoblox and Barracuda Were Both Breached Through Vendors They Trusted, Turning Third-Party Access Into the Security Industry’s Own Weak Spot

Two companies whose whole business is keeping other organizations safe have disclosed breaches in the same week, and neither attack started inside their own walls. Infoblox, the privately held DNS, networking and security vendor, confirmed on November 16 that hackers reached company and customer information through a compromised third-party data migration vendor. The same day, Barracuda published details of a cloud intrusion that began with an access key it had handed to an outside AI vendor and never took back.

Taken together, the two incidents make an uncomfortable point for every board and IT leader: the access you give contractors, integrators and short-term project partners is now one of the most reliable ways into a company, even a security company.

What happened at Infoblox

According to TechCrunch, an Infoblox spokesperson said the company is investigating “unauthorized access to certain company information through a compromised third-party data migration vendor.” Two people familiar with the incident told TechCrunch the vendor provided SharePoint data migration services, and one said sensitive customer data was taken. Infoblox has not named the vendor, though one source said it has ended the relationship.

The Register, which first reported the breach, said the intruders used the vendor’s accounts and trusted access to pull data straight out of Infoblox’s Microsoft SharePoint environment. The stolen material reportedly includes configuration snapshots from some customers’ NIOS deployments, the backups of DNS and DHCP settings, Grid databases and reporting logs that are used to restore an appliance after a failure or bad upgrade.

Employees were hit too. The Register said an email from CEO Scott Harrell told staff that exposed details include direct deposit information, contact details, dates of birth and Social Security numbers for employees and their dependents. Affected staff received a $100 “spot bonus” to buy a password manager, plus two years of free credit monitoring and identity protection, and were warned to watch for phishing and vishing.

Infoblox says it has “no indication that any Infoblox products, cloud services, software updates or build-and-release processes were involved,” and it declined to say how many customers or employees were affected, according to both outlets and SC Media.

What happened at Barracuda

Barracuda’s own account, summarized by BleepingComputer, is unusually candid. An attacker spent about 44 hours inside roughly 10 of its cloud accounts on November 1 and 2, and the activity was discovered on November 4. The way in was a valid cloud access key Barracuda had issued to an AI company for an earlier project. “We did not retire the key when the vendor — a company working in AI — finished that work. That is on us,” the company wrote.

Barracuda believes the key was stolen from the vendor in October, where it sat in a configuration file in the vendor’s GitHub repository. From there the attacker chained credentials across Barracuda’s data analytics environment, source-code repositories and Kubernetes clusters, went after cryptocurrency secrets such as private keys and seed phrases, and tried to set up persistence through a container that mounted the host file system. An attempt to create a new cloud administrator identity was blocked.

The company said the probing patterns matched ARTEX, an open-source agentic AI penetration-testing framework, and compared the intrusion to a recent incident at cloud host Railway. The attacker reached a system holding customer integration credentials for Barracuda XDR. Barracuda found no evidence those credentials were accessed, but as a precaution it asked potentially affected Managed XDR Cloud and Monitored Endpoint customers to revoke and reissue them, according to its trust center notice.

The common thread: access that outlives its purpose

These were different attacks with different goals, but the root cause rhymes. In both cases, the attackers didn’t have to beat the target’s front-line defenses. They borrowed an identity the target had already decided to trust.

  • Migration and integration vendors get broad, temporary-sounding access. A SharePoint migration project needs read access to large amounts of internal content. That’s exactly what an attacker wants, and it often runs through service accounts that skip the scrutiny applied to employees.
  • “Temporary” credentials are rarely temporary. Barracuda’s key stayed live after the project ended. Unused keys don’t set off alarms, so they sit quietly until someone else finds them.
  • Your security depends on your vendor’s hygiene. A secret committed to a vendor’s GitHub repository became Barracuda’s problem the moment it leaked.
  • AI tooling speeds up the follow-through. Once inside, an automated framework can enumerate systems and chain secrets far faster than a human team, which shrinks the window defenders have to notice.

Why it matters for business leaders

For Infoblox customers, the sensitive part is the NIOS configuration data. Network configuration backups can reveal internal hostnames, IP ranges and service layouts, the kind of map that makes later intrusions or targeted phishing easier. Customers who got a notice should treat it as a reason to review what those snapshots contained and rotate any credentials or keys stored in them.

For everyone else, the lesson is about process more than any one product. Third-party access deserves the same lifecycle discipline as employee access:

  • Keep an inventory of every vendor account, API key and cloud credential, with a named internal owner and an end date.
  • Revoke access automatically when a statement of work closes, and audit for keys that haven’t been used in 30 to 90 days.
  • Scope vendor access to the narrowest data set and time window the job needs, and log and alert on bulk downloads from collaboration platforms like SharePoint.
  • Write contract terms that require vendors to report compromises quickly and keep customer secrets out of code repositories.
  • Assume employee data held in HR and payroll systems is a target, and plan your response, including identity protection and phishing warnings, before you need it.

There’s also a reputational angle. Customers judge security vendors by how they handle their own incidents. Barracuda’s plain admission of fault and its specific guidance to customers set a useful bar, while Infoblox’s investigation is still in its early days, with key questions about scope unanswered.

The bottom line

When two security firms fall to borrowed trust in the same week, the takeaway is clear: your attack surface includes every partner you’ve ever given a key to. Retiring old access, limiting what vendors can reach and watching for unusual data pulls costs far less than explaining a breach to customers and staff.

Don’t let a breach notice turn into missed calls. When customers and partners call with security questions, MAJ.COM Voice AI puts 24/7 AI voice agents on every inbound call and handles outbound sales and support, so your business never misses a lead or leaves a worried customer waiting.

Edited by Coron @QUE.COM
Website: https://QUE.COM Intelligence
Sponsored by: https://MAJ.COM AI Autonomous


Discover more from QUE.com

Subscribe to get the latest posts sent to your email.

Coron @QUE.COM

Editor at QUE.com Intelligence.

coronquecom has 154 posts and counting.See all posts by coronquecom

Leave a Reply

Connect with

Discover more from QUE.com

Subscribe now to keep reading and get access to the full archive.

Continue reading