Malicious Code Injection in Agreed Lemming 0xrequest Package
Summary
MAL-2025-99266: Malicious code in agreed_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 'agreed_lemming_0xrequest' package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a token reward campaign that exploits npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the 'agreed_lemming_0xrequest' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive data and the degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall agreed_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 avoid using the 'agreed_lemming_0xrequest' package and look for alternative packages that provide similar functionality without the associated risks. Always validate the integrity of packages before including them in your project.
Conclusion
The 'agreed_lemming_0xrequest' package poses significant risks due to its malicious code that alters project files and publishes unauthorized packages. It is crucial to remove this package and monitor your dependencies regularly to maintain the security and integrity of your applications.
See every vulnerability recorded for agreed_lemming_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to unauthorized modifications in your project, potentially exposing sensitive data and compromising the integrity of your application.
Immediately uninstall the package using 'npm uninstall agreed_lemming_0xrequest' and review your project's dependencies for any other compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.
Yes, consider looking for reputable packages that offer similar functionality but do not have a history of malicious behavior.
