Loading story…
GitHub rolled out new supply-chain protections across GitHub Actions and npm to curb attacks that abuse CI/CD workflows and malicious package publishing. On public repositories hosted on GitHub.com, workflow runs that GitHub flags as suspicious are now automatically paused until a repository collaborator with write access approves them through an authenticated web session. The safeguard is enabled by default and is aimed at attacks involving compromised GitHub credentials, malicious workflow files, and workflow-based secret theft or package tampering, though GitHub has not disclosed detection logic and said the control does not guarantee every malicious run will be caught.
GitHub also introduced publish-time malware scanning for npm packages, shifting enforcement from scanning after publication to gating releases before they become available. Under the new process, a package can be published, held for review, or blocked based on scan results, alongside new dual-use metadata requirements such as contentPolicy and DISCLOSURE. The changes build on GitHub’s broader response to open-source supply-chain attacks, including guidance to pin third-party Actions to full commit SHAs, avoid unsafe pull_request_target usage, use OpenID Connect for secretless authentication, and rely on trusted publishing across ecosystems including npm, PyPI, NuGet, RubyGems, and Crates.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
6 events from the most recent confirmed update back to the earliest known activity.
As part of the July 28, 2026 publish-time scanning changes, npm introduced a contentPolicy field and required dual-use packages to include a text-only DISCLOSURE file and use a publishing method that enforces 2FA.
On July 28, 2026, npm announced that newly published packages will be scanned before becoming installable, with packages either published, held for manual review, or blocked based on scan results.
On July 28, 2026, GitHub announced that suspicious GitHub Actions workflow runs in public repositories on GitHub.com will be automatically paused until a repository collaborator with write access approves them in an authenticated web session.
On June 18, 2026, GitHub updated actions/checkout so version 7 and supported backported versions reject common configurations that retrieve unreviewed fork code during privileged pull_request_target or certain workflow_run executions.
In an April 1, 2026 blog post, GitHub said npm scans every package version for malware and that human reviewers validate detections before enforcement because false positives at npm scale would be highly disruptive.
GitHub cited the late-2025 Shai-Hulud attacks as a major supply-chain incident that helped drive changes to its npm and GitHub Actions security roadmap.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
5 references tracked. Mallory keeps watching after this page renders.
opensourcemalware.com
Open sourcetechrepublic.com
Open sourcegithub.blog
Open sourcegithub.blog
Open sourcegithub.blog
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.
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.
Jul 29, 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
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 28, 2026