Malicious Code Injection in retail_goose_requirement: A Threat to npm Packages
Summary
MAL-2025-96343: Malicious code in retail_goose_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 'retail_goose_requirement' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. Such practices can lead to the pollution of the npm registry, affecting developers and users relying on legitimate packages.
Vulnerability Detail
The vulnerability in 'retail_goose_requirement' stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to create numerous derivative packages that flood the npm registry, potentially leading to confusion and misuse of legitimate packages. The malicious payload can compromise the integrity of the npm ecosystem and affect developers' trust in package management.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall retail_goose_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 'retail_goose_requirement' package from your project by executing 'npm uninstall retail_goose_requirement'. This will prevent any potential malicious code from executing until a fix is applied.
Conclusion
The 'retail_goose_requirement' package poses a significant threat due to its malicious behavior aimed at polluting the npm registry. It is crucial for developers to take immediate action by updating or removing the package and to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.
See every vulnerability recorded for retail_goose_requirement →
FAQ
The 'retail_goose_requirement' package is an npm package that is suspected to be involved in a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
This vulnerability can lead to the pollution of the npm registry, potentially causing confusion and misuse of legitimate packages, which can compromise the integrity of your project.
If you are using 'retail_goose_requirement', it is advisable to uninstall the package and monitor for any updates or patches that address the vulnerability.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.
To prevent vulnerabilities, regularly update your packages, use trusted sources, and employ tools like Vulert to monitor for potential threats in your dependencies.
