Bloom Security reports hijacking risk for over 1,500 npm packages


The packages had more than 10 million downloads collectively, Bloom Security said, according to The Hacker News’s 13 October report. The reported guidance advises maintainers to check that approved repository names still point to code they control.
Bloom Security found more than 1,500 npm software packages potentially vulnerable to unauthorized publishing through unused trust settings, The Hacker News reported on 13 October. The cybersecurity company said those packages had more than 10 million downloads collectively. These figures describe potential exposure and total package downloads, not demonstrated compromises or downloads of malicious versions.
GitHub announced on 2 October that unvalidated npm trusted-publishing configurations expire 48 hours after creation and can no longer authorize publishing. GitHub said the deadline limits the risk of trusting a repository or project name that changes ownership.
npm is a registry where developers publish software packages. Its trusted-publishing system lets an approved automated workflow, such as one running through GitHub Actions, publish using a short-lived credential rather than a stored, long-lived secret. A trusted-publisher binding is the setting that links a package to its approved publishing workflow.
Bloom’s finding, called SlugFest, concerned bindings that had never been used to publish. According to The Hacker News, npm initially identified the approved repository by its human-readable owner/repository name, called a slug. Until the first successful publish, npm ignored the repository’s permanent numeric identity, which remains unchanged when a repository is renamed or transferred.
If a rename, transfer or deletion freed that name for someone else to claim, an attacker could create a different repository at the same address. For a still-valid binding that had never published, the matching name could authorize an unauthorized release under the victim package’s legitimate name without credential theft, according to Bloom’s findings. A malicious version could then use the package’s established reputation and existing relationships with software that depends on it.

The Hacker News reported that Bloom disclosed the findings to GitHub on 6 June.
A first successful publish validates the configuration and exempts it from expiry, GitHub said. Changing the repository or project identity requires a new trust relationship with a fresh 48-hour validation window. Ordinary edits do not restart the deadline.
If a configuration expires, GitHub instructs users to recreate it to start another 48-hour window. Expired configurations remain visible in trusted-publisher settings but do not count toward per-package limits. Other valid configurations on the same package are unaffected.
GitHub also said npm rejects trusted-publishing tokens—the credentials that authorize publishing—from GitHub Actions issue_comment events, alongside the existing restriction on pull_request_target events.
GitHub advises affected developers to move publishing to a permitted trigger, such as push, release or workflow_dispatch.
The guidance reported by The Hacker News advises npm maintainers to take these steps:
Altman puts spending on OpenAI’s claimed Navier–Stokes solution at around $10 million, “maybe a little more,” and says the company holds further unpublished mathematical discoveries.
2 min

The platform is designed to investigate software alerts and recommend fixes, while engineers remain involved by default.
3 min

The features extend shopping beyond the TikTok Shop marketplace, but availability and terms remain unclear.
2 min