Malicious Code Injection in veylatea Package - npm Vulnerability
Summary
MAL-2025-91761: Malicious code in veylatea (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 veylatea package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the veylatea package arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially affecting other developers and applications relying on npm packages. The origin of this vulnerability is linked to a campaign aimed at exploiting the npm ecosystem for token rewards, making it a significant concern for developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall veylateaIf 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 veylatea package and check your package-lock.json file for any dependencies that might be affected by this vulnerability. If you are using Vulert, you can monitor your project for vulnerabilities in real-time without needing to access the code directly.
Conclusion
The veylatea package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security and integrity of their projects.
See every vulnerability recorded for veylatea →
FAQ
The veylatea package is an npm package associated with a token reward campaign, designed to generate and publish derivative packages automatically.
The vulnerability can lead to the pollution of the npm registry, affecting the integrity of packages you may depend on and potentially compromising your project's security.
You should uninstall the veylatea package immediately using the command npm uninstall veylatea and review your dependencies for any other potential vulnerabilities.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by simply using your package-lock.json file.
You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without any signup.
