Skip to main content
Mallory
← Back to News
package-repository-poisoningopen-source-dependency-vulnerability

GitHub Launches npm Package Firewall to Block Risky Dependencies Before Installation

Supply Chain Risk · 5 sources · Updated 19d ago · First seen Oct 29, 2026

GitHub Launches npm Package Firewall to Block Risky Dependencies Before Installation

GitHub has launched Package Firewall in public preview for GitHub Enterprise Cloud customers, introducing installation-time controls to block suspicious npm packages. The firewall inspects package metadata requests and downloads against administrator-configured policies covering known malware, vulnerability severity, attestation downgrades, newly introduced installation scripts, and minimum package age. Enterprise administrators and security managers can approve exceptions for blocked packages, providing a controlled route for dependencies that require review.

The launch reflects growing adoption of package publication cooldowns as a software supply-chain defense, with Rust 1.100 also scheduled to introduce configurable minimum-publication-age controls. These waiting periods give defenders time to identify malicious releases before organizations install them, but can delay legitimate security fixes and cannot stop malicious packages that remain undetected beyond the cooldown. Security teams evaluating the preview should pair age-based restrictions with malware and vulnerability policies and a governed exception process, rather than treating package age as proof of safety.

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.

1 event
  1. Reported Oct 29, 202623d ago

    GitHub launches npm Package Firewall in public preview

    GitHub introduced Package Firewall in public preview for all GitHub Enterprise Cloud customers, including those using data residency. The npm-only firewall inspects package metadata and downloads to enforce administrator-configured rules covering malware, vulnerabilities, attestation downgrades, newly introduced install scripts, and minimum package age.

    GitHub Launches npm Firewall to Block Malicious Packages Before Installation
Linked entities

Related entities

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

Open in app →

Organizations

1 linked
GitHub
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.