Software Supply Chain Security: Stop Bad Packages
Software supply chain security is the set of checks that stop malicious or vulnerable open source packages from reaching developers and build systems. It screens components before install, records what each release contains, and blocks packages that fail policy, so a compromised dependency cannot run code on a developer machine or slip into production.
By Abdullah Shafique, AI Engineer
What is software supply chain security?
Software supply chain security covers every component a team pulls in, including parts it did not write: open source libraries, third party packages, container images, and build tools. A modern application is assembled from these parts, and trust in the finished software depends on knowing where each part came from and whether it is safe. Sonatype describes this shift plainly in its 2026 research on open source malware: the question is whether an organization can stop a malicious package before it reaches developers and build systems.
A vulnerability is an unintentional flaw in otherwise legitimate code. Open source malware is deliberately designed to cause harm, according to Sonatype, and that intent changes how it must be defended against. A scanner that only lists known flaws will miss a package that was built to steal credentials. Teams need controls that judge a package before it is trusted, since a check after install comes too late.
Why are malicious packages rising in 2025?
Sonatype identified over 454,600 new malicious packages in 2025, pushing the total beyond 1.233 million, in research published in May 2026. Over 99 percent of open source malware occurred on npm. Attackers optimize for developer workflows because those workflows hold tokens and access to release systems.
Trusted release paths have become part of the attack surface. Sonatype points to cases where attackers abused automation, service accounts, and tokens to inherit built in trust and spread widely, and to cases where a small change in a dependency executed on install, deployed a secondary payload, and removed traces of its activity. A familiar package name or a historically trusted maintainer does not guarantee safety when attackers position themselves inside those trust signals.
How do attackers reach developers?
Install time is the moment that matters most. Malware embedded in a package can execute during installation, before any release time scan runs. Sonatype warns that end of pipeline security is no longer sufficient for this reason: by the time a late scan reports, malware may have already exfiltrated secrets or established persistence. Developer machines and continuous integration environments deserve the same protection as production systems.
Transitive dependencies widen the opening. A team may audit the packages it chose directly and still pull in many more through frameworks and libraries, with unclear ownership for each indirect component. Sonatype lists transitive dependencies, install scripts, and unusual changes among the signals that need inspection. A policy that only checks direct dependencies leaves most of the surface unchecked.
Secrets handling sits next to this problem. A stolen token from a developer machine can move laterally and escalate access, as Sonatype describes in its account of staged, multi step attacks. Limiting credential exposure, enforcing least privilege access, and rotating secrets quickly after an incident are the practical responses. Readers who run privileged build or release accounts should also review the controls in Privileged Access Management: Cut Standing Admin Rights, which covers vaulted credentials and time limited elevated rights.
Why do teams keep downloading vulnerable versions?
Malicious packages are only half the story. The other half is avoidable risk from known vulnerabilities with fixes available. In 2025, developers pulled Log4j from Maven Central nearly 300 million times, and roughly 13 percent of those downloads, about 40 million, still contained Log4Shell, even though safe versions had been available for almost four years, according to Sonatype research published in December 2025. Across the broader ecosystem, about 95 percent of vulnerable components downloaded already had a safer version available, while only around 0.5 percent truly lacked a fix.
Habits explain most of that gap. Dependencies get set and forgotten once they compile, and tools generate noisy finding lists without a clear upgrade instruction. Feature work gets rewarded while quiet removal of a vulnerable library does not. The result is a stubborn baseline of vulnerable downloads. Fixing this pattern starts with a simple rule: when a safer version exists, move to it, and give any exception an owner and an expiry date.
Prioritization data adds a second difficulty. In 2025, 65 percent of open source CVEs were left without CVSS scores by the National Vulnerability Database, according to Sonatype, forcing teams to triage without consistent severity signals. A long list of findings without exploitability or reachability context pushes effort toward the loudest alerts. Screening that adds exploitability and reachability to each finding cuts that noise.
What should a team check before approving a package?
A workable approval check has four parts. First, inventory everything, including transitive dependencies, so the team knows what it is running. Second, screen each component at ingestion, before it reaches a developer machine, using malware detection and policy enforcement that can block or quarantine a suspicious package. Third, control the pathway: a proxy repository that mediates access to public registries gives the team one place to enforce policy. Fourth, record the decision in a software bill of materials, so a new vulnerability can be matched against shipped software in minutes.
| Approach | When it checks | What it stops | Where it falls short |
|---|---|---|---|
| Scan at the end of the pipeline | After the build | Known flaws in finished code | Install time malware may already have run |
| Proxy repository with block rules | Before install | Known malicious and non compliant packages | Transitive packages still need full inventory |
| Full governance with SBOM | Before install and after release | Malicious packages, vulnerable versions, and unknown components | Needs upkeep as dependencies change |
The United States Cybersecurity and Infrastructure Security Agency, known as CISA, together with its co authoring partners, released the 2026 Minimum Elements for a Software Bill of Materials, replacing the 2021 guidance from the National Telecommunications and Information Administration. The revision adds new minimum elements, including component hash algorithms, component licenses, the name of the SBOM generation tool, and generation context, and it applies the minimum elements to SBOMs for all software. An SBOM is a list of the components that make up a software package and their supply chain relationships, and it helps teams assess supply chain risks and make informed security decisions.
An SBOM only helps when it is treated as a living record. Sonatype makes the same point about federal programs: an SBOM generated at release loses relevance as dependencies evolve, and without enrichment and enforcement it becomes a snapshot. Regenerate the SBOM with each release, link it to vulnerability alerts, and use it to answer one question fast when a new flaw appears: does this affect anything we shipped.
Bhagwat Swaroop, chief executive officer of Sonatype, put the stakes in governance terms: "Software supply chain security must be treated as a core part of how enterprises govern innovation, manage risk, and ship trusted software at scale." Attackers now target the build process itself, and the fix is governance that runs at the same speed as development.
Recovery planning belongs in the same program. If a malicious package does reach a build, the team needs isolation, clean rebuilds, and secret rotation ready to go, without a debate under pressure. The steps in Ransomware Recovery Plan: Restore Fast, Pay Less cover tested restore steps and decision logging.
Frequently asked questions
What is a software supply chain attack?
It is an attack that reaches an organization through a component it trusts, such as a malicious open source package, a compromised build tool, or a tampered release path.
How many malicious packages did Sonatype find in 2025?
Sonatype identified over 454,600 new malicious packages in 2025, pushing the total beyond 1.233 million, with over 99 percent of open source malware occurring on npm.
Why do teams keep downloading vulnerable components?
Sonatype found that about 95 percent of vulnerable components downloaded already had a safer version available, while only around 0.5 percent truly lacked a fix, so most of the risk comes from staying on old versions.
What is an SBOM?
An SBOM, or software bill of materials, is a list of the components that make up a software package and their supply chain relationships. CISA's 2026 Minimum Elements add fields such as component hash algorithms, component licenses, SBOM tool name, and generation context.
What should a small team do first?
Inventory all dependencies including transitive ones, route downloads through a proxy repository with block rules, screen packages before install, and regenerate the SBOM with each release so a new vulnerability can be checked against shipped software quickly.
Which dependency check caught a risky package in your last release, or which check are you adding next? Share your approach in the comments, including what worked and what got in the way. Use the share buttons above to pass this post to a teammate who owns your build pipeline.

Comments
Post a Comment