Malicious Code Injection in mutual_ladybug_z3n Package
Summary
MAL-2025-88559: Malicious code in mutual_ladybug_z3n (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 mutual_ladybug_z3n package is part of the npm ecosystem, often associated with token reward campaigns that aim to inflate developer reputation scores. This package is designed to automate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry. Its primary functionality revolves around creating and managing these packages, but it has been compromised to include malicious scripts.
Vulnerability Detail
The vulnerability in the mutual_ladybug_z3n package stems from its inclusion in a campaign that floods npm with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the continuous republishing of these variants. This not only affects the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mutual_ladybug_z3nIf 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 remove the mutual_ladybug_z3n package from your project to prevent any potential exploitation. Use the following command: npm uninstall mutual_ladybug_z3n. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The mutual_ladybug_z3n package has been identified as containing malicious code that can compromise the integrity of npm projects. It is crucial for developers to take immediate action by updating or removing the package and utilizing monitoring tools like Vulert to ensure ongoing security.
See every vulnerability recorded for mutual_ladybug_z3n →
FAQ
The mutual_ladybug_z3n package is an npm package involved in automated package generation and publication, often linked to token reward campaigns.
The vulnerability can lead to the modification of your package.json file, potentially exposing your project to further malicious activities and affecting the integrity of your dependencies.
If you have installed the mutual_ladybug_z3n package, it is recommended to uninstall it immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
To prevent future vulnerabilities, regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
