Critical Malicious Code Vulnerability in @kvytech/habbit-e2e-test Package
Summary
MAL-2025-191239: Malicious code in @kvytech/habbit-e2e-test (npm). Affects @kvytech/habbit-e2e-test versions 0.0.2. 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 @kvytech/habbit-e2e-test package is an npm package designed for end-to-end testing in JavaScript applications. It provides tools and utilities to facilitate automated testing processes. However, this package has been compromised, making it a significant security risk for any application utilizing it.
Vulnerability Detail
The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials from the user's environment and publish them to GitHub. It can also propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. The malicious payload may even lead to the destruction of the user's home directory, making it critical to address this issue immediately.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @kvytech/habbit-e2e-testIf 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 workaround, consider using an alternative package for end-to-end testing until the vulnerability is resolved. Ensure that any sensitive information is not stored on the affected machine.
Conclusion
The @kvytech/habbit-e2e-test package has been compromised, posing a severe risk to users. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies is crucial to prevent future vulnerabilities.
See every vulnerability recorded for @kvytech/habbit-e2e-test →
FAQ
Immediately uninstall the package and rotate all secrets and keys stored on the affected machine.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
The malicious code can steal sensitive tokens and credentials, potentially leading to unauthorized access to your systems and data loss.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
The vulnerability originated from a malicious npm worm known as Sha1-Hulud: The Second Coming, which compromised the package.
