Malicious Code Injection in xaver-enting68-ruro Package
Summary
MAL-2025-111053: Malicious code in xaver-enting68-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
Background
The xaver-enting68-ruro 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 its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the xaver-enting68-ruro package stems 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 variants, polluting the npm registry and potentially affecting other developers by inflating reputation scores fraudulently. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded npm with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall xaver-enting68-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 workaround, consider using a package-lock.json file to lock your dependencies to known safe versions. This can help prevent the installation of malicious packages. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.
Conclusion
The xaver-enting68-ruro package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your project for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for xaver-enting68-ruro →
FAQ
The xaver-enting68-ruro package is an npm package involved in the tea.xyz token reward campaign, which has been identified as containing malicious code.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to pollution of the npm registry and affect your project's integrity.
You should uninstall the xaver-enting68-ruro package immediately using 'npm uninstall xaver-enting68-ruro' and check for any other affected packages.
You can use Vulert to monitor your project for vulnerabilities by analyzing your package-lock.json file. It provides real-time alerts without requiring code access or installation.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and ensure to keep your packages updated.
