Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 10.0amended

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

CVE-2026-46412GHSA-6xwp-cp5h-q856

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @beproduct/nestjs-auth

    Affected
    >= 0.1.2, <= 0.1.19
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2026-46412: 0.77% estimated exploitation activity in the next 30 days; percentile 55.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 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 - Other secrets present in environment variables Exfiltration target:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-6xwp-cp5h-q856

  2. Revision 2 · amended ·

    Amended from osv record GHSA-6xwp-cp5h-q856

  3. Revision 1 · created ·

    Published from ghsa record GHSA-6xwp-cp5h-q856

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46412

Advisory: Malicious code in @beproduct/nestjs-auth (0.1.2 through 0.1.19) — Mini Shai-Hulud worm
IDs: CVE-2026-46412, GHSA-6xwp-cp5h-q856
Record: https://patchnext.com/advisories/cve-2026-46412 (revision 3, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @beproduct/nestjs-auth: affected >= 0.1.2, <= 0.1.19

## Suggested inspection (read-only)
- `npm ls @beproduct/nestjs-auth --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @beproduct/nestjs-auth.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6xwp-cp5h-q856 (GitHub-reviewed advisory GHSA-6xwp-cp5h-q856 lists affected ranges: npm @beproduct/nestjs-auth >=0.1.2 <=0.1.19)
- Verified: https://osv.dev/vulnerability/GHSA-6xwp-cp5h-q856 (OSV record GHSA-6xwp-cp5h-q856 lists affected ranges: npm @beproduct/nestjs-auth >=0.1.2 <=0.1.19)

Commands are suggestions: review each one before running it.

Loading voting…