# Supply chain attack

> A supply chain attack is a cyber attack in which attackers first compromise a supplier, such as a provider of software or components, in order to reach the actual target through it.

Original page: https://t10.de/en/glossary/supply-chain-attack
Publisher: total10 GmbH, https://t10.de/en/glossary

ENISA's [2021 report on supply chain attacks](https://www.enisa.europa.eu/sites/default/files/publications/ENISA%20Threat%20Landscape%20for%20Supply%20Chain%20Attacks.pdf) describes the attack as a combination of at least two attacks: first on the supplier, then through the supplier on the target, which can be the final customer or another supplier. The report's list of targeted supplier assets includes third-party libraries and packages. In an [information pack on a secure supply chain](https://www.bsi.bund.de/DE/Themen/Regulierte-Wirtschaft/NIS-2-regulierte-Unternehmen/NIS-2-Infopakete/NIS-2-Lieferkette/NIS-2-Lieferkette.html) (in German), the BSI adds that malicious code can be introduced into insecure supply chains already at the development or delivery stage, for example through manipulated updates or compromised components.

In a shop, too, dependencies and plugins can come from third parties. Recital 85 of the [NIS2 Directive](https://data.europa.eu/eli/dir/2022/2555/oj) explains why supply chain risks matter: attacks exploiting vulnerabilities in third-party products and services are prevalent. The [OWASP Top 10:2025](https://owasp.org/Top10/2025/A03_2025-Software_Supply_Chain_Failures/) category "Software Supply Chain Failures" covers breakdowns or compromises in building, distributing or updating software, often caused by vulnerabilities or malicious changes in third-party code. The list recommends obtaining components only from official sources and preferring signed packages.

On a knowledge platform we built for a pharma logistics provider, an automated check compares the packages in use against known vulnerabilities before code leaves a developer's machine. For Shopware 5, for example, we compare the lock file shipped with it against known security advisories. Both checks catch only vulnerabilities that are already known.

## See also

- [SBOM](https://t10.de/en/glossary/sbom): An SBOM (software bill of materials) is a machine-readable record of the components of a software product and of their supply chain relationships.
- [Dependency](https://t10.de/en/glossary/dependency): A dependency is a third-party software package that a project builds on and needs in order to run; packages required by a dependency count as dependencies too.
- [Plugin](https://t10.de/en/glossary/plugin): A plugin is an add-on that extends software such as a shop system with additional features and can be installed separately from it.
- [Repository](https://t10.de/en/glossary/repository): A repository (on GitHub, for example) holds a software project with all its files, its documentation and the revision history of every file.
- [Lock file](https://t10.de/en/glossary/lock-file): A lock file records the exact versions of all packages installed in a project, so that every installation ends up in the same state; with Composer it is composer.lock.

## Where the term appears

- [Knowledge platform for a pharma logistics provider](https://t10.de/en/blog/knowledge-platform-pharma)
- [Non-GxP in pharma: what we build, what we leave out and where our systems stop](https://t10.de/en/blog/non-gxp-pharma-logistics)

## Sources

1. [ENISA Threat Landscape for Supply Chain Attacks (July 2021)](https://www.enisa.europa.eu/sites/default/files/publications/ENISA%20Threat%20Landscape%20for%20Supply%20Chain%20Attacks.pdf), ENISA (Agentur der Europäischen Union für Cybersicherheit), accessed 2026-11-18
2. [Sichere Lieferkette (#nis2know)](https://www.bsi.bund.de/DE/Themen/Regulierte-Wirtschaft/NIS-2-regulierte-Unternehmen/NIS-2-Infopakete/NIS-2-Lieferkette/NIS-2-Lieferkette.html), Bundesamt für Sicherheit in der Informationstechnik (BSI), accessed 2026-11-18
3. [Richtlinie (EU) 2022/2555 (NIS-2-Richtlinie), ABl. L 333 vom 27.12.2022, deutsche Fassung](https://data.europa.eu/eli/dir/2022/2555/oj), Amtsblatt der Europäischen Union, accessed 2026-11-18
4. [OWASP Top 10:2025, A03:2025 Software Supply Chain Failures](https://owasp.org/Top10/2025/A03_2025-Software_Supply_Chain_Failures/), OWASP Foundation, accessed 2026-11-18
