Malicious Code Injection in yearling_mongoose_0xrequest Package
Summary
MAL-2025-111265: Malicious code in yearling_mongoose_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
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 yearling_mongoose_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate requests in a structured manner. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the yearling_mongoose_0xrequest package stems from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts designed to automatically publish derivative packages with altered metadata. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random names, ultimately polluting the npm registry and potentially compromising the integrity of applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall yearling_mongoose_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 yearling_mongoose_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for any changes that may introduce vulnerabilities.
Conclusion
The yearling_mongoose_0xrequest package poses a significant security risk due to its malicious code injection capabilities. It is essential to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive is key to maintaining the security of your applications.
See every vulnerability recorded for yearling_mongoose_0xrequest →
FAQ
It is an npm package used for making structured requests in JavaScript applications, but it has been identified as malicious.
The vulnerability can lead to the injection of malicious code, altering your application's behavior and potentially compromising security.
You should remove the yearling_mongoose_0xrequest package immediately and look for alternatives.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
