Malicious Code Injection in xaver-sroto61-riris Package: A Threat to npm Users
Summary
MAL-2025-92418: Malicious code in xaver-sroto61-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 xaver-sroto61-riris package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign aimed at exploiting npm's publishing features. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards associated with the tea.xyz protocol.
Vulnerability Detail
The vulnerability stems from the package's malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-sroto61-ririsIf 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, avoid using the xaver-sroto61-riris package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your package-lock.json file to identify and remove any malicious packages.
Conclusion
The xaver-sroto61-riris package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to mitigate the risks associated with this package.
See every vulnerability recorded for xaver-sroto61-riris →
FAQ
It is an npm package identified as part of a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to the inclusion of malicious code in your project, compromising its security and integrity.
You should uninstall the package immediately and check for any dependencies that may rely on it.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
