mythsthe wider recordMOVEit / Clop2023managed file transfer / supply chain

everyone assumed:

a tool our vendors use isn't our problem

what was actually true:

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.

how it happened

  1. whoClopSQL injection zero-day
  2. the gapvendors' file serversdata from many companies
  3. the resultthousands of organisationsvictims never chose MOVEit
the gap that let it happen the result

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

  1. 27 May 2023Clop exploits a zero-day in MOVEit TransferA file transfer tool inside payroll, benefits and government vendors.
  2. 31 May 2023a patch arrives too lateExploitation has already begun.
  3. breaches travel through vendorsOrganisations are hit through a tool they never installed.the assumption breaks here
  4. 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.

your company
a normal dayYour payroll or benefits provider uses a file-transfer tool you have never heard of.
the gap nobody seesYour staff data passes through that tool, and you have no say in how it is run.a connected app with standing access
  1. in this story
    the 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.
  2. or it goes like this
    howA 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
    it happenedSalesloft / Drift, 2025
  3. or it goes like this
    howIntegration 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
    it happenedGitHub OAuth tokens, 2022

sources

  1. CISA advisory AA23-158A, "CL0P Ransomware Gang Exploits CVE-2023-34362 MOVEit Vulnerability" ,
  2. Cybersecurity Dive, "MOVEit mass exploit timeline" ,
  3. Akamai, "MOVEit SQLi Zero-Day (CVE-2023-34362) Exploited by CL0P Ransomware Group" ,

← all myths

your turn

what you can do about it

  1. 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.

  2. go deeper

  3. 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 →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.