VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

kill-port: vulnerability history, versions and safety

kill-port is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 14 releases, from Mar 2019 to Nov 2025. 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
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 24 Nov 2025.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all kill-port vulnerabilities

Vulert verdict on kill-port 2.0.1 i

Updated on 23 Oct 2026

Careful: 2.0.1 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 Slowing
  • Popularity Widely used
  • Community Inactive

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

What to do: Do not resolve 2.0.1 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 2.0.1 — affected i
  • Vulnerabilities on record 2 over 6 years · 1 in the last year i
  • Latest disclosure 24 Nov 2025 i
  • Highest CVSS 8.1 i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Depended on by 132 packages i
  • Stars 571 i
  • OpenSSF scorecard 1/10 i
  • Last release 52 months ago 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 kill-port, 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
2.0.1 21 Jun 2022 C1 malicious MIT No Details →
2.0.0 15 May 2022 C1 malicious MIT No Details →
1.6.1 15 Jul 2020 C1 malicious MIT No Details →
1.6.0 01 Oct 2019 C1 malicious MIT No Details →
1.5.2 12 Sep 2019 C1 malicious MIT No Details →
1.5.1 01 Jun 2019 C1 malicious MIT No Details →
1.5.0 10 May 2019 C1 malicious MIT No Details →
1.4.0 03 May 2019 C1 malicious MIT No Details →
1.3.2 11 Sep 2018 C1 malicious MIT No Details →
1.3.1 05 Jul 2018 C1 H1 malicious MIT No Details →
1.3.0 02 Jul 2018 C1 H1 malicious MIT No Details →
1.2.0 13 May 2018 C1 H1 malicious MIT No Details →
1.1.0 05 Jan 2018 C1 H1 malicious MIT No Details →
1.0.0 08 Apr 2017 C1 H1 malicious MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2025 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 kill-port

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-5414: Command Injection in kill-port 8.1 high 1.3.2 25 Mar 2019
Critical Malicious Code Vulnerability in kill-port Package N/A critical No fix published 24 Nov 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 kill-port

Is kill-port safe to use?

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

What is kill-port's Vulert package health score?

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

Yes. 2.0.1, 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.

Which version of kill-port should I use?

2.0.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does kill-port have?

2 vulnerabilities are recorded for kill-port 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 kill-port vulnerabilities disclosed?

1 vulnerability was recorded for kill-port in the last 12 months, and the oldest entry in this database dates to 25 Mar 2019. 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 kill-port 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 kill-port for upcoming vulnerabilities?

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