Malicious Code Injection in vayzave: A Threat to npm Ecosystem
Summary
MAL-2025-110377: Malicious code in vayzave (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 vayzave package is part of the npm ecosystem, which is a popular platform for JavaScript package management. It is often used by developers to share and reuse code. However, vayzave has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in the vayzave package originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The malicious code embedded in vayzave modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also inflates developer reputation scores fraudulently, potentially compromising the security of applications that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vayzaveIf 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 avoid using the vayzave package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The vayzave package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Regular audits and the use of monitoring tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for vayzave →
FAQ
The vayzave package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The malicious code can lead to the modification of your package.json file, potentially compromising your application's integrity and security.
You should uninstall the vayzave package immediately and check your package-lock.json file for any references to it.
You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
