Malicious Code Vulnerability in solid_moose_requirement Package
Summary
MAL-2025-96668: Malicious code in solid_moose_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 solid_moose_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is often utilized in various projects to streamline the development process. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful packages, which can compromise the integrity of applications relying on it.
Vulnerability Detail
The vulnerability originates from the solid_moose_requirement package being associated with the tea.xyz token reward campaign. This campaign involves the use of autopublish scripts that automatically generate and publish derivative packages with randomized names. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants to pollute the npm registry. This can lead to security risks, including the potential exposure of sensitive information and the degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall solid_moose_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 remove the solid_moose_requirement package from your project by executing the following command: npm uninstall solid_moose_requirement. This will help prevent any malicious activity associated with the package until a fix is available.
Conclusion
The solid_moose_requirement package has been identified as a vector for malicious code due to its association with a harmful npm campaign. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential threats.
See every vulnerability recorded for solid_moose_requirement →
FAQ
The solid_moose_requirement package is a dependency management tool used in JavaScript applications, part of the npm ecosystem.
This vulnerability can compromise your application's integrity by introducing malicious code that alters package configurations and can lead to security breaches.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.
If you cannot update the package, it is advisable to remove it from your project to avoid potential security risks.
Regularly check for updates to your dependencies, use tools like Vulert for monitoring vulnerabilities, and audit your package.json and package-lock.json files.
