Critical Malicious Code Vulnerability in kill-port Package

kill-port Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191116: Malicious code in kill-port (npm). Affects kill-port versions 2.0.2 – 2.0.3. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The kill-port package is a Node.js utility designed to terminate processes that are using specific ports. It is commonly used in development environments to free up ports for applications. However, this package has been compromised, leading to severe security risks for users who have it installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the kill-port package, specifically in versions 2.0.2 and 2.0.3. This malicious code can fully compromise any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has inserted harmful code into the package, which can lead to significant security breaches.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall kill-port

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, users can temporarily use alternative methods to free up ports, such as manually terminating processes using system tools or other trusted packages that do not have known vulnerabilities.

Conclusion

The kill-port package has been compromised with malicious code, posing a significant risk to users. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for kill-port →

Share this vulnerability

FAQ

You should immediately remove the kill-port package and rotate any sensitive information stored on your computer.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

Failing to address this vulnerability could lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just your package-lock.json file.

It is advisable to avoid using the kill-port package until a verified and secure version is released.

Related vulnerabilities

Recent vulnerabilities recorded for kill-port.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall kill-port

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

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 →
Help improve this record
Report an issue or send feedback