Critical Malicious Code Vulnerability in vscode-kubernetes-tools Package
Summary
MAL-2025-6779: Malicious code in vscode-kubernetes-tools (npm). Affects vscode-kubernetes-tools versions >= 1.4.0. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The vscode-kubernetes-tools package is a popular npm library designed to enhance the development experience for Kubernetes users by providing tools and integrations within Visual Studio Code. It offers features such as cluster management, resource editing, and deployment capabilities. However, this package has been identified to communicate with a domain associated with malicious activity, raising significant security concerns for users relying on it for their development workflows.
Vulnerability Detail
The vulnerability identified as MAL-2025-6779 originates from version 1.4.0 of the vscode-kubernetes-tools package. It involves the package's communication with a domain linked to malicious activities, which could potentially lead to data breaches, unauthorized access, or other harmful consequences for users. This vulnerability poses a risk to the integrity and security of applications utilizing this package, making it imperative for developers to address it promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vscode-kubernetes-toolsIf 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 temporary measure, users can avoid using the affected version of the package (1.4.0 and above) until a patch is applied. Consider using an earlier version of the package that does not exhibit this vulnerability, or explore alternative packages that provide similar functionality without the associated risks.
Conclusion
The vscode-kubernetes-tools package has a critical vulnerability that allows communication with a malicious domain, posing risks to users. It is essential to update the package to a secure version and consider using tools like Vulert for ongoing vulnerability monitoring. By taking these steps, developers can protect their applications and maintain a secure development environment.
See every vulnerability recorded for vscode-kubernetes-tools →
FAQ
The vulnerability involves the package communicating with a domain associated with malicious activity, which could compromise user data and application security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can provide real-time alerts without requiring code access.
Update the vscode-kubernetes-tools package to the latest patched version using the command 'npm update vscode-kubernetes-tools' and monitor your dependencies for vulnerabilities regularly.
Yes, you can avoid using version 1.4.0 and above of the vscode-kubernetes-tools package until a patch is available, or consider using alternative packages.
Detailed information can be found on the GitHub repository of the malicious packages project, which documents vulnerabilities like MAL-2025-6779.
