# SlugFest: The npm Trusted Publishing flaw that trusted names, not IDs

DevFeed: [SlugFest: The npm Trusted Publishing flaw that trusted names, not IDs](<https://devfeed.tech/articles/slugfest-the-npm-trusted-publishing-flaw-that-trusted-names-not-ids-88798.md>)

Original publisher: [Read original article](<https://workos.com/blog/npm-trusted-publishing-slugfest>)

Author: WorkOS

Published: 2026-10-16T15:19:21Z

Content type: news

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [axios supply chain attack](<https://devfeed.tech/topics/axios-supply-chain-attack.md>), [axios npm attack](<https://devfeed.tech/topics/axios-npm-attack.md>), [npm security](<https://devfeed.tech/topics/npm-security.md>), [trust](<https://devfeed.tech/topics/trust.md>), [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [attack](<https://devfeed.tech/tags/attack.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [class](<https://devfeed.tech/tags/class.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [github](<https://devfeed.tech/tags/github.md>), [npm-trusted-publishing](<https://devfeed.tech/tags/npm-trusted-publishing.md>)

## AI overview

The article describes SlugFest, a flaw in npm Trusted Publishing that tied publishing authorization to a GitHub repository's changeable owner/repository name rather than its immutable ID. Bloom Security found more than 1,500 exposed packages, and the article explains the attack path, npm's subsequent validation changes, recommended audits, and the broader risk of using mutable names as authorization identities.

## Source excerpt

npm keyed publishing trust on a renameable owner/repo name instead of GitHub's immutable repository ID, exposing 1,500+ packages. The bug, the fix, and the same mistake in your own authorization code.