Dependency Cooldowns Can Slow Malicious Package Releases, but Do Not Eliminate Supply-Chain Risk
Summary
Recent malicious releases in npm, PyPI, and GitHub Actions show how quickly compromised dependencies can spread. Cooldowns and package-scanning or blocking tools reduce exposure, but cannot prevent delayed malware or vulnerabilities in already-published packages.
Key points
- Datadog’s 2026 State of DevSecOps report found that half of organizations in scope used at least one dependency within a day of release; the figure was 54% for JavaScript applications.
- The article cites the Axios compromise and the s1ngularity and Shai-Hulud attacks as examples of malicious npm releases spreading through package dependencies.
- TeamPCP used compromised credentials to publish malicious Trivy versions affecting GitHub Actions workflows and Docker images; attackers also released two compromised LiteLLM versions on PyPI.
- The article links npm’s large transitive dependency trees and rapid worldwide release availability to increased supply-chain exposure; version ranges such as ^ and ~ can automatically accept future releases.
- Cooldown options include npm’s minimum release age setting, Yarn and pnpm configurations, and Dependabot cooldowns across supported ecosystems.
- The article says Axios malicious versions were discovered roughly three hours after release and s1ngularity packages were live for around four hours; it estimates a 12-hour cooldown would have blocked their spread.
- Cooldowns may be bypassed by delayed malware execution and do not address vulnerabilities in already-published packages. GuardDog and Supply-Chain Firewall provide additional package detection or blocking.
Article Details
- Defense Focus
- Reduce exposure to malicious dependency releases by delaying installation, detecting malicious packages before installation, blocking known malicious packages, and identifying affected environments.
- Detection Methods
- Use GuardDog to analyze npm and PyPI packages for malicious indicators before installation.
- Use Datadog SCA and its emerging threats feed to identify hosts, containers, and build environments with compromised packages installed and assess exposure to newly identified malicious packages.
- Data Sources
- Installed-package and software-composition data from hosts, containers, and build environments.
- Newly identified malicious-package information surfaced through the emerging threats feed.
- Package release age and dependency-update information used to enforce cooldowns.
- Platforms
- Developer workstations
- CI/CD pipelines
- Hosts
- Containers
- Build environments
- Defensive Actions
- Configure dependency cooldowns or minimum release ages; the article recommends one week as common guidance and says a 12-hour cooldown would have blocked the described Axios and s1ngularity releases.
- Use ecosystem-supported minimum-age settings in npm, Yarn, or pnpm, or configure Dependabot cooldowns for supported ecosystems.
- Scan npm and PyPI packages for malicious indicators before installation.
- Block installation of known malicious or vulnerable packages at developer workstations.
- Use SCA to identify environments with compromised packages installed and assess exposure promptly.
MITRE ATT&CK
T1078 · Valid AccountsThe article reports that TeamPCP used compromised credentials to publish malicious Trivy versions affecting GitHub Actions workflows and Docker images.T1195 · Supply Chain CompromiseAttackers published malicious package releases, including compromised npm packages, to distribute malicious software through package ecosystems.T1204 · User ExecutionMalicious code in compromised packages can execute when dependencies are installed or picked up by CI.
Threat Actors
Vendors
DatadogDefensive measures such as dependency cooldowns, minimum release age settings, and tools like GuardDog, Supply-Chain Firewall, and Datadog SCA can reduce exposure but do not fully eliminate the risk.GitHubRecent supply-chain attacks across npm, PyPI, and GitHub Actions show that rapidly consuming newly released dependencies can introduce malicious releases that propagate within hours and compromise large numbers of
Products
Datadog Code SecurityDatadog Code Security customers can use Software Composition Analysis (SCA) to identify hosts, containers, and build environments that have compromised packages installed.DependabotMitigations include dependency cooldowns/min-release-age features (npm 11.10.0, Yarn/pnpm configs, Dependabot cooldowns) and detection/blocking tools (GuardDog, Supply-Chain Firewall, Datadog SCA), but each hasDockercredentials to publish malicious versions of Trivy, which impacted both GitHub Actions workflows and Docker images.’)GitHub ActionsRecent supply-chain attacks across npm, PyPI, and GitHub Actions show that rapidly consuming newly released dependencies can introduce malicious releases that propagate within hours and compromise large numbers ofnpmRecent supply-chain attacks across npm, PyPI, and GitHub Actions show that rapidly consuming newly released dependencies can introduce malicious releases that propagate within hours and compromise large numbers ofpnpmMitigations include dependency cooldowns/min-release-age features (npm 11.10.0, Yarn/pnpm configs, Dependabot cooldowns) and detection/blocking tools (GuardDog, Supply-Chain Firewall, Datadog SCA), but each hasPyPIRecent supply-chain attacks across npm, PyPI, and GitHub Actions show that rapidly consuming newly released dependencies can introduce malicious releases that propagate within hours and compromise large numbers ofYarnMitigations include dependency cooldowns/min-release-age features (npm 11.10.0, Yarn/pnpm configs, Dependabot cooldowns) and detection/blocking tools (GuardDog, Supply-Chain Firewall, Datadog SCA), but each has
Tools
GuardDogDefensive measures such as dependency cooldowns, minimum release age settings, and tools like GuardDog, Supply-Chain Firewall, and Datadog SCA can reduce exposure but do not fully eliminate the risk.Supply-Chain FirewallDefensive measures such as dependency cooldowns, minimum release age settings, and tools like GuardDog, Supply-Chain Firewall, and Datadog SCA can reduce exposure but do not fully eliminate the risk.