Malicious Code Injection in nosy_ladybug_requirement Package
Summary
MAL-2025-95672: Malicious code in nosy_ladybug_requirement (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 nosy_ladybug_requirement package is a component within the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is part of a broader campaign that exploits npm's package management system to inflate developer reputation scores through automated scripts. This package, like others in the campaign, is designed to publish numerous derivative packages with altered metadata, potentially leading to security and integrity issues within the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the nosy_ladybug_requirement package, which is associated with the tea.xyz token reward campaign. The package includes scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional code execution and dependency issues for developers who may unknowingly integrate these compromised packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nosy_ladybug_requirementIf 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 nosy_ladybug_requirement package and any packages that depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The nosy_ladybug_requirement package poses a significant security risk due to its malicious code designed to manipulate npm's package management system. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their applications are secure from such vulnerabilities.
See every vulnerability recorded for nosy_ladybug_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring any signup.
You should remove the nosy_ladybug_requirement package from your project and monitor for any updates or patches that may address this vulnerability.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, ensuring you are alerted to any issues as they arise.
