Malicious Code Injection in xaver-lapis34-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-111063: Malicious code in xaver-lapis34-ruro (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package xaver-lapis34-ruro is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in xaver-lapis34-ruro stems from its inclusion in a malicious campaign that deploys autopublish scripts. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward scheme, which incentivizes such malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-lapis34-ruroIf 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-lapis34-ruro package and any other packages that may be part of the tea.xyz token reward campaign. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The xaver-lapis34-ruro package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and take necessary actions to mitigate the risks associated with this vulnerability. Regular updates and monitoring can help maintain the security of your projects.
See every vulnerability recorded for xaver-lapis34-ruro →
FAQ
xaver-lapis34-ruro is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and affecting your application's security.
You should remove the xaver-lapis34-ruro package from your project and monitor for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just the 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 requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
