Malicious Code Injection in living_whippet_requirement Package
Summary
MAL-2025-95297: Malicious code in living_whippet_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 living_whippet_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the living_whippet_requirement package originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify package.json files, removing private flags and changing version numbers. The malicious payload generates random package names and continuously republishes variants, which can lead to reputation inflation for the perpetrators and pollution of the npm registry. This poses significant risks, including the potential for developers to unknowingly use compromised packages, leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall living_whippet_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 living_whippet_requirement package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The living_whippet_requirement package has been identified as a malicious package that poses significant security risks to developers using npm. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your software.
See every vulnerability recorded for living_whippet_requirement →
FAQ
The living_whippet_requirement package is an npm package that is part of a malicious campaign aimed at exploiting the npm registry.
If your application uses the living_whippet_requirement package, it may be at risk of security breaches due to the malicious code that modifies package.json and republishing of compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected by this vulnerability without any signup.
If you have already used the living_whippet_requirement package, you should uninstall it immediately and review your project's dependencies for any other potentially compromised packages.
Yes, Vulert provides a tool that uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities, helping you maintain the security of your applications.
