Malicious Code Injection in sour_goat_requirement Package
Summary
MAL-2025-96681: Malicious code in sour_goat_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 sour_goat_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the integration of various libraries and tools within a project. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages aimed at inflating developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and their projects.
Vulnerability Detail
The vulnerability in the sour_goat_requirement package 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 leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation and distribution of these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sour_goat_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 sour_goat_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 sour_goat_requirement package poses a significant risk due to its malicious behavior, which can compromise the integrity of projects relying on it. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for sour_goat_requirement →
FAQ
The sour_goat_requirement package is an npm package used for managing dependencies in JavaScript applications, but it has been identified as part of a malicious campaign.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and exposing it to further risks.
If you have installed the sour_goat_requirement package, you should uninstall it immediately using npm uninstall sour_goat_requirement.
Yes, tools like Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software without requiring access to the code or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
