Malicious Code Injection in big_meadowlark_0xrequest Package
Summary
MAL-2025-99968: Malicious code in big_meadowlark_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 big_meadowlark_0xrequest package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages. This vulnerability poses a significant risk to developers and users alike, as it can lead to the proliferation of harmful code within the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a token reward campaign that floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry with potentially harmful variants, leading to security risks for any application that depends on it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall big_meadowlark_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 big_meadowlark_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The big_meadowlark_0xrequest package poses a significant security risk due to its malicious code injection. It is crucial for developers to remove this package from their projects and seek alternatives to ensure the safety of their applications. Continuous monitoring for vulnerabilities is recommended to maintain secure software development practices.
See every vulnerability recorded for big_meadowlark_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.
You should uninstall the package immediately and check for any dependencies that may rely on it.
Yes, you should look for other reputable packages that provide similar functionality without the associated risks.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.
