Malicious Code Injection in wicked_marmot_requirement Package
Summary
MAL-2025-97367: Malicious code in wicked_marmot_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 wicked_marmot_requirement package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate specific functionalities within applications. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with altered metadata.
Vulnerability Detail
The vulnerability stems from the wicked_marmot_requirement package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags and changing version numbers. The malicious payload generates random package names and continuously republishes variants, which can lead to pollution of the npm registry and potentially compromise the integrity of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wicked_marmot_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, consider removing the wicked_marmot_requirement package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall wicked_marmot_requirement'. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The wicked_marmot_requirement package has been identified as a vector for malicious code injection, which poses a significant risk to applications using it. It is crucial to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for wicked_marmot_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity and security of applications that depend on this package.
You should uninstall the wicked_marmot_requirement package and monitor for any updates or patches that address the vulnerability.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
