Vulnary
← back to the feed
Critical· 10official fix available

CVE-2026-46412

A malicious version of the @beproduct/nestjs-auth package was published to npm between 20:19 and 22:56 UTC on 2026-05-11. The post‑install script harvested a wide range of credentials from the environment, including npm tokens, GitHub PATs, AWS keys, and Vault tokens. The clean version 0.1.20 was republished from the original source.

publishedJul 20, 2026
last modifiedJul 23, 2026
sourcesNVD
severity · cvss
10
critical · how bad it is
exploitation · epss
<1%
35th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 19, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Developers who installed @beproduct/nestjs-auth versions 0.1.2 through 0.1.19 for use with NestJS and BeProduct IDS.

02

Real-world impact

An attacker who gains access to a system that installed one of the compromised package versions can harvest all secrets present in that environment—npm publish tokens, GitHub personal access tokens, OAuth tokens, AWS access keys, HashiCorp Vault tokens, and any other credentials stored in environment variables or config files—potentially allowing full compromise of the developer’s accounts and infrastructure.

03

Why this severity

The CVSS score of 10 reflects that the vulnerability allows an attacker to fully compromise confidentiality, integrity, and availability of all secrets on the system without any authentication or user interaction, and the impact is complete.

04

What to do about it

official fix available
recommended steps
  1. 01Uninstall any @beproduct/nestjs-auth version 0.1.2–0.1.19.
  2. 02Clear the npm cache with `npm cache clean --force`.
  3. 03Install the clean version 0.1.20 using `npm install @beproduct/nestjs-auth@0.1.20`.
  4. 04Rotate all credentials that may have been exposed (npm tokens, GitHub PATs/OAuth, AWS keys, Vault tokens, etc.).
  5. 05Scan affected hosts for signs of compromise; if found, treat the host as compromised and reimage.
  6. 06Review repository history for unexpected additions in .claude/ or .vscode/ directories.

NVD-referenced vendor advisory

05

Timeline

  1. Jul 20, 2026 · 13d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 20, 2026 · 13d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
  3. Jul 23, 2026 · 10d ago
    Advisory updated
    The NVD record was last revised.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeChanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →