how it happened
- whoClopSQL injection zero-day
- the gapvendors' file serversdata from many companies
- the resultthousands of organisationsvictims never chose MOVEit
what everyone assumed
An organization picks its vendors carefully, and trusts that those vendors have picked theirs. The boundary of responsibility feels obvious: you secure what you run, your suppliers secure what they run, and a file-transfer product four steps down the chain is somebody else’s audit. It is a reasonable place to draw the line, because the alternative, knowing every tool your vendors’ vendors use, sounds impossible.
what happened
On May 27, 2023, the Clop ransomware group began exploiting a previously unknown SQL injection flaw, later catalogued as CVE-2023-34362, in Progress Software’s MOVEit Transfer. MOVEit is the kind of product most affected organizations never bought directly; it sat inside payroll providers, benefits administrators, government agencies, and other vendors who used it to move data. Progress released a patch on May 31, but exploitation had already begun, and the access propagated the way file transfers do: through the relationships between companies. A breach of one MOVEit instance was a breach of everyone whose data passed through it, and many of those people had no contractual relationship with the company that ran the server.
step by step
- 27 May 2023Clop exploits a zero-day in MOVEit TransferA file transfer tool inside payroll, benefits and government vendors.
- 31 May 2023a patch arrives too lateExploitation has already begun.
- breaches travel through vendorsOrganisations are hit through a tool they never installed.the assumption breaks here
- second half of 20232,000 plus organisations, 60 million plus peopleDisclosed one letter at a time.
how it surfaced
The scale arrived in waves through the second half of 2023 as victim after victim disclosed. CISA and the FBI issued an advisory on the campaign. By the counts that settled later, the cascade reached more than two thousand organizations and the records of over sixty million individuals, most of them people who had never heard of MOVEit and a good number reached through a vendor of a vendor. The assumption retired itself one disclosure letter at a time, each from an organization explaining a breach of a tool it had never installed.
Your attack surface is not the list of tools you run; it is the list of tools that touch your data, including the ones three companies removed from you.
A vendor’s flaw becomes your incident the moment your records pass through it.
picture it at a company like yours
The company here is made up. The other two paths are not: they happened, and each links to the story.
- in this storythe day it mattersAttackers break into the tool and copy everything that passed through it.what it costs youYou are writing breach letters to employees about a system you never installed.
- or it goes like thisit happenedSalesloft / Drift, 2025howA chat tool's key into your CRM is stolen from the vendor.what leavessupport tickets, including passwords pasted into themwho ends up with itan extortion group working through hundreds of companies
- or it goes like thisit happenedGitHub OAuth tokens, 2022howIntegration keys to your code host are stolen from the integration vendor.what leavesyour private code and the secrets inside itwho ends up with itattackers looking for the next door
sources
your turn
what you can do about it
this week
Ask your top handful of suppliers what they use to transfer your data and how they would tell you if it were compromised.
You can name your direct vendors, which is why the question feels answered. The quiet-months question goes one layer down: which of those vendors moves your sensitive data with a tool you have never been told the name of. The MOVEit victims who learned fastest were the ones who already had that line of sight before May 27.
go deeper
if you're not sure where to start
Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.
open the checklist →
