CybersecurityHacking

GitHub Fortifies npm with Package Firewall to Thwart Malicious Installs

Analyst 207||Source: TheHackerNews
A laptop sits on a clean surface with a blurred screen and subtle background of out-of-focus computer equipment.

"The firewall inspects both metadata requests and package downloads for signs of malicious activity, acting as an install-time policy gate," GitHub said.

What the npm firewall does at install time

GitHub has introduced a preview package firewall that blocks installation of suspicious npm packages during installation time. The feature, which currently supports only npm packages, inspects both metadata requests and package downloads and sits between endpoints or internal registries and upstream package repositories. According to the Microsoft subsidiary, the placement is intended to deter malware attacks that compromise systems when packages are installed.

Policy controls administrators must configure

Administrators using the firewall must configure one or more policy controls. GitHub lists the following options for blocking or allowing installs:

  • Block known malware by checking against the GitHub Advisory Database for active malware advisories.
  • Block packages based on the severity of vulnerabilities by checking the GitHub Advisory Database for flaws that affect the requested package version. The control defaults to "Critical only" but can be set to "High or higher," "Medium or higher," or "Any severity."
  • Block attestation downgrades by comparing attestations for the requested package version with those of earlier versions and stopping the download if the requested version does not have an SLSA attestation.
  • Block newly-introduced install scripts by checking whether the package recently added scripts that run using preinstall or postinstall hooks, which can be abused to steal sensitive data.
  • Block packages based on a cooldown period that prevents versions newer than the configured minimum age from being installed. The cooldown value can range from 1 to 365 days, defaults to 1 day, and can be disabled by setting it to 0.

How teams deploy the firewall and handle exceptions

The firewall is available in public preview for all GitHub Enterprise Cloud customers, including data-resident GitHub Enterprise Cloud. The intended workflow is that endpoints such as coding agents and CI/CD hosts use the firewall for their requests instead of pointing directly to public registries, so installs go through the policy gate.

If the firewall blocks a package that a user needs, the user can submit an exception request. Those exception requests can then be approved by enterprise administrators and security managers.

Cooldowns, Rust 1.100, and ecosystem trends

GitHub’s cooldown control joins a broader move across package ecosystems to add friction before new releases are allowed into automated builds. The report notes that Rust 1.100, scheduled for release on November 12, 2026, will add support for a configurable minimum publish age via the "global-min-publish-age" option in "cargo/config.toml." When unspecified, Rust will apply a seven-day waiting period by default. Over the past year, similar waiting periods have been implemented across npm, Python, Microsoft Visual Studio Code, Ruby, Bun, pnpm, and Yarn to give security scanners and maintainers time to flag and block malicious releases before they are installed.

What this means for coding agents, CI runners, and enterprise administrators

  • Coding agents and CI runners: The firewall is designed to be used by automated endpoints that install dependencies without explicit human approval, forcing those agents to route installs through the policy gate rather than fetching directly from public registries.
  • Enterprise administrators and security managers: Administrators must select and tune policy controls—severity thresholds, cooldown periods, and attestation checks—and process exception requests when legitimate fixes are being blocked.
  • Open-source maintainers and security researchers: The cooldown and attestation controls buy time for maintainers and scanners to detect and flag malicious releases, but they also slow deployment of legitimate fixes unless exceptions are made.

GitHub’s firewall and the broader adoption of minimum-publish-age policies aim to add friction to attacks in which an adversary publishes a poisoned version of a package after gaining control of a maintainer account. As Socket noted in the coverage, "The tradeoff is that legitimate fixes have to wait, too, unless developers make an exception," and a cooled release that escapes detection may still remain malicious. The value, the source says, is in buying researchers, maintainers, and registries time to act before the next dependency update spreads an attack further.

Original story: https://thehackernews.com/2026/10/github-launches-npm-firewall-to-block.html

Emerging ThreatsGithubNpmSupply Chain SecurityThreat DetectionMalware OperationsSecure Software DevelopmentPackage ManagementPackage FirewallInstall-Time Security
Related Intelligence

Continue Reading

Modern tech company interface on a large computer screen with blurred coding content and office background.

Exposed Cloud Credentials Abound in Public Gitee Repositories

A recent scan of public Gitee repositories uncovered a staggering 26,400 exposed cloud credentials that still worked when tested, highlighting the alarming risk of long-discarded secrets remaining live and exploitable. This shocking discovery was made by independent researcher Ben Zimmermann, who analyzed a massive 7.25 million public repositories.

Analyst 207
Sleek AI workstation sits at center of modern security operations center.

AI Redefines Security Operations with Emerging Threat Operator Role

AI is revolutionizing security operations by taking over tasks traditionally handled by security analysts, paving the way for a new era of AI-driven threat detection and response. By integrating functions like threat intelligence, hunting, and incident response, AI agents can now tackle security challenges with unprecedented speed and efficiency.

Analyst 207
Windows 11 laptop on a desk with update progress on screen in a modern office setting.

Microsoft Releases KB5127936 Update, Bolstering Windows 11 Security and Features

Microsoft just dropped a new update, KB5127936, for Windows 11, packing 41 changes and fixes to supercharge your experience. This optional update is a sneak peek at what's coming next, and you can grab it now from the Microsoft Update Catalog to try out the latest features and improvements.

Analyst 207
Factory interior with CNC milling machine and Windows servers on a rack in the background.

Hackers Exploit Anger, Not Weak Passwords

You'd think hackers would target weak passwords, but surprisingly, they're more likely to exploit your emotions - specifically, your anger. A recent factory network scan revealed few obvious entry points, but it's what hackers use to get inside that might just surprise you.

Analyst 207