Supply-chain compromise provides threat actors with trusted access to multiple downstream organisations. Empirical research in 2026 shows that 34 out of 42 analysed supply-chain intrusions reached downstream victims directly through third-party infrastructure. Concurrently, the UK Cyber Security Breaches Survey 2025/26 found that 43% of UK businesses experienced a breach or attack in the previous 12 months, and 69% of large commercial organisations suffered a breach or attack over the preceding twelve months. Despite these operational realities, many mid-market organisations still skip thorough cyber security risk assessments across their vendor ecosystems, treating supplier oversight as a static compliance exercise rather than an active, unmonitored attack corridor capable of compromising operational continuity and sensitive corporate credentials at scale.
View the data behind this chart
| March | April | May | June | July | |
|---|---|---|---|---|---|
| Tracked Attacks | 13 attacks | 9 attacks | 9 attacks | 10 attacks | 6 attacks |
The Scale of Supply-Chain Cyber Attacks in 2026
Software and third-party dependencies are a significant attack corridor for modern organisations. CYFIRMA analysed 42 supply-chain incidents disclosed between November 2025 and October 2026, coding each intrusion across approximately 20 distinct technical fields, including supplier categorisation, specific delivery vectors, threat actor attribution, root cause, and the operational role of artificial intelligence. In CYFIRMA’s 42-incident dataset, 34 cases were supplier-mediated (81%); 26 of those 34 involved supplier compromise, failure or channel/access abuse (76% of supplier-mediated cases, representing 62% of the overall 42-incident sample). These metrics reflect a curated technical sample of disclosed incidents rather than a universal population estimate.
In CYFIRMA’s dataset, many incidents reached victims through compromised suppliers or abused supplier channels and access. The available incident tracking shows that supply-chain compromises are recurring rather than isolated events.
Parallel data tracking the software engineering pipeline highlights an equally intense operational tempo within open-source package repositories. Independent analysis from StepSecurity tracked 56 distinct open-source supply-chain compromises over the 12 months covered by its 2026 report, encompassing malicious software packages, compromised development extensions, and poisoned GitHub Actions. The StepSecurity dataset shows recurring open-source supply-chain activity, including 13 incidents in March 2026 and nine or more in each of April through June.
- •In CYFIRMA’s 42-incident dataset, 34 cases reached victims through a supplier (81%).
- •56 distinct open-source software supply chain compromises were systematically tracked across developer ecosystems over a 12-month reporting window.
- •StepSecurity recorded its highest listed monthly count in March 2026, with 13 incidents.

UK Baseline Exposure: DSIT and NCSC Metrics
The wider threat environment within the United Kingdom provides critical context for these supply-chain vulnerabilities, establishing a clear distinction between population-level prevalence and curated incident datasets. Official government findings from the UK Cyber Security Breaches Survey 2025/26 published by the Department for Science, Innovation and Technology (DSIT) reveal that 43% of UK businesses experienced a cyber security breach or attack in the preceding 12 months. When isolating corporate enterprises, this figure scales substantially: 69% of large UK businesses reported suffering a breach or attack over the same period.
Furthermore, DSIT estimated that 19% of all UK businesses were victims of at least one cyber crime in the preceding year. This proportion represents approximately 267,000 individual commercial organisations dealing with direct technical intrusions, credential theft, or unauthorised data access across the UK economy.
Operational reporting from the National Cyber Security Centre (NCSC) reflects the volume of enterprise compromise handled centrally. During the period covered by its 2026 Annual Review, the NCSC received 1,831 reports; 337 required support and 80 were classed as nationally significant. In its 2026 Annual Review period, the NCSC said its Early Warning service notified 8,500 organisations of events indicating a suspected compromise.
Public Sector Vulnerability and the Blast-Radius Multiplier
The concentration of risk is particularly visible across public sector infrastructure and regulated bodies, where enterprise services are deeply integrated with external contractors, digital service providers, and outsourced software platforms. A Risk Ledger survey of UK public-sector cyber-security and third-party-risk professionals found that 82% of respondents reported at least one supply-chain incident in the previous year; this is not a population-wide public-sector estimate.
Recurring exposure remains common within this surveyed cohort. The Risk Ledger dataset indicates that 40% of surveyed public-sector professionals reported experiencing two or more supply-chain incidents during the preceding twelve months.
Consequently, supplier governance has become a dominant operational challenge for technical leadership. The research established that 86% of surveyed UK public-sector respondents placed supply-chain incidents among their top three concerns for 2026. A vulnerability in a specialist supplier could affect multiple connected public-sector organisations, depending on access and network architecture.
Anatomy of Upstream Compromise: Secrets Theft and Package Poisoning
Modern third-party intrusions exploit developer workflows, identity tokens, and automated software dependencies. Rather than exploiting complex memory-corruption bugs in runtime environments, threat actors systematically target the trust boundaries embedded within build systems and open-source software registries.
A clear demonstration of automated developer compromise occurred during the Shai-Hulud campaign in September 2025, which used stolen maintainer tokens to compromise more than 500 npm packages. The incident highlighted critical vulnerabilities in token hygiene across developer environments, underscoring the necessity of short-lived authentication credentials, automated secret scanning in repositories, and mandatory multi-factor authentication for package publication to prevent automated worm propagation.
The potential downstream reach of supply-chain harvesting was demonstrated by a focused five-day campaign documented by StepSecurity. StepSecurity described a five-day campaign that stole 78,330 secrets from 2,186 organisations. StepSecurity reported that 92 public companies were among the affected organisations, with a combined reported market value of $6.2 trillion. The campaign demonstrates how stolen secrets can expose downstream cloud and administrative environments; its impact on perimeter detection depends on the affected organisations’ controls.
- •More than 500 npm packages were compromised during September 2025 by the Shai-Hulud worm using stolen maintainer tokens.
- •A single five-day threat campaign successfully exfiltrated 78,330 operational secrets from 2,186 corporate organisations.
- •Victims of that campaign included 92 publicly traded corporations representing $6.2 trillion in aggregate market capitalisation.
Access Abuse vs Product Flaws: The Delivery Taxonomy
Understanding how third-party incidents develop requires separating supplier-hosted access vectors from traditional software vulnerabilities. Security teams often treat supply-chain management purely as a patching problem, assuming that regular vulnerability scanning covers their third-party risk. In CYFIRMA’s sample, supplier compromise or access/channel abuse was more common than exploitation of a supplier-product flaw.
In CYFIRMA’s 42-incident dataset, 34 cases were supplier-mediated (81%); 26 of those 34 involved supplier compromise, failure or channel/access abuse (76% of supplier-mediated cases, or 62% across all 42 cases). In these incidents, the software itself did not necessarily contain an unpatched zero-day exploit; instead, the external vendor’s infrastructure was compromised, or legitimate access channels connecting the supplier to the customer network were hijacked by attackers.
CYFIRMA classified eight supplier-mediated cases as exploitation of a flaw in a supplier’s product at the customer. This technical breakdown demonstrates that relying solely on software vulnerability assessments or Common Vulnerabilities and Exposures (CVE) scanning leaves an organisation exposed to the most common delivery vector: administrative account compromise and channel hijacking within trusted vendor relationships.
View the data behind this chart
| Layer | Detail |
|---|---|
| Large Business Breaches | 69% of large commercial organisations reported a breach or attack |
| All Business Breaches | 43% of all UK businesses reported experiencing a cyber security incident |
| Cyber Crime Victimisation | 19% of UK businesses (~267,000 organisations) victimised by cyber crime |
Bridging Procurement and AppSec: Actionable Supplier Governance
Traditional third-party risk management often relies on static annual questionnaires that fail to capture real-time operational risks. An annual compliance document cannot alert security teams to a compromised pipeline token or an exploited administrative account at an external service provider. Establishing effective oversight requires a continuous technical framework that bridges corporate procurement, operational IT, and application security.
For UK IT buyers, supply-chain risk is not only a software-security issue: it directly impacts outsourced IT, cloud administration, managed service providers, education, and public-sector procurement. Supplier assessments should therefore record privileged access, subcontractors, software components, incident-notification obligations, recovery responsibilities, and evidence of security controls before renewal or onboarding.
Organisations seeking to enhance their resilience should ensure technical reviews integrate structured processes for vetting third-party suppliers. These evaluations must examine the vendor's subcontractor chains, mandatory incident notification windows, administrative isolation, and recovery responsibilities. Connecting procurement workflows to continuous security monitoring ensures that supply-chain governance operates as an active technical defence rather than an administrative rubber-stamping exercise.
- •Given that 26 of 34 supplier-mediated breaches involved access and channel abuse rather than product flaws, prioritise privileged-access reviews and least-privilege enforcement over CVE vulnerability scanning.
- •With 56 open-source supply-chain incidents tracked in a year and campaigns compromising 500+ packages via stolen tokens, maintain strict inventories of build dependencies, rotate publish credentials, and restrict CI/CD pipeline permissions.
- •To mitigate the blast radius seen in campaigns harvesting over 78,000 corporate secrets, mandate contractual incident-notification deadlines and clear operational recovery obligations across all suppliers.
- •Because specialist supplier compromises propagate across connected ecosystems—affecting 82% of surveyed public-sector organisations—require subcontractor disclosures to evaluate risks beyond tier-1 vendors.
- •In light of high enterprise breach baselines (69% among large UK firms), require independently verified evidence of technical security controls prior to contract onboarding and renewal.
Methodology
This data study examines the systemic profile of supply-chain attacks and general organisational cyber risk by compiling verified datasets from government agencies, public-sector researchers, and technical threat intelligence laboratories. Data points were sourced from the UK Department for Science, Innovation and Technology (DSIT) Cyber Security Breaches Survey 2025/26, the National Cyber Security Centre (NCSC) Annual Review operational reporting, CYFIRMA threat intelligence research, StepSecurity open-source tracking metrics, and Risk Ledger's public-sector risk survey.
Care must be taken to distinguish population-level statistical estimates from curated incident counts and professional surveys. DSIT metrics represent representative population-wide estimates of UK business breach rates (43% across all businesses, 69% for large businesses, and 19% cyber crime victimisation representing approximately 267,000 businesses). NCSC data reflects operational caseloads, logging 1,831 reports affecting organisations, 337 incidents requiring support, 80 nationally significant incidents, and 8,500 Early Warning alerts.
In contrast, threat intelligence and practitioner datasets are bounded by specific technical monitoring scopes. CYFIRMA's research examined 42 specific supply-chain incidents disclosed between November 2025 and October 2026, categorised across approximately 20 fields including supplier category, attack vector, actor, AI role, and root cause. StepSecurity tracking captured 56 distinct open-source software supply-chain compromises over a 12-month period, including malicious packages, poisoned GitHub Actions, and compromised IDE extensions, recording 13 incidents in March 2026, nine in April, nine in May, 10 in June, and six in July. Risk Ledger's findings reflect a survey of UK public-sector cyber-security and third-party-risk professionals, rather than an all-inclusive census of UK public bodies.
Sources
Every figure in this article traces to the sources below.
- •Department for Science, Innovation and Technology — Cyber Security Breaches Survey 2025/26
- •Department for Science, Innovation and Technology — DSIT Cyber Security Newsletter May 2026
- •National Cyber Security Centre — Annual Review 2026 Incident Management
- •CYFIRMA — Threat Horizon: Where Supply Chain Risk and AI-Enabled Attacks Are Heading
- •StepSecurity — State of Open Source Supply Chain Attacks
- •Risk Ledger — State of Supply Chain Security in the UK Public Sector
The 8 data points behind this study are free to download, each with its source. The figures belong to those sources: cite the named source and check its terms before reusing a figure.
Cite as: Servnet Research, “Supply Chain Attack Statistics 2026: Incident Dataset”, servnetuk.com, 2026.
Servnet Research publishes dated observations from public sources for information only. It is not legal, security, financial or investment advice, and data are provided without warranty. Figures from named sources belong to those sources. Spotted an error, or want something corrected or removed? See our corrections and takedown policy.
