CVE-2026-46412 Details
Description
@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 <=0.1.19` should remove the package and clean the npm cache; install the clean version; rotate every credential present in the install environment, including all npm publish tokens, all GitHub PATs and OAuth tokens, AWS access keys, HashiCorp Vault tokens, and any other secret that was in env vars or config files at install time; scan affected hosts for indicators of compromise and, if any are found, treat the host as compromised and reimage; and check committed repository history for unexpected additions in `.claude/` or `.vscode/` directories. The worm is known to commit `setup.mjs` + hook configs to PR branches via automated agent runtimes.
A supply chain vulnerability has been identified in the @beproduct/nestjs-auth package, specifically in versions 0.1.2 through 0.1.19. During a brief window on May 11, 2026, an attacker exploited a compromised npm publish token to release 18 malicious versions of the package. These versions included a postinstall payload designed to steal various credentials and secrets from the user's environment, such as npm tokens, GitHub personal access tokens, AWS credentials, and HashiCorp Vault tokens. The stolen information was exfiltrated to an external server, and the malicious code also established persistence by writing files into the developer's working directory. The vulnerability has been linked to the 'Mini Shai-Hulud' npm worm campaign, which targeted other packages in addition to @beproduct/nestjs-auth.
Users should uninstall the @beproduct/nestjs-auth package, clean the npm cache, and then reinstall the package, ensuring to get the clean version 0.1.20. After reinstalling, it is crucial to rotate all credentials that were present in the environment during the installation of the malicious version, including npm tokens, GitHub personal access tokens, AWS credentials, HashiCorp Vault tokens, and any other secrets that were in environment variables or configuration files at that time. Additionally, users should scan their systems for the indicators of compromise associated with this vulnerability, and if any are found, treat the host as compromised and reimage it.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 20, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-506 | Embedded Malicious Code | [email protected] |
Affected Products
No affected product data is available for this CVE.
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 20, 2026 | New CVE Received | [email protected] |
| Jul 20, 2026 | CVE Modified | CISA-ADP |