VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@nx/node: vulnerability history, versions and safety

@nx/node is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @nx/node vulnerabilities

Vulert verdict on @nx/node 24.0.0 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @nx/node is a malicious-package vulnerability — a published version contained hostile code rather than a bug. Do not install it, and check whether it is already resolved in your dependencies.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release contains malicious code, which caps this score.

What to do: Do not install this package. If it is already in your dependency tree, remove or replace it, and check what resolved it in the first place. Vulert keeps watching the name: if a maintained replacement appears, you will see it here. Monitor it with Vulert →

  • Current release 24.0.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 27 Aug 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Depended on by 5 packages i
  • Stars 29,415 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @nx/node, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
24.0.0-canary.20261022-d90f061 22 Oct 2026 C1 malicious MIT No Details →
24.0.0 21 Oct 2026 C1 malicious MIT No Details →
24.0.0-canary.20261021-b84b2a4 21 Oct 2026 C1 malicious MIT No Details →
24.0.0-rc.1 21 Oct 2026 C1 malicious MIT No Details →
24.0.0-rc.0 21 Oct 2026 C1 malicious MIT No Details →
24.0.0-canary.20261020-e7ffd79 20 Oct 2026 C1 malicious MIT No Details →
24.0.0-canary.20261019-c4bb923 19 Oct 2026 C1 malicious MIT No Details →
24.0.0-beta.4 19 Oct 2026 C1 malicious MIT No Details →
24.0.0-beta.3 18 Oct 2026 C1 malicious MIT No Details →
24.0.0-canary.20261016-5ef7804 16 Oct 2026 C1 malicious MIT No Details →
24.0.0-beta.2 14 Oct 2026 C1 malicious MIT No Details →
24.0.0-pr.37405.acdaf31 14 Oct 2026 C1 malicious MIT No Details →
24.0.0-canary.20261013-994ecba 13 Oct 2026 C1 malicious MIT No Details →
24.0.0-beta.1 13 Oct 2026 C1 malicious MIT No Details →
24.0.0-beta.0 13 Oct 2026 C1 malicious MIT No Details →
23.3.0 07 Oct 2026 C1 malicious MIT No Details →
23.3.0-rc.1 07 Oct 2026 C1 malicious MIT No Details →
23.3.0-canary.20261007-e09f772 07 Oct 2026 C1 malicious MIT No Details →
23.3.0-rc.0 06 Oct 2026 C1 malicious MIT No Details →
23.3.0-pr.37224.268062c 06 Oct 2026 C1 malicious MIT No Details →
23.3.0-beta.9 03 Oct 2026 C1 malicious MIT No Details →
23.3.0-beta.8 02 Oct 2026 C1 malicious MIT No Details →
23.3.0-canary.20261001-d5b5b55 01 Oct 2026 C1 malicious MIT No Details →
23.3.0-canary.20260930-70dab9e 30 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260929-b8beaaa 29 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260928-ff94a98 28 Sep 2026 C1 malicious MIT No Details →
23.3.0-beta.7 28 Sep 2026 C1 malicious MIT No Details →
23.3.0-beta.6 26 Sep 2026 C1 malicious MIT No Details →
23.3.0-pr.37036.f6e3fb2 24 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260924-5d445e3 24 Sep 2026 C1 malicious MIT No Details →
23.3.0-beta.5 23 Sep 2026 C1 malicious MIT No Details →
23.3.0-pr.37036.2b7abf9 23 Sep 2026 C1 malicious MIT No Details →
23.3.0-beta.4 22 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260922-cf6d9f0 22 Sep 2026 C1 malicious MIT No Details →
23.3.0-beta.3 22 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260921-685cbff 21 Sep 2026 C1 malicious MIT No Details →
23.3.0-beta.2 21 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260918-027a0b0 18 Sep 2026 C1 malicious MIT No Details →
23.3.0-beta.1 17 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260917-ea5c01d 17 Sep 2026 C1 malicious MIT No Details →
23.3.0-pr.37068.f95e11e 16 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260915-071d621 15 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260914-69b08a6 14 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260911-50efd6a 11 Sep 2026 C1 malicious MIT No Details →
22.7.12 10 Sep 2026 C1 malicious MIT No Details →
23.3.0-pr.36958.5270397 09 Sep 2026 C1 malicious MIT No Details →
22.7.11 09 Sep 2026 C1 malicious MIT No Details →
23.2.1 09 Sep 2026 C1 malicious MIT No Details →
23.3.0-canary.20260909-359c09a 09 Sep 2026 C1 malicious MIT No Details →
23.3.0-pr.36841.f66e88b 09 Sep 2026 C1 malicious MIT No Details →
22.7.10 09 Sep 2026 C1 malicious MIT No Details →
23.3.0-beta.0 08 Sep 2026 C1 malicious MIT No Details →
23.2.0-canary.20260908-89f02c1 08 Sep 2026 C1 malicious MIT No Details →
23.2.0-canary.20260902-6e38e5e 02 Sep 2026 C1 malicious MIT No Details →
23.2.0 02 Sep 2026 C1 malicious MIT No Details →
23.2.0-rc.2 01 Sep 2026 C1 malicious MIT No Details →
22.7.9 01 Sep 2026 C1 malicious MIT No Details →
23.2.0-rc.1 01 Sep 2026 C1 malicious MIT No Details →
23.1.3 31 Aug 2026 C1 malicious MIT No Details →
23.2.0-rc.0 31 Aug 2026 C1 malicious MIT No Details →
23.2.0-pr.36866.449f6f3 31 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260831-0afbe76 31 Aug 2026 C1 malicious MIT No Details →
23.2.0-beta.12 31 Aug 2026 C1 malicious MIT No Details →
23.2.0-pr.36838.ef8e258 31 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260827-d05d38d 27 Aug 2026 C1 malicious MIT No Details →
23.2.0-beta.11 27 Aug 2026 C1 malicious MIT No Details →
23.1.2 26 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260826-b7682e7 26 Aug 2026 C1 malicious MIT No Details →
23.2.0-beta.10 26 Aug 2026 C1 malicious MIT No Details →
23.2.0-pr.36527.2252709 24 Aug 2026 C1 malicious MIT No Details →
23.2.0-beta.9 21 Aug 2026 C1 malicious MIT No Details →
23.2.0-beta.8 21 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260820-c75960a 20 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260814-d9c21b2 14 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260811-bc454cf 11 Aug 2026 C1 malicious MIT No Details →
23.2.0-beta.7 11 Aug 2026 C1 malicious MIT No Details →
23.2.0-beta.6 11 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260810-f8dee87 10 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260807-3298fd8 07 Aug 2026 C1 malicious MIT No Details →
23.2.0-beta.5 07 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260804-c3b7f1e 04 Aug 2026 C1 malicious MIT No Details →
23.2.0-canary.20260731-0634da3 31 Jul 2026 C1 malicious MIT No Details →
22.7.8 30 Jul 2026 C1 malicious MIT No Details →
23.1.1 30 Jul 2026 C1 malicious MIT No Details →
23.2.0-canary.20260730-c654db8 30 Jul 2026 C1 malicious MIT No Details →
23.2.0-beta.4 30 Jul 2026 C1 malicious MIT No Details →
23.2.0-canary.20260729-e3e16e9 29 Jul 2026 C1 malicious MIT No Details →
23.2.0-beta.3 29 Jul 2026 C1 malicious MIT No Details →
23.2.0-canary.20260728-26fd7d9 28 Jul 2026 C1 malicious MIT No Details →
23.2.0-canary.20260724-9c735d4 24 Jul 2026 C1 malicious MIT No Details →
23.2.0-beta.2 22 Jul 2026 C1 malicious MIT No Details →
23.2.0-canary.20260722-6a072a2 22 Jul 2026 C1 malicious MIT No Details →
23.2.0-canary.20260720-beb379f 20 Jul 2026 C1 malicious MIT No Details →
23.2.0-beta.1 20 Jul 2026 C1 malicious MIT No Details →
23.2.0-canary.20260717-dc22f7e 17 Jul 2026 C1 malicious MIT No Details →
23.2.0-beta.0 17 Jul 2026 C1 malicious MIT No Details →
23.1.0-canary.20260717-ee5de80 17 Jul 2026 C1 malicious MIT No Details →
23.1.0-canary.20260714-6d65703 14 Jul 2026 C1 malicious MIT No Details →
23.1.0 13 Jul 2026 C1 malicious MIT No Details →
23.1.0-canary.20260713-a5b10cd 13 Jul 2026 C1 malicious MIT No Details →
23.1.0-rc.3 13 Jul 2026 C1 malicious — No Details →
22.7.7 11 Jul 2026 C1 malicious — No Details →
23.1.0-canary.20260710-54c52e3 10 Jul 2026 C1 malicious — No Details →
23.0.2 10 Jul 2026 C1 malicious — No Details →
23.1.0-rc.2 09 Jul 2026 C1 malicious — No Details →
23.1.0-rc.1 09 Jul 2026 C1 malicious — No Details →
23.1.0-pr.36263.fac529b 09 Jul 2026 C1 malicious — No Details →
23.1.0-canary.20260709-b95c507 09 Jul 2026 C1 malicious — No Details →
23.1.0-canary.20260708-cbc390b 08 Jul 2026 C1 malicious — No Details →
23.1.0-rc.0 07 Jul 2026 C1 malicious — No Details →
23.1.0-canary.20260706-71a511d 06 Jul 2026 C1 malicious — No Details →
23.1.0-beta.7 03 Jul 2026 C1 malicious — No Details →
23.1.0-canary.20260703-5c65c68 03 Jul 2026 C1 malicious — No Details →
23.1.0-canary.20260702-bdb703a 02 Jul 2026 C1 malicious — No Details →
23.1.0-beta.6 02 Jul 2026 C1 malicious — No Details →
23.1.0-beta.5 30 Jun 2026 C1 malicious — No Details →
23.1.0-canary.20260630-d5821e2 30 Jun 2026 C1 malicious — No Details →
23.1.0-pr.36127.e594f53 29 Jun 2026 C1 malicious — No Details →
23.1.0-pr.36127.5a31f69 29 Jun 2026 C1 malicious — No Details →
23.1.0-pr.36127.8b9019b 26 Jun 2026 C1 malicious — No Details →

The newest 120 of 1,953 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @nx/node

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Vulnerability in @nx/node: Code Injection and NPM Token Theft N/A critical No fix published 27 Aug 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @nx/node

Is @nx/node safe to use?

No. Vulert records a malicious-package vulnerability for @nx/node: a published version contained hostile code rather than a bug, and the package looks like one that was withdrawn for abuse. Do not install it, and check whether it is already resolved in your dependencies.

What is @nx/node's Vulert package health score?

Vulert scores @nx/node 15/100, which reads as critical. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release contains malicious code, which caps this score.

Is the latest version of @nx/node affected?

Yes. 24.0.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does @nx/node have?

1 vulnerability is recorded for @nx/node in the npm ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @nx/node vulnerabilities disclosed?

0 vulnerabilities were recorded for @nx/node in the last 12 months, and the oldest entry in this database dates to 27 Aug 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @nx/node are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor @nx/node for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @nx/node version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.