Malicious Code Vulnerability in eligible_slug_0xrequest Package
Summary
MAL-2025-102046: Malicious code in eligible_slug_0xrequest (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 eligible_slug_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is aimed at inflating developer reputation scores for token rewards, making the package a potential threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the eligible_slug_0xrequest package originates from its malicious payload, which 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 not only compromises the security of the affected applications but also affects the overall reliability of the npm ecosystem by introducing potentially harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eligible_slug_0xrequestIf 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include eligible_slug_0xrequest in its dependencies.
Conclusion
The eligible_slug_0xrequest package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant and remove any instances of this package from their projects to maintain the security and integrity of their applications.
See every vulnerability recorded for eligible_slug_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the eligible_slug_0xrequest package immediately and monitor your project for any other potentially malicious packages.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
