Skip to main content
Mallory
← Back to News
package-repository-poisoningbuild-pipeline-compromisevendor-distribution-compromise

Dependency Cooldowns Limit Exposure to Malicious Package Releases

Supply Chain Risk · 6 sources · Updated 3mo ago · First seen Aug 31, 2026

Dependency Cooldowns Limit Exposure to Malicious Package Releases

Organizations are adopting dependency cooldowns to prevent build systems from automatically selecting newly published package versions during a defined waiting period. Semgrep deployed a one-week cooldown across Python projects using uv, causing resolution to choose older eligible releases while registries and the community have time to identify and remove malicious packages. Its rollout required an updated uv version, exemptions for internal or urgently needed packages and registries without reliable publication timestamps, and lockfile validation.

The control addresses supply-chain campaigns in which compromised maintainer credentials and trusted release pipelines distribute malicious updates, including reported Shai-Hulud-related npm activity. Renovate provides a comparable minimumReleaseAge policy for dependency-update workflows; updates remain pending until they meet the age threshold, while security updates bypass the delay. Effective deployment depends on strict handling of missing release timestamps, immutable dependency pinning, curated registries, short-lived OIDC credentials, restricted CI/CD runner egress, and hardened GitHub Actions workflows so a compromised update or pull request cannot seize build credentials.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

6 events · Sep 14, 2025 – Aug 4, 2026
  1. Reported Aug 31, 20263mo ago

    Semgrep fixes Kubernetes failure during Poetry-to-uv migration

    During a migration from Poetry to uv, an incorrect service entry point caused a read-only Kubernetes service to reinstall dependencies at startup and crash when installation failed. Semgrep corrected the entry point to use the image-build virtual environment and added CI testing for the failure mode.

    How to Roll Out Dependency Cooldowns Org-Wide | Semgrep
  2. Reported Aug 31, 20263mo ago

    Semgrep begins organization-wide dependency-cooldown rollout

    Semgrep began rolling out dependency cooldowns in late March, using uv configuration to prevent recently published package versions from being selected automatically. The rollout used targeted exclusions for internal packages and registries lacking upload timestamps, plus automated lockfile regeneration and validation.

    How to Roll Out Dependency Cooldowns Org-Wide | Semgrep
  3. Aug 4, 20264mo ago

    ChainDrop reportedly compromises 400-plus packages

    On August 4, 2026, the ChainDrop variant allegedly compromised more than 400 packages within four hours through a legitimate signed release pipeline. The poisoned packages received valid SLSA provenance because the campaign abused a compromised authorized maintainer account rather than forging signatures.

    Shai-Hulud: Whoever controls your package registry controls your pipeline - The New Stack
  4. 2026

    Mini Shai-Hulud targets AI coding-tool credentials

    By spring 2026, the Mini Shai-Hulud variant had emerged and was targeting credentials associated with Claude, Codex, Cursor, and Gemini.

    Shai-Hulud: Whoever controls your package registry controls your pipeline - The New Stack
  5. Nov 24, 20251y ago

    Shai-Hulud 2.0 reportedly backdoors 796 packages

    Shai-Hulud 2.0 allegedly appeared on November 24, 2025, backdooring 796 packages and executing earlier in the installation process. The variant reportedly deleted a user's home directory when it could not obtain credentials or propagate.

    Shai-Hulud: Whoever controls your package registry controls your pipeline - The New Stack
  6. Sep 14, 20251y ago

    Shai-Hulud compromises and republishes npm package versions

    Between September 14 and 18, 2025, the Shai-Hulud worm allegedly altered more than 500 npm package versions. It injected a malicious postinstall payload, harvested developer and cloud credentials, and used stolen npm tokens to republish compromised maintainers' packages.

    Shai-Hulud: Whoever controls your package registry controls your pipeline - The New Stack
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Uv

Organizations

1 linked
Semgrep
Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.