Malicious Code Injection in liable_ladybug-silentdev Package
Summary
MAL-2025-105110: Malicious code in liable_ladybug-silentdev (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 liable_ladybug-silentdev package is part of the npm ecosystem, typically used for various JavaScript applications. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability stems from the package's involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is executed through autopublish scripts, which continuously republish variants of the package, compromising the integrity of the npm registry and potentially affecting users who unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall liable_ladybug-silentdevIf 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 workaround, you can monitor your package dependencies using tools like Vulert. By utilizing Vulert, you can check if your application is affected by this vulnerability without needing to access the code or installation. You can use the Vulert playground at https://vulert.com/scanner to analyze your package-lock.json file for vulnerabilities.
Conclusion
The liable_ladybug-silentdev package poses a significant risk due to its malicious code designed to manipulate the npm registry. Users are advised to uninstall this package and utilize tools like Vulert for ongoing monitoring of their dependencies to safeguard against similar vulnerabilities in the future.
See every vulnerability recorded for liable_ladybug-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and security.
You should uninstall the liable_ladybug-silentdev package immediately using 'npm uninstall liable_ladybug-silentdev'.
Yes, regularly monitor your dependencies using tools like Vulert to receive real-time alerts for open-source vulnerabilities.
No, the liable_ladybug-silentdev package is considered malicious and should be removed rather than patched.
