CVE-2026-46412 BeProduct @beproduct/nestjs-auth vulnerability
@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.
Browse npm security risksQuick answer
@beproduct/nestjs-auth should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- >= 0.1.2, <= 0.1.19
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-46412 affects @beproduct/nestjs-auth and involves software supply-chain compromise. Installing an affected package may run malicious code, steal build or developer credentials, and alter source-controlled files. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. Remove affected @beproduct/nestjs-auth versions, clear the npm cache, and install 0.1.20 or later. Rotate every credential exposed to the install environment, review repository history for malicious changes, and reimage hosts with compromise indicators.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses @beproduct/nestjs-auth.
- Compare the installed version with the recorded affected range: >= 0.1.2, <= 0.1.19.
- Remove affected @beproduct/nestjs-auth versions, clear the npm cache, and install 0.1.20 or later. Rotate every credential exposed to the install environment, review repository history for malicious changes, and reimage hosts with compromise indicators.
- Stop installing the affected package range, block it in dependency policy, and isolate build or developer systems that executed it.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to @beproduct/nestjs-auth; remove access that is not required.
- Review package-manager, CI, process, network, credential, and repository history for malicious install activity, secret access, or unexpected file changes.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-46412 in place.
- Use a safe regression test to confirm the affected software supply-chain compromise path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-46412?
@beproduct/nestjs-auth versions listed as affected should be reviewed: >= 0.1.2, <= 0.1.19.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.