Critical Malicious Code Vulnerability in @hypervector/hypervector-test Package
Summary
MAL-2025-6352: Malicious code in @hypervector/hypervector-test (npm). Affected versions are not published. 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 @hypervector/hypervector-test package is an npm library designed for testing purposes within the Hypervector ecosystem. It provides functionalities that facilitate the development and testing of applications. However, this package has been identified to contain malicious code, posing significant security risks to systems that utilize it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the @hypervector/hypervector-test package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information, including secrets and keys. The origin of this vulnerability is linked to the package's malicious intent, as indicated by its classification under CWE-506, which denotes embedded malicious code. The ramifications of this vulnerability are severe, as it can lead to full system compromise.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @hypervector/hypervector-test
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 temporary measure, you can prevent the execution of the malicious code by isolating the environment where the package is used. However, the safest approach is to remove the package entirely from your project.
Conclusion
The @hypervector/hypervector-test package contains malicious code that poses a significant security threat. Immediate action is required to remove the package and secure any compromised information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for @hypervector/hypervector-test →
FAQ
Immediately remove the package from your system and rotate any sensitive information that may have been compromised.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
The risks include unauthorized access to sensitive data, potential system compromise, and the possibility of further malicious activities on your system.
Currently, the best course of action is to remove the package. Keep an eye on updates from the package maintainers for any patched versions.
Regularly audit your dependencies, utilize tools like Vulert for monitoring, and stay informed about security advisories related to the packages you use.