Vendor breach PR is the communication a company issues when attackers reached its data through a supplier, a third-party service or an inherited system. In November 2026, Infoblox said hackers accessed company information through a compromised data migration vendor, and Maersk said a threat actor extracted data from a legacy system gained in an acquisition. Both statements name the entry point and leave the counts open.
Last updated: November 17, 2026
In this article
What did Infoblox say about its vendor breach?
Infoblox said it is investigating a security event involving unauthorized access to certain company information through a compromised third-party data migration vendor, according to a statement given to TechCrunch on November 16, 2026. The company added that it activated its incident response procedures, took steps to contain the incident and is working with outside cybersecurity experts.
The statement also drew a boundary. Infoblox said it has no indication that its products, cloud services, software updates or build and release processes were involved. For a company whose customers buy security and networking software, that sentence answers the first question a customer will ask.
TechCrunch reported, citing two people with knowledge of the incident, that the vendor provides SharePoint data migration services and that sensitive customer data was taken. Infoblox did not name the vendor, did not say how many customers were affected and did not say whether the hackers had made demands. One of TechCrunch's sources said Infoblox has ended its work with the vendor, a point the company did not comment on.
What did Maersk say about its legacy system breach?
Maersk announced that a threat actor gained unauthorized access to a local legacy system inherited through an earlier acquisition and extracted data from it, according to the BleepingComputer report summarized in the Privacy Guides breach roundup for November 6 to 12, 2026. The shipping group said its investigation is ongoing and that current evidence indicates no sensitive data has been disclosed.
The ransomware group WhiteArmor demanded $5 million, according to the same roundup. The threat actor claims its data includes nearly 30,000 driver records, plaintext passwords, 33 super admin accounts and signed delivery receipts. Those are the criminal group's claims, and Maersk's position is that no sensitive data has been disclosed so far.
Maersk's framing names the type of system, a legacy system from an acquisition, so a reader learns where the weakness sat without a technical briefing.
How do five November 2026 breach statements compare?
Five breach disclosures from the Privacy Guides roundup and TechCrunch show that companies describe the entry point in different levels of detail. Infoblox and Maersk named the type of entry point. SEGA named its provider. Baker Tilly gave the least detail.
| Company | Entry point described | What the company said | What was left open |
| Infoblox | Compromised third-party data migration vendor | Incident response activated; products and build processes not indicated as involved | Vendor name, customer count, any demands |
| Maersk | Local legacy system inherited in an acquisition | Data extracted; evidence indicates no sensitive data disclosed | Final scope while the investigation continues |
| SEGA | Third-party newsletter provider ARARA | 2.2 million email addresses exposed; no names, birth dates, addresses, phone numbers, card details or passwords in the compromised data; SEGA Account addresses unaffected | Details on 92,300 records with additional information |
| Baker Tilly | Third-party provider, breach on September 6, investigation completed October 28 | Clients notified | Provider name, client count, specific data types in the notice |
| Iris Ohyama | Third-party cloud service | About 7.7 million people may be affected; exposed data includes names, addresses, phone numbers, emails, birth dates and passwords described as encrypted | Full scope; the encryption method |
The table shows a pattern. The statements that did the most work for readers said what was not affected, as Infoblox did with its products and SEGA did with its account system. The statement that left the most questions open was Baker Tilly's notice, which named neither the provider nor the specific data types, according to the roundup.
Why are third-party and legacy breaches a distinct PR problem?
Third-party and legacy system breaches create a distinct communications problem because the company owns the customer relationship but not the system that failed. A company cannot fix a vendor's servers, yet customers hold the company responsible for the data it handed over.
Naming the vendor is a real decision with trade-offs. SEGA named ARARA, which tells readers exactly which newsletters were involved and which were not. Infoblox and Baker Tilly did not name their providers, which limits what a reporter can verify but may reflect contract terms or an investigation that is still running. Legal counsel and contract terms often shape that choice, so the communications team should know the answer before an incident, not during one.
Legacy systems raise a separate issue. An inherited system may sit outside the security reviews that cover a company's main infrastructure, and a statement that explains this in one sentence, as Maersk's did, reads as candid. A statement that says only "an older system" with no context reads as an excuse.
What should a third-party breach statement include?
A company's statement should include the type of entry point, what was and was not affected, the actions taken, who is being notified and when the next update will come. The five items below are drawn from the strongest parts of the statements compared above.
- Name the type of entry point, such as a data migration vendor or an inherited system, even if the provider's name stays private.
- State what was not affected, such as products, cloud services or a separate account system, only when the investigation supports the statement.
- List the actions taken, for example activating incident response, containing the incident and bringing in outside experts.
- Say who is being notified, and describe protection offered to affected people when it applies.
- Give a specific time for the next update, because an open investigation will keep producing news.
When a criminal group publishes its own claims, as WhiteArmor did about Maersk, the company's written position should address them directly. Maersk's line that current evidence indicates no sensitive data has been disclosed gives reporters a company statement to set beside the group's list.
Why attribute criminal claims in the story itself?
A ransomware group's list of stolen items is a claim until the company or an independent party confirms it. Attributing the list to the group, as the Privacy Guides summary does for WhiteArmor, keeps a story accurate and protects the publisher if the claim proves overstated.
What should communications teams audit this month?
Communications teams should audit which vendors and inherited systems hold customer or employee data, and confirm that a pre-approved statement exists for each type of breach. The checks below fit in one working session with security and legal:
- List every vendor that handles data migration, newsletters, cloud hosting or customer messages, and note whether the contract allows you to name them publicly.
- List systems gained through acquisitions and record who owns their security review.
- Write one holding statement per scenario: vendor breach, legacy system breach and criminal claim without confirmation.
- Agree on who approves the line about what was not affected, since it can only be used when the evidence supports it.
The crisis communications plan guide covers how to store and approve those statements, and the crisis PR cost guide shows what retainers for this kind of readiness typically include. The crypto hack playbook shows the same first-hour discipline applied to a different kind of breach.
The common thread across Infoblox and Maersk is that both described the how before the how many. Communications teams that prepare that sentence in advance can publish it within hours, while the investigation is still running.