The common thread in the breaches logged this week is that the victim and the point of failure are seldom the same party. Baker Tilly's clients were exposed through a third-party provider, Maersk through a legacy system inherited with an acquisition, and thousands of GitHub users through accounts that were themselves the entry point. In each case, the organization that suffered the loss was not the one that controlled the vulnerability. That distinction matters for US technology companies, because it means the security posture of a single vendor, subsidiary, or user account now determines the exposure of parties who never chose them directly.
Third Parties Extend the Perimeter
The Baker Tilly Advisory Group is notifying clients that a data breach at a third-party provider compromised certain personal information about them and their dependents, as BleepingComputer reported. The detail that deserves attention is the word dependents. The data at issue is not only the client's own, but the personal information of people who had no relationship with either Baker Tilly or its provider. That is the practical consequence of outsourced processing: exposure propagates outward to individuals who never consented to the arrangement and have no way to audit it. For US companies that rely on advisory, accounting, and processing vendors, the lesson is that due diligence cannot end at the contract. The breach did not originate inside Baker Tilly, yet the notification obligation and the reputational cost land there anyway.
Acquisitions Carry Old Systems and Old Risk
Maersk confirmed a data breach after a threat actor gained unauthorized access to a local legacy system inherited through an earlier acquisition and extracted data from it, as BleepingComputer reported. The accompanying demand of $5 million from the WhiteArmor ransomware group is notable, but the more instructive fact is the vector: a legacy system that came in with an acquisition. Corporate transactions routinely transfer infrastructure that predates current security standards, and integration work tends to prioritize business continuity over hardening. The result is a class of systems that no current employee built, that may sit outside the standard patch cycle, and that are still reachable. For US technology companies that grow by acquisition, every deal adds an inventory problem. A system that was adequate when it was built and is still running years later becomes an attack surface the acquirer inherited without choosing it.
Accounts Are the Credential Supply Chain
A campaign dubbed wfx-loot unfolded on GitHub, where threat actors used 4,837 compromised accounts to probe 61,764 repositories, open pull requests, and push secrets-stealing malware, as BleepingComputer reported. The scale here is the story. Thousands of compromised accounts were enough to touch tens of thousands of repositories, because a single account with commit or review rights can reach everything its permissions allow. The targets were not the account holders alone; they were the projects those accounts could influence. This is the same structural problem as the third-party breach, expressed in code rather than contracts. Access granted for convenience becomes a distribution channel for anyone who takes over the account.

