Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A supply chain attack targets an organisation indirectly by compromising a trusted third party, such as a software vendor, open-source library, or managed service provider.

What Is a Supply Chain Attack?
A supply chain attack is one in which an attacker compromises an organisation by first breaching something it trusts: a software vendor, an update mechanism, an open-source package, a cloud service, or a managed service provider. Instead of attacking a well-defended target head-on, the attacker poisons a source the target already relies on, and lets the normal flow of business deliver the compromise.
The appeal is scale. A single successful attack on a widely used supplier can give access to thousands of downstream organisations at once, all of which may have done nothing wrong themselves.
| Year | Incident | What happened |
|---|---|---|
| 2017 | NotPetya | Destructive malware spread through a hijacked update of M.E.Doc, Ukrainian accounting software, causing global damage |
| 2020 | SolarWinds | A trojanised update to the Orion platform reached around 18,000 customers, with a smaller number targeted further by a Russian state group |
| 2021 | Kaseya VSA | The REvil group abused remote management software to deploy ransomware to MSP clients, affecting up to 1,500 businesses |
| 2023 | 3CX | A trojanised desktop phone application was itself the result of an earlier supply chain compromise |
| 2023 | MOVEit Transfer | A vulnerability in file transfer software was exploited by Cl0p, affecting hundreds of organisations, including UK employers through a payroll provider |
| 2024 | XZ Utils | A backdoor planted over two years by a trusted maintainer was discovered just before it reached mainstream Linux distributions |
UK organisations were also targeted by the APT10 “Cloud Hopper” campaign, publicly attributed by the NCSC and allies in 2018, which compromised managed IT service providers to reach their clients.
Supply chain attacks exploit trust that organisations deliberately extend. Signed software updates are supposed to be installed. MSPs are supposed to have administrative access. Developers are supposed to download packages. Malicious code arriving through these channels often bypasses controls designed to stop outsiders, and it may sit undetected for months, as in the SolarWinds case.
No organisation can eliminate supply chain risk, but you can reduce both likelihood and impact:
The NCSC publishes supply chain security guidance built around twelve principles, covering understanding risks, establishing control, checking arrangements, and continuous improvement. The UK government’s Software Security Code of Practice, published in 2025, sets out expectations for software vendors. Regulated sectors face further requirements, including outsourcing and third-party risk rules for financial services, and the EU’s DORA for firms operating in the EU.
At Privia Security, our Red Team Services can include third-party and supplier access scenarios, showing how a compromised partner could be used to reach your critical systems.
Start with an accurate inventory of the suppliers, software versions, and integrations you use, so you can quickly check against published indicators of compromise. Review logs for activity from the affected software or supplier accounts, follow vendor and NCSC advisories, and consider a compromise assessment if the supplier had privileged access to your environment.
Open-source software underpins almost all modern applications and is generally no less secure than commercial code. The risk lies in unmanaged use: unknown dependencies, abandoned projects, and look-alike malicious packages. Using trusted registries, pinning versions, scanning dependencies, generating SBOMs, and reviewing new packages before adoption greatly reduce the risk.
Ask about certifications such as ISO/IEC 27001 or Cyber Essentials, how they protect access to your data and systems, whether they use MFA, how they secure their software development and update processes, how quickly they will notify you of an incident, and how they manage their own suppliers. Tailor the depth of questioning to the supplier’s risk.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.