Loading story…
GitHub has changed Dependabot to wait three days before opening pull requests for non-security version updates, aiming to keep fast-moving malicious package releases out of automated developer workflows. The company said the change was driven by repeated software supply-chain incidents in which poisoned npm releases were detected and removed within hours, but still had enough time to be pulled into builds. GitHub pointed to a 2025 npm compromise in which an attacker phished a maintainer and published malicious versions of widely used packages including chalk and debug, with code that rewrote cryptocurrency wallet addresses before the packages were taken down roughly two hours later. Security updates tied to known advisories are not delayed and will still be issued immediately.
The move aligns with broader industry guidance that the first hours after a package is published are the highest-risk period for dependency consumers. Research cited similar attacks affecting 18 npm packages with more than 2.6 billion weekly downloads and the Nx build attack, which remained live for about four hours, reinforcing recommendations to delay automated updates by 24 to 48 hours or longer. GitHub said the npm ecosystem logged more than 6,500 malware advisories in the year ending May 2026 and urged teams to combine cooldowns with other controls, including lockfiles, careful review before merge, scoped CI tokens, disabling install scripts where possible, and pinning dependency versions to reduce supply-chain exposure.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
4 events from the most recent confirmed update back to the earliest known activity.
The compromised npm packages cited by GitHub were taken down about two hours after publication. GitHub highlighted that this was still long enough for automated dependency update tools to ingest the poisoned releases.
In September 2025, an attacker phished an npm maintainer and published malicious versions of chalk, debug, and other widely used packages. The malware rewrote cryptocurrency wallet addresses, creating a short but dangerous supply-chain exposure window.
On 2026-07-23, GitHub announced that Dependabot now waits three days by default before opening non-security version update pull requests. The change is intended to reduce exposure to fast-moving software supply-chain attacks while leaving security updates unaffected.
On 2026-01-12, Semgrep published an analysis of npm supply-chain attacks, including incidents involving 18 compromised packages and the Nx build attack. The post recommended mitigations such as pinning versions, blocking install scripts, and delaying automated updates by 24 to 48 hours.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
4 references tracked. Mallory keeps watching after this page renders.
thehackernews.com
Open sourcehelpnetsecurity.com
Open sourcegithub.blog
Open sourcesemgrep.dev
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Package ecosystem maintainers and security vendors highlighted new guardrails and failure modes in automated dependency workflows. npm CLI 11.x introduced **`minimumReleaseAge`**, a release “cooldown” control that blocks installation of newly published versions until they reach a configured age, aiming to reduce exposure to malicious packages that rely on rapid adoption before detection or takedown. npm also added bulk configuration for **OIDC trusted publishing**, aligning with broader efforts to harden CI-based publishing; similar release-age gating has already been implemented in other Node.js package managers (pnpm, Yarn, and Bun), though npm’s initial implementation lacks an exclusion mechanism for cases like urgent internal hotfixes. Separately, StepSecurity reported detecting a “release storm” affecting multiple Microsoft **`@types/*`** packages on npm, where dozens of semver releases were published within 24 hours with no code changes beyond repeated deprecation-version bumps—attributed to an automation loop tied to a scheduled GitHub Actions workflow in *microsoft/DefinitelyTyped-tools* (`publish-packages.yml`). In the Go ecosystem, a maintainer of widely used cryptography code criticized GitHub **Dependabot** for generating large volumes of low-signal alerts and PRs after a minor security fix, arguing the tool often flags repositories based on dependency presence rather than reachability/actual impact, creating alert fatigue and potentially reducing security; he recommended reachability-aware tooling such as *govulncheck* for Go vulnerability triage.
Jun 29, 2026
GitHub and the Python Package Index (**PyPI**) introduced new time-based protections aimed at slowing the spread of malicious open-source packages and preventing tampering with trusted releases. GitHub added a default **72-hour cooldown** for non-security Dependabot updates, delaying automatic pull requests for newly published package versions so suspicious releases have more time to be detected and removed before broad adoption. PyPI said it will block maintainers from uploading new files to package releases more than **14 days** old, a safeguard designed to stop attackers from poisoning long-stable versions after compromising maintainer accounts, tokens, or publishing workflows. PyPI said it has not seen this technique abused to date, but noted there is no technical barrier to it; the restriction is expected to be enforced after the `Upload 2.0` API and staged previews are standardized under **PEP 694**. Both platforms said the changes respond to repeated software supply-chain incidents, while GitHub also urged developers to keep using controls such as lockfiles, scoped tokens, and disabling unnecessary CI install scripts.
Jul 27, 2026
A series of high-profile supply chain attacks targeted the npm ecosystem, compromising hundreds of packages and exposing sensitive data. The s1ngularity attack exploited a vulnerability in GitHub Actions to steal npm publishing tokens for Nx packages, leading to the distribution of credential-harvesting malware and the public exposure of thousands of private repositories and secrets. Another incident involved a phishing campaign against a prominent npm maintainer, resulting in the compromise of widely used packages such as debug and chalk. These attacks highlighted the persistent risks posed by weak CI/CD protections, compromised dependencies, and social engineering tactics. In response to these incidents, GitHub implemented stricter security measures for npm package publishing. The new requirements include mandatory two-factor authentication (2FA) for all local publishing, limiting token lifetimes, and promoting trusted publishing workflows. Legacy authentication methods are being deprecated in favor of FIDO-based 2FA, and developers must now use hardware security keys, biometrics, or authenticator apps for authentication. These changes aim to reduce the risk of account takeovers and malware injection, but experts warn that additional security practices are necessary to address other attack surfaces within the software supply chain.
Jun 29, 2026