Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-46412 — nestjs-auth

🔴 CVSS 10.0 — Critical ✅ No Known Exploit CWE-506 NVD
10.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

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](https://www.aikido.dev/blog/mini-shai-hulud-is-back-tanstack-compromised).

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: https://filev2.getsession.org. The worm also wrote persistence artefacts (tanstack_runner.js, router_init.js, setup.mjs, plus IDE-hook configurations in .claude/ and .vscode/) into the developer's working tree where the malicious install ran.

Indicators of compromise

| Type | Value |

|---|---|

| File name (payload) | tanstack_runner.js, router_init.js, router_runtime.js |

| SHA-256 (tanstack_runner.js) | 2ec78d556d696e208927cc503d48e4b5eb56b31abc2870c2ed2e98d6be27fc96 |

| SHA-256 (router_init.js) | ab4fcadaec49c03278063dd269ea5eef82d24f2124a8e15d7b90f2fa8601266c |

| Exfil endpoint | filev2.getsession.org |

| Cloud metadata probe | 169.254.169.254/latest/meta-data/iam/security-credentials/ |

| npm token endpoint | registry.npmjs.org/-/npm/v1/tokens |

| Vault probe | vault.svc.cluster.local:8200 |

| IDE hook pattern | .claude/settings.json SessionStart hook + .vscode/tasks.json runOn: "folderOpen" running node .claude/setup.mjs or node .vscode/setup.mjs |

Mitigation

If you installed any version in the range >=0.1.2 <=0.1.19:

1. Remove the package and clean the npm cache:

```bash

npm uninstall @beproduct/nestjs-auth

npm cache clean --force

```

2. Install the clean version:

```bash

npm install @beproduct/[email protected]

```

3. Rotate every credential present in the install environment, including:

  • All npm publish tokens (https://www.npmjs.com/settings/<you>/tokens)
  • All GitHub PATs and OAuth tokens (https://github.com/settings/applications + https://github.com/settings/tokens)
  • AWS access keys
  • HashiCorp Vault tokens
  • Any other secret that was in env vars or config files at install time

4. Scan affected hosts for the indicators of compromise above. If any are found, treat the host as compromised and reimage.

5. 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.

Timeline (UTC)

| Time | Event |

|---|---|

| 2026-05-11 20:19:43 | First malicious version (0.1.2) published |

| 2026-05-11 22:56:39 | Final malicious version (0.1.19) published — 18 versions in 2h37m |

| 2026-05-12 ~14:12 | npm Security removes the malicious versions from the registry |

| 2026-05-13 | BeProduct discovers the incident via Aikido's public disclosure |

| 2026-05-14 | Compromised npm publish token revoked; BeProduct GitHub OAuth credentials rotated |

| 2026-05-14 | Clean release 0.1.20 published; this advisory filed |

Root cause

The compromised npm publish token was harvested by a Mini-Shai-Hulud-infected transitive dependency in an automated GitHub coding-agent runtime that had read access to the NPM_TOKEN GitHub Actions secret for an unrelated repository under the same npm publisher account. The publish itself was performed by the attacker against the public npm registry; the source repository for this package was not modified by the attacker.

References

  • https://www.aikido.dev/blog/mini-shai-hulud-is-back-tanstack-compromised
  • https://www.aikido.dev/blog/checklist-github-actions

```

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Changed — a successful attack reaches components beyond the vulnerable one.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-46412 is classified as CWE-506: Embedded Malicious Code. The product contains code that appears to be malicious in nature.

Affected software

CVE-2026-46412 is recorded against 2 packages.

  • @beproduct/nestjs-auth
  • unknown

Timeline and source

Published on 19 May 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Web)
github.com (Package)
www.aikido.dev (Web)
www.aikido.dev (Web)

Other advisories for this package

@beproduct/nestjs-auth has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-506: Embedded Malicious Code) in other software:

Details

Severity CRITICAL
CVSS Score 10.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CWE CWE-506
Public Exploit ✅ No
Source NVD
Published 2026-05-19
Updated 2026-08-20
Modified 2026-05-19
Fix URL N/A

Affected Packages

Software From version Fixed in
@beproduct/nestjs-auth
unknown

Similar Threats

Exploit Protection

Are you running nestjs-auth?

CVE-2026-46412 carries CVSS 10.0 Critical rating. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2026-46412 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026