VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

n158: vulnerability history, versions and safety

n158 is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 1 release, from May 2023 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 H1
i
2 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 30 Jul 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all n158 vulnerabilities

Vulert verdict on n158 0.0.1-security i

Updated on 23 Oct 2026

Careful: 0.0.1-security was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Not enough data

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

What to do: Do not resolve 0.0.1-security as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 0.0.1-security — affected i
  • Vulnerabilities on record 2 over 3 years · 1 in the last year i
  • Latest disclosure 30 Jul 2026 i
  • Highest CVSS 7.8 i
  • With no published fix 2 i
  • Malicious packages 1 i
  • Last release 2 months ago 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 n158, 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.0.1-security 30 Jul 2026 C1 H1 malicious — No Details →

All 1 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for n158

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-26127: Command Injection in n158 Package 7.8 high No fix published 27 May 2023
Critical Malicious Code Vulnerability in n158 Package N/A critical No fix published 30 Jul 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 n158

Is n158 safe to use?

Vulert records 2 vulnerabilities for n158 in npm: 1 critical, 1 high, 0 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is n158's Vulert package health score?

Vulert scores n158 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 n158 affected?

Yes. 0.0.1-security, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does n158 have?

2 vulnerabilities are recorded for n158 in the npm ecosystem: 1 critical, 1 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 n158 vulnerabilities disclosed?

1 vulnerability was recorded for n158 in the last 12 months, and the oldest entry in this database dates to 27 May 2023. 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 n158 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 n158 for upcoming vulnerabilities?

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