Malicious Code Injection in xaver-sate44-riris: A Threat to npm Ecosystem
Summary
MAL-2025-92411: Malicious code in xaver-sate44-riris (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 package xaver-sate44-riris is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often include scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in xaver-sate44-riris stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to create derivative packages that pollute the npm registry, making it difficult for developers to trust the integrity of packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-sate44-riris
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 workaround, you can avoid using the xaver-sate44-riris package and monitor your project for any dependencies that may indirectly include it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The xaver-sate44-riris package poses a significant risk due to its malicious code that manipulates package metadata. It is crucial for developers to be aware of this vulnerability and take immediate action to remove the package from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for xaver-sate44-riris →
FAQ
xaver-sate44-riris is an npm package that is part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages and potentially exposing your project to further malicious code.
You should uninstall the xaver-sate44-riris package immediately using the command: npm uninstall xaver-sate44-riris.
You can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without needing to access the code or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.