CVE-2026-46412: Malicious code in @beproduct/nestjs-auth (0.1.2 through 0.1.19) — Mini Shai-Hulud worm

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 0.8%, percentile 55: FIRST’s model estimates a 0.8% chance of exploitation activity in the next 30 days, higher than 55% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes @beproduct/nestjs-auth (npm) >= 0.1.2, <= 0.1.19, no fixed version listed. Check your lockfile, including transitive dependencies.

What it is

@beproduct/nestjs-auth is a NestJS authentication module for BeProduct IDS (Identity Server) with OpenID Connect support. Between 2026-05-11 20:19 UTC and 22:56 UTC, an attacker used a compromised npm publish token to publish 18 malicious versions of @beproduct/nestjs-auth (0.1.2 through 0.1.19). The postinstall payload attempted to harvest npm tokens (from ~/.npmrc); GitHub personal access tokens, OAuth tokens (gho), and Actions OIDC tokens; AWS credentials (from environment variables and ~/.aws/credentials); HashiCorp Vault tokens; and other secrets present in environment variables. Version 0.1.20 is a clean republish from the original 0.1.1 source tree. Anyone who installed any version in the range >=0.1.2

From the GitHub advisory

Summary

Between 2026-05-11 20:19 UTC and 22:56 UTC, an attacker used a compromised npm publish token to publish 18 malicious versions of @beproduct/nestjs-auth (0.1.2 through 0.1.19). The packages contained payloads from the Mini Shai-Hulud npm supply-chain worm campaign described by Aikido Security.

npm Security removed the malicious versions from the registry shortly after publication, but anyone who ran npm install @beproduct/nestjs-auth resolving to any version in the affected range during that window executed the malicious postinstall script and is potentially compromised.

Version 0.1.20 is a clean republish from the original 0.1.1 source tree.

Impact

Weakness type: CWE-506.

Product: @beproduct/nestjs-auth (npm) · Assigned by: GitHub_M · Published: 2026-07-20

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.77% probability of exploitation activity in the next 30 days; percentile 55.

Timeline

• 2026-05-19 — GitHub-reviewed advisory GHSA-6xwp-cp5h-q856 published (critical)
• 2026-07-20 — CVE record last updated
• 2026-07-20 — CVE record published by GitHub_M

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-6xwp-cp5h-q856 github.com
2. CVE.org record CVE-2026-46412 cve.org
3. NVD entry CVE-2026-46412 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. aikido.dev aikido.dev
3. aikido.dev aikido.dev

Critical npm advisories · Today’s Security Digest