VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@nubjs/types: vulnerability history, versions and safety

@nubjs/types is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Sep 2026. 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
1 in the last 12 months

Most recent disclosure 25 Sep 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @nubjs/types vulnerabilities

Vulert verdict on @nubjs/types 0.9.7 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @nubjs/types 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 Little adoption
  • Community Not enough data

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 0.9.7 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 25 Sep 2026 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 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 @nubjs/types, 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
0.9.7 19 Oct 2026 C1 malicious MIT No Details →
0.9.6 01 Oct 2026 C1 malicious MIT No Details →
0.9.5 25 Sep 2026 C1 malicious MIT No Details →
0.9.3-canary.20260920.524 20 Sep 2026 C1 malicious MIT No Details →
0.9.3 19 Sep 2026 C1 malicious MIT No Details →
0.9.2-canary.20260916.519 16 Sep 2026 C1 malicious MIT No Details →
0.9.2-canary.20260914.518 15 Sep 2026 C1 malicious MIT No Details →
0.9.2-canary.20260914.517 14 Sep 2026 C1 malicious MIT No Details →
0.9.2 13 Sep 2026 C1 malicious MIT No Details →
0.9.1-canary.20260912.514 13 Sep 2026 C1 malicious MIT No Details →
0.9.1 12 Sep 2026 C1 malicious MIT No Details →
0.9.0-canary.20260912.512 12 Sep 2026 C1 malicious MIT No Details →
0.9.0-canary.20260910.511 11 Sep 2026 C1 malicious MIT No Details →
0.9.0-canary.20260910.510 10 Sep 2026 C1 malicious MIT No Details →
0.9.0-canary.20260909.509 09 Sep 2026 C1 malicious MIT No Details →
0.9.0-canary.20260908.508 08 Sep 2026 C1 malicious MIT No Details →
0.9.0 07 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260907.506 07 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260906.505 06 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260904.503 04 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260904.502 04 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260904.498 04 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260904.493 04 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260904.491 04 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260904.490 04 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260904.481 04 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260904.476 04 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260903.456 03 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260903.450 03 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260903.448 03 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260903.446 03 Sep 2026 C1 malicious MIT No Details →
0.8.3-canary.20260903.442 03 Sep 2026 C1 malicious MIT No Details →
0.8.3 03 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260902.438 03 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260902.437 03 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260902.433 02 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260902.432 02 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260902.430 02 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260902.428 02 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260902.427 02 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260901.425 02 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260901.424 01 Sep 2026 C1 malicious MIT No Details →
0.8.2-canary.20260901.423 01 Sep 2026 C1 malicious MIT No Details →
0.8.2 01 Sep 2026 C1 malicious MIT No Details →
0.8.1-canary.20260901.420 01 Sep 2026 C1 malicious MIT No Details →
0.8.1-canary.20260831.417 01 Sep 2026 C1 malicious MIT No Details →
0.8.1-canary.20260831.410 31 Aug 2026 C1 malicious MIT No Details →
0.8.1 29 Aug 2026 C1 malicious MIT No Details →
0.8.0-canary.20260829.402 29 Aug 2026 C1 malicious MIT No Details →
0.8.0-canary.20260829.400 29 Aug 2026 C1 malicious MIT No Details →
0.8.0-canary.20260829.399 29 Aug 2026 C1 malicious MIT No Details →
0.8.0-canary.20260829.396 29 Aug 2026 C1 malicious MIT No Details →
0.8.0-canary.20260828.394 28 Aug 2026 C1 malicious MIT No Details →
0.8.0-canary.20260828.380 28 Aug 2026 C1 malicious MIT No Details →
0.8.0-canary.20260828.374 28 Aug 2026 C1 malicious MIT No Details →
0.8.0 28 Aug 2026 C1 malicious MIT No Details →
0.8.0-canary.20260827.370 27 Aug 2026 C1 malicious MIT No Details →
0.7.5-canary.20260814.317 14 Aug 2026 C1 malicious MIT No Details →
0.7.5-canary.20260814.315 14 Aug 2026 C1 malicious MIT No Details →
0.7.5-canary.20260812.313 12 Aug 2026 C1 malicious MIT No Details →
0.7.5-canary.20260811.311 12 Aug 2026 C1 malicious MIT No Details →
0.7.5-canary.20260811.310 12 Aug 2026 C1 malicious MIT No Details →
0.7.5-canary.20260811.309 11 Aug 2026 C1 malicious MIT No Details →
0.7.5-canary.20260811.305 11 Aug 2026 C1 malicious MIT No Details →
0.7.5-canary.20260811.304 11 Aug 2026 C1 malicious MIT No Details →
0.7.5 09 Aug 2026 C1 malicious MIT No Details →
0.7.4-canary.20260809.297 09 Aug 2026 C1 malicious MIT No Details →
0.7.4-canary.20260808.295 08 Aug 2026 C1 malicious MIT No Details →
0.7.4 08 Aug 2026 C1 malicious MIT No Details →
0.7.3-canary.20260808.283 08 Aug 2026 C1 malicious MIT No Details →
0.7.3-canary.20260808.281 08 Aug 2026 C1 malicious MIT No Details →
0.7.3 08 Aug 2026 C1 malicious MIT No Details →
0.7.2-canary.20260808.271 08 Aug 2026 C1 malicious MIT No Details →
0.7.2-canary.20260807.264 08 Aug 2026 C1 malicious MIT No Details →
0.7.2-canary.20260807.261 07 Aug 2026 C1 malicious MIT No Details →
0.7.2-canary.20260807.259 07 Aug 2026 C1 malicious MIT No Details →
0.7.2 07 Aug 2026 C1 malicious MIT No Details →
0.7.1-canary.20260806.253 06 Aug 2026 C1 malicious MIT No Details →
0.7.1-canary.20260806.252 06 Aug 2026 C1 malicious MIT No Details →
0.7.1-canary.20260806.251 06 Aug 2026 C1 malicious MIT No Details →
0.7.1-canary.20260806.249 06 Aug 2026 C1 malicious MIT No Details →
0.7.1-canary.20260806.248 06 Aug 2026 C1 malicious MIT No Details →
0.7.1 05 Aug 2026 C1 malicious MIT No Details →
0.7.0-canary.20260805.239 05 Aug 2026 C1 malicious MIT No Details →
0.7.0-canary.20260805.232 05 Aug 2026 C1 malicious MIT No Details →
0.7.0 05 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260805.225 05 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260804.220 04 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260804.218 04 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260803.216 04 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260803.215 03 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260803.208 03 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260803.207 03 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260803.205 03 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260803.198 03 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260802.194 02 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260802.187 02 Aug 2026 C1 malicious MIT No Details →
0.6.0-canary.20260729.137 29 Jul 2026 C1 malicious MIT No Details →
0.6.0-canary.20260729.131 29 Jul 2026 C1 malicious MIT No Details →
0.6.0-canary.20260729.129 29 Jul 2026 C1 malicious MIT No Details →
0.6.0-canary.20260729.123 29 Jul 2026 C1 malicious — No Details →
0.6.0-canary.20260729.121 29 Jul 2026 C1 malicious — No Details →
0.6.0-canary.20260729.120 29 Jul 2026 C1 malicious — No Details →
0.6.0-canary.20260729.118 29 Jul 2026 C1 malicious — No Details →
0.6.0-canary.20260729.114 29 Jul 2026 C1 malicious — No Details →
0.6.0-canary.20260729.110 29 Jul 2026 C1 malicious — No Details →
0.6.0-canary.20260728.108 28 Jul 2026 C1 malicious — No Details →
0.6.0-canary.20260728.107 28 Jul 2026 C1 malicious — No Details →
0.6.0-canary.20260728.105 28 Jul 2026 C1 malicious — No Details →
0.6.0-canary.20260727.102 27 Jul 2026 C1 malicious — No Details →
0.6.0 25 Jul 2026 C1 malicious — No Details →
0.5.0-canary.20260725.97 25 Jul 2026 C1 malicious — No Details →
0.5.0-canary.20260725.96 25 Jul 2026 C1 malicious — No Details →
0.5.0-canary.20260725.95 25 Jul 2026 C1 malicious — No Details →
0.5.0 22 Jul 2026 C1 malicious — No Details →
0.4.13 15 Jul 2026 C1 malicious — No Details →
0.4.12 15 Jul 2026 C1 malicious — No Details →
0.4.11 12 Jul 2026 C1 malicious — No Details →
0.4.10 12 Jul 2026 C1 malicious — No Details →
0.4.9 12 Jul 2026 C1 malicious — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for @nubjs/types

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Malicious Code Vulnerability in @nubjs/types Package N/A critical No fix published 25 Sep 2026

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 @nubjs/types

Is @nubjs/types safe to use?

No. Vulert records a malicious-package vulnerability for @nubjs/types: 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 @nubjs/types's Vulert package health score?

Vulert scores @nubjs/types 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 @nubjs/types affected?

Yes. 0.9.7, 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 @nubjs/types have?

1 vulnerability is recorded for @nubjs/types 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 @nubjs/types vulnerabilities disclosed?

1 vulnerability was recorded for @nubjs/types in the last 12 months, and the oldest entry in this database dates to 25 Sep 2026. 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 @nubjs/types 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 @nubjs/types for upcoming vulnerabilities?

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