Malicious Code Injection in liable_whippet_z3n Package
Summary
MAL-2025-95244: Malicious code in liable_whippet_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
Background
The liable_whippet_z3n package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate its own metadata and publish numerous variants, leading to potential security risks for developers and users relying on it.
Vulnerability Detail
The vulnerability in the liable_whippet_z3n package stems from its association with a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, ultimately polluting the npm registry and compromising the integrity of the software supply chain. The malicious payload can lead to unintended consequences, including the installation of compromised packages by unsuspecting developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall liable_whippet_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 avoid using the liable_whippet_z3n package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The liable_whippet_z3n package poses a significant security risk due to its malicious behavior of modifying package metadata and flooding the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for liable_whippet_z3n →
FAQ
The liable_whippet_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and publish derivative packages.
This vulnerability can lead to the installation of compromised packages, potentially exposing your application to security risks and affecting its integrity.
If you have installed the liable_whippet_z3n package, it is recommended to remove it from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time, alerting you to any issues 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 needing to sign up.
