This page collects the current statistics on attacks that reach an organization through someone else: a vendor, a SaaS platform, a managed file transfer tool, an open-source package or a build pipeline. It draws on the Verizon 2026 Data Breach Investigations Report, IBM’s Cost of a Data Breach reports, Sonatype and ReversingLabs malware research, Black Kite and SecurityScorecard breach analyses, ENISA, CISA, the FBI and government surveys. Each figure is linked to the organization that produced it, with the year it describes.
How to cite: link to this page or to the primary source beside each figure. Survey figures carry their sample size.
Key numbers at a glance
- 48% of breaches in the 2026 DBIR dataset involved a third party, after a 60% increase in one year. (Verizon 2026 DBIR Executive Summary)
- 454,648 new malicious open-source packages were identified in 2025, bringing the total Sonatype has logged since 2019 to 1,233,219. (Sonatype 2026 State of the Software Supply Chain)
- 73% more malicious open-source packages were detected in 2025 than in 2024, and npm accounted for nearly 90% of them. (ReversingLabs 2026 Software Supply Chain Security Report)
- 5.28 downstream victims per third-party breach on average in 2025, the highest Black Kite has recorded and more than double the 2.56 of 2024. (Black Kite 2026 Third-Party Breach Report)
- 267 days: supply chain compromises took the longest of any attack vector to identify and contain in IBM’s 2025 study, at an average cost of $4.91 million. (IBM Cost of a Data Breach Report 2025)
- 14% of UK businesses formally review the cyber risks posed by their immediate suppliers; 7% look at their wider supply chain. (UK Cyber Security Breaches Survey 2025, 2,180 businesses)
1. How many breaches involve a third party
- 48% of breaches had third-party involvement in the 2026 DBIR, which analyzed more than 22,000 confirmed breaches from over 31,000 incidents in 145 countries. Verizon reports the share rose 60% from the previous year’s dataset. (Verizon 2026 DBIR Executive Summary)
- 30% was the figure a year earlier, itself up from roughly 15% in the 2024 edition, when Verizon first started tracking the metric. (Verizon 2025 DBIR)
- Third-party involvement by industry in the 2026 DBIR: Retail 68%, Manufacturing 61%, Education 40%, Public Administration 36%, Financial and Insurance 34%, Healthcare 32%. In small and medium-sized businesses it was 55%. (Verizon 2026 DBIR Executive Summary)
- By region: Latin America and Caribbean 74%, Asia-Pacific 69%, Europe, Middle East and Africa 54%, Northern America 43%. (Verizon 2026 DBIR Executive Summary)
- 35.5% of 2024 breaches were third-party related in SecurityScorecard’s analysis of 1,000 breaches, which it calls likely conservative because of underreporting. Retail and hospitality had the highest rate (52.4%), followed by technology (47.3%) and energy and utilities (46.7%). The US rate was 30.9%. (SecurityScorecard 2025 Global Third-Party Breach Report)
- 41.4% of ransomware attacks in that dataset started through a third party, and two exploited file transfer vulnerabilities accounted for 63.5% of third-party breaches driven by a vulnerability. (SecurityScorecard 2025; report page)
- Healthcare had the most third-party breaches in SecurityScorecard’s sample (78) but a below-average rate of 32.2%. (SecurityScorecard 2025)
- In the United States, supply chain attacks affected 1,251 entities in 2025, up from 660 in 2024, although the number of attacks rose by only one. (ITRC 2025 Annual Data Breach Report, as reported by HIPAA Journal)
The two methods differ. Verizon counts any third-party involvement in a breach it analyzes; SecurityScorecard and Black Kite count publicly reported breaches that started at a vendor. Across these methods, between roughly a third and a half of breaches now involve a third party. For the wider breach picture, see our data breach statistics.
2. How far one vendor breach spreads
Black Kite’s 2026 report covers 136 verified third-party breach events disclosed between January 1 and December 31, 2025. A victim was counted only when explicitly named with credible confirmation of impact. (Black Kite methodology)
- 719 named victim companies, plus about 26,000 additional impacted companies that were never publicly named. (Black Kite 2026)
- 433 million people affected, based on publicly disclosed figures. (Black Kite 2026)
- Average downstream victims per third-party breach: 2.46 (2021), 4.73 (2022), 3.09 (2023), 2.56 (2024), 5.28 (2025). (Black Kite 2026)
- Median time to detect was 10 days (79 events with timeline data), but the median lag before public disclosure was 73 days, with an average of 117. (Black Kite 2026)
- Among the 50 third parties most relied on by Forbes Global 2000 companies, 70% had at least one vulnerability in the CISA Known Exploited Vulnerabilities catalog, 62% had corporate credentials exposed in stealer logs, and 18% were breached in the last year. (Black Kite 2026)
- Across about 200,000 monitored organizations, 53.77% had at least one critical vulnerability and 23.34% had corporate credentials circulating on the dark web. (Black Kite 2026)
- ENISA’s analysis of 8,257 incidents in 2025 found cybercriminals increasingly targeted third-party providers such as digital services, “highly likely” to make their attacks more efficient. (ENISA Threat Landscape 2026)
3. What supply chain breaches cost and how long they last
- 15% of breaches started with a third-party vendor or supply chain compromise in IBM’s 2025 study, the second most common vector after phishing (16%). (IBM Cost of a Data Breach Report 2025)
- $4.91 million: the average cost of those breaches, second only to malicious insiders ($4.92 million), against a global average of $4.44 million. (IBM 2025)
- 267 days to identify (196) and contain (71) a supply chain breach, the longest of any vector. (IBM 2025)
- $227,244: the extra cost a supply chain breach added, the largest of the cost-increasing factors IBM measured in 2025. (IBM 2025)
- 30% of security incidents involving AI models or applications came through the AI supply chain (compromised apps, APIs or plug-ins), the most common cause. (IBM 2025)
- In IBM’s 2026 study of 602 organizations breached between March 2025 and February 2026, the global average cost reached $4.99 million. (IBM newsroom, July 2026) Supply chain compromise was again the second most common vector, took 258 days to identify and contain, and added $227,250 per breach, the largest of 30 cost factors. (IBM 2026, as reported by Cycode)
- In Canada, supply chain compromise was the largest factor raising breach costs in 2026, adding CA$368,000. (IBM Canada, July 2026)
- In the Middle East, supply chain compromise was the vector in 16% of breaches, at an average of $8.45 million. (IBM Middle East, 2026)
The long lifecycle is what makes these breaches expensive: in 2025, breaches that took more than 200 days to resolve cost $5.01 million on average against $3.87 million for shorter ones (IBM 2025). A supply chain breach starts in an environment you do not monitor. Contract terms that require prompt notification, and a third-party penetration test of the vendor systems that touch your data, attack that gap directly.
See what a real pentest finds. Read our sample report, then get a fixed quote in writing.
4. Malicious open-source packages
- 454,648 new malicious packages identified in 2025 across npm, PyPI, Maven Central, NuGet and Hugging Face, for a cumulative total of 1,233,219 since 2019. (Sonatype 2026)
- Sonatype’s headline growth figure for open-source malware was 75%, against 9.8 trillion downloads across the four largest registries in 2025, up 67% year over year. (Sonatype press release, January 2026)
- Over 99% of the open-source malware Sonatype found in 2025 was on npm. (Sonatype 2026)
- ReversingLabs measured a 73% rise in malicious package detections in 2025; malicious activity on npm more than doubled, while PyPI and NuGet malware fell 43% and 60%, which ReversingLabs links to controls such as mandatory two-factor authentication and trusted publishing. (ReversingLabs 2026)
- What the packages do: repository abuse in 55.9% of logged malicious packages, potentially unwanted applications 27.5%, host information theft 5.7%, secrets theft 3.9%, droppers 2.7%, backdoors 2.1%. (Sonatype 2026)
- 21,764 malicious packages in the first quarter of 2026, one every six minutes, with npm at 75%. (Sonatype Q1 2026 Open Source Malware Index)
- By the end of the second quarter of 2026 Sonatype had logged more than 1.8 million malicious packages, and npm accounted for 96.6% of that quarter’s count. (Sonatype Q2 2026 Open Source Malware Index)
5. Worms, maintainer takeovers and dependency confusion
- 500+ npm packages were compromised by the Shai-Hulud worm, which stole GitHub personal access tokens and AWS, Google Cloud and Azure keys. CISA told organizations to pin dependencies to releases from before September 16, 2025. (CISA alert, September 2025)
- 1,000+ npm packages were compromised across two Shai-Hulud campaigns, exposing an estimated 25,000 GitHub repositories. (ReversingLabs 2026)
- 171,740 malicious packages were added to npm in a few months by self-replicating campaigns; one campaign, IndonesianFoods, created more than 150,000 packages in a couple of days. (Sonatype 2026)
- 800+ packages were linked to North Korea’s Lazarus Group in 2025, 97% of them on npm. About 98% carried droppers, 64% stole secrets and 29% had backdoor functions. (Sonatype 2026)
- Dependency confusion, publishing a public package with the same name as a company’s internal one, was demonstrated inside more than 35 organizations in the 2021 research that named the technique; Shopify, Apple and PayPal each paid $30,000 bounties. (Dependency Confusion research, 2021) Sonatype listed dependency confusion among the attack paths of the second quarter of 2026. (Sonatype Q2 2026)
- 27.76%: the rate at which a leading large language model hallucinated dependency upgrade versions in Sonatype’s tests. (Sonatype 2026)
- 94 days: the median time to remediate leaked secrets discovered in a GitHub repository. GitLab tokens made up 50% of leaked development and CI/CD secrets. (Verizon 2025 DBIR)
Every one of these attacks runs on a developer machine or a build runner, where tokens are present and reusable. Our guide to CI/CD pipeline security covers how attackers abuse runners and secrets, and secure coding standards covers dependency and secrets handling in the code itself.
6. Known-vulnerable components that stay in use
- 42 million+ downloads of vulnerable Log4j versions in 2025, 13% of all Log4j downloads, four years after Log4Shell. (Sonatype 2026)
- 838,778 npm releases in 2025 were associated with CVSS 9.0+ vulnerabilities. (Sonatype 2026)
- Nearly 65% of open-source CVEs had no CVSS score from the NVD; when Sonatype scored them, 46% were High or Critical. (Sonatype 2026)
- 14% of Log4j artifacts affected by Log4Shell are now end-of-life, representing more than 619 million downloads in 2025 with no maintained fix path. (Sonatype 2026)
Software composition analysis finds the known-bad version; it does not find the flaw in your own code that calls it. The comparison in our SAST tools guide shows which scanners cover dependencies and which cover first-party code.
7. Major supply chain incidents, verified
| Incident | When | How it worked | Scale (as stated by the source) |
|---|---|---|---|
| SolarWinds Orion | Campaign from Sept 2019; trojanized updates from Feb 2020 | Malicious code inserted into software updates | Nearly 18,000 customers received the compromised update (GAO, 2021) |
| 3CX Desktop App | March 2023 | Installer compromised via an earlier supply chain attack on X_TRADER software | The first cascading software supply chain compromise Mandiant had seen (Mandiant, 2023) |
| MOVEit Transfer (CVE-2023-34362) | Exploitation from May 27, 2023 | Cl0p mass-exploited a zero-day in a file transfer product (CISA AA23-158A) | 2,773 organizations and 95,788,491 individuals; 78.9% of known victim organizations were in the US (Emsisoft tally, last updated June 2024) |
| XZ Utils (CVE-2024-3094) | March 2024 | Malicious code embedded in versions 5.6.0 and 5.6.1 of a compression library | Could allow unauthorized access to affected systems (CISA, 2024) |
| Change Healthcare | 2024 | Ransomware; entry through a remote access service without MFA | 192.7 million individuals; $22 million ransom paid (HHS OCR figure, as reported by HIPAA Journal) |
| Snowflake customer accounts | From April 2024 | Stolen credentials used against customer accounts without MFA | About 165 organizations notified; at least 79.7% of accounts used had prior credential exposure, some dating to November 2020 (Mandiant, 2024) |
| CDK Global | 2024 | Ransomware at a software provider to auto dealers | Cited by Verizon with Change Healthcare and Blue Yonder as cases that caused substantial downtime for customers (Verizon 2025 DBIR) |
| Salesforce via vishing (UNC6040) | Since October 2024 | Callers posing as IT support persuaded staff to authorize a malicious connected app, often a modified Data Loader, which bypasses MFA (FBI FLASH, 2025) | Some victims later received extortion emails (FBI, 2025) |
| Salesloft Drift (UNC6395) | Aug 8 to at least Aug 18, 2025 | Stolen OAuth tokens for a third-party app used to export Salesforce data and hunt for AWS keys, passwords and Snowflake tokens | “Numerous” corporate Salesforce instances (Google Threat Intelligence, 2025) |
| Shai-Hulud npm worm | From Sept 16, 2025 | Self-replicating malware that hijacked maintainer accounts | 500+ packages (CISA, 2025) |
Verizon also cites an insurer’s finding that 40% of claims in its Midyear 2024 report had third-party involvement, naming CDK Global and Change Healthcare. (Verizon 2025 DBIR) The Salesforce cases show that a connected app is a vendor with standing access; our article on malicious OAuth apps explains how to find them.
8. How organizations manage vendor risk
- 14% of UK businesses review risks from immediate suppliers and 7% from the wider supply chain; for large businesses the figures are 45% and 25%, for medium businesses 32% and 15%. (UK Cyber Security Breaches Survey 2025, 2,180 businesses and 1,081 charities)
- 46% of organizations named third-party and supply chain vulnerabilities among their top three challenges to cyber resilience. (WEF Global Cybersecurity Outlook 2026, 804 qualified respondents in 92 countries)
- 78% of CEOs of highly resilient organizations called supply chain and third-party dependencies their most significant resilience challenge. (WEF 2026)
- 74% of highly resilient organizations assess the security of their suppliers, against 48% of insufficiently resilient ones. (WEF 2026)
- 78% of organizations say their cybersecurity programs cover less than half of their vendor ecosystem, 67% still rely on static security audits, and 60% take eight days or more to remediate high-severity issues. 90% are confident they could keep operating through a vendor breach. (SecurityScorecard 2026 Supply Chain Cybersecurity Trends Report, survey of “hundreds” of vendor risk professionals; exact sample not stated)
- Only 23% of third-party organizations fully remediated missing or weak MFA on cloud accounts; for weak passwords and permission misconfigurations, resolving half of the findings took almost eight months. (Verizon 2026 DBIR Executive Summary, 7,513 exposures)
- 66% of suppliers in ENISA’s study of 24 supply chain attacks did not know, or did not report, how they had been compromised. (ENISA Threat Landscape for Supply Chain Attacks, 2021)
A questionnaire is a claim; a test result is evidence. SOC 2 includes vendor management criteria, and our SOC 2 controls list maps them to the evidence an auditor expects.
9. SBOM adoption and regulation
- 47% of organizations were using software bills of materials (SBOMs), with 78% expected in 2022 and 88% in 2023, in the most recent large adoption survey we could verify. (Linux Foundation, The State of SBOM and Cybersecurity Readiness, 2022, 412 organizations)
- 98% of the same organizations used open-source software. (Linux Foundation, 2022)
- March 29, 2023: since this date, section 524B of the FD&C Act has required makers of cyber devices to provide a software bill of materials covering commercial, open-source and off-the-shelf components. (FDA)
- August 22, 2025: CISA published a draft update of the 2021 NTIA SBOM minimum elements for public comment. (CISA)
- The EU Cyber Resilience Act entered into force on December 10, 2024; its reporting obligations apply from September 11, 2026 and its main obligations from December 11, 2027. (European Commission)
- Under the act, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least top-level dependencies; non-compliance with the essential requirements can bring fines of up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher. (Regulation (EU) 2024/2847)
An SBOM tells you which components you ship. Whether they can be reached and exploited in your application is a separate question, which a source code review answers.
What to expect in 2027
These are trends in the cited data, not predictions of our own.
- The third-party share has risen three years running. Verizon’s figure went from about 15% to 30% to 48% across three editions (Verizon 2025 DBIR; Verizon 2026 DBIR), and Black Kite’s downstream victims per breach reached a record 5.28 (Black Kite 2026).
- npm remains the main target. Sonatype put npm at over 99% of 2025 malware and 96.6% in the second quarter of 2026 (Sonatype Q2 2026), while ReversingLabs links falling PyPI and NuGet numbers to stronger registry controls (ReversingLabs 2026).
- EU SBOM duties arrive. Cyber Resilience Act reporting obligations have applied since September 11, 2026, and the SBOM and other main obligations apply from December 11, 2027. (European Commission)
- A vendor forecast on cost. Cybersecurity Ventures estimated software supply chain attacks would cost $60 billion in 2025, rising to $138 billion by 2031, assuming 15% annual growth. This is a projection, not a measurement. (Cybersecurity Ventures, 2024)
Related statistics
Part of our cybersecurity statistics hub. See also data breach statistics and ransomware statistics.
Sources
- Verizon, 2026 Data Breach Investigations Report, Executive Summary (2026)
- Verizon, 2025 Data Breach Investigations Report (2025)
- IBM and Ponemon Institute, Cost of a Data Breach Report 2025 (2025)
- IBM, Cost of a Data Breach Report 2026 press release, Canada release and Middle East findings (2026); report page
- Sonatype, 2026 State of the Software Supply Chain and press release (2026); Q1 2026 and Q2 2026 Open Source Malware Index (2026)
- ReversingLabs, 2026 Software Supply Chain Security Report (2026)
- Black Kite, 2026 Third-Party Breach Report and methodology (2026)
- SecurityScorecard, 2025 Global Third-Party Breach Report (2025) and 2026 Supply Chain Cybersecurity Trends Report (2026)
- ENISA, Threat Landscape 2026 (2026) and Threat Landscape for Supply Chain Attacks (2021)
- Identity Theft Resource Center, 2025 Annual Data Breach Report, as reported by HIPAA Journal (2026)
- CISA, Advisory AA23-158A on MOVEit (2023), XZ Utils alert (2024), npm ecosystem alert (2025), 2025 Minimum Elements for an SBOM (2025)
- FBI, FLASH-20250912-001 on UNC6040 and UNC6395 (2025)
- Google Threat Intelligence and Mandiant, Snowflake (UNC5537) (2024), Salesloft Drift (UNC6395) (2025), 3CX (2023)
- US Government Accountability Office, SolarWinds Cyberattack (2021)
- Emsisoft, MOVEit breach statistics (last updated 2024)
- HIPAA Journal, Change Healthcare cyberattack, citing the HHS Office for Civil Rights breach portal (2025)
- Alex Birsan, Dependency Confusion (2021)
- UK Department for Science, Innovation and Technology, Cyber Security Breaches Survey 2025 (2025)
- World Economic Forum, Global Cybersecurity Outlook 2026 (2026)
- Linux Foundation, The State of Software Bill of Materials and Cybersecurity Readiness (2022)
- US Food and Drug Administration, Cybersecurity resources for medical device manufacturers
- European Commission, Cyber Resilience Act, and Regulation (EU) 2024/2847 (2024)
- Cybersecurity Ventures, Software supply chain attack cost forecast (2024)
Frequently asked questions
What percentage of data breaches involve a third party? 48% of breaches in the Verizon 2026 DBIR had third-party involvement, up from 30% a year earlier (Verizon 2026 DBIR). SecurityScorecard, counting breaches that started at a vendor, put the 2024 figure at 35.5% of 1,000 breaches (SecurityScorecard 2025).
How much does a supply chain breach cost? $4.91 million on average in IBM’s 2025 study, against a $4.44 million global average, and a supply chain breach added $227,244 to the cost of a breach (IBM 2025).
How many malicious open-source packages are there? Sonatype identified 454,648 new malicious packages in 2025 and had logged more than 1.8 million by mid-2026 (Sonatype 2026; Sonatype Q2 2026).
How long does it take to detect a supply chain attack? In IBM’s 2025 study, 267 days to identify and contain, the longest of any vector (IBM 2025). Black Kite found a median 73-day lag between a third-party breach and its public disclosure (Black Kite 2026).
Which industries have the most third-party breaches? In the 2026 DBIR, retail (68%) and manufacturing (61%) had the highest third-party involvement (Verizon 2026 DBIR).
Is an SBOM legally required? For cyber devices submitted to the FDA, since March 29, 2023 (FDA). In the EU, the Cyber Resilience Act requires manufacturers to draw one up, with its main obligations applying from December 11, 2027 (European Commission).
Written by
Wahid Iqbal, Head of Compliance
20+ years in the field. Focus: PCI DSS, ISO 27001 & ISO 22301. Part of the team that scopes, tests, and reports for our clients. Full profile →