Malicious Code Injection in leading_lemming_0xrequest Package
Summary
MAL-2025-105042: Malicious code in leading_lemming_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 leading_lemming_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages. The malicious nature of this package stems from its ability to modify critical files and republish variants, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in leading_lemming_0xrequest originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. The package contains scripts that automatically alter package.json files by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential exploitation of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall leading_lemming_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 file to monitor dependencies. Ensure that your project does not include leading_lemming_0xrequest by removing it from your package.json and running npm install to refresh your dependencies.
Conclusion
The leading_lemming_0xrequest package poses a significant security risk due to its malicious code that alters package files and repurposes them for nefarious activities. It is crucial for developers to remain vigilant and take immediate action to secure their applications by updating or removing the affected package.
See every vulnerability recorded for leading_lemming_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications of your package.json file and the potential introduction of malicious code into your application.
You should update the package to a patched version or remove it entirely from your project to mitigate risks.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
